They’re Courting You, Marketer and That’s the Tell.
Or Why Martech Latest Moves Gives You Leverage
Last week has been an absolute whirlwind in the marketing technology (martech) industry. Databricks announced their Agentic CDP while Hightouch make a billionaire offer for customer identity capabilities.
Although these may seem disconnected at first glance, the reading on what connects them (and other recent martech related news) is the following: it all points to you, Dear Marketer, as all of these announcements are indeed targeted to you.
The reason for this is actually simple: without marketing's involvement, marketing technology won't realize it's promise or value. And this gives us, marketers, leverage!
This is what the article below is about. How can marketers use this leverage to ensure they are always involved in the right conversations around technology, regardless of its architecture.
This past week, Databricks launched the CustomerLake. An agentic CDP, built right into the data platform. No more moving data into a separate system. No more begging IT for a copy of the customer file. Everything governed in one place. The main headlines around this announcement told marketers they were getting more power, by sitting closer to where all the data lives.
Maybe. Or maybe not. And that ambiguity is the whole point of this piece.
This article is my read of this ambiguity based on my own experience so far.
CustomerLake could genuinely help marketers. All the data, all the context an agent needs, in one place and easier to handle than it has ever been. I know what it is like to have marketers close to where the customer data lives. When I built the customer data infrastructure for a global enterprise, unifying millions of customer profiles across different countries, consolidating into the customer data platform was the moment marketing gained access, not lost it. Before that the data was scattered and out of reach. Putting it in one governed place is what finally let us use it.
But there is another version, and many marketers out there live it. The consolidation of customer data can live closer to IT than to marketing. Consolidating the customer assets could just as easily push these further from the people who activate it. I cannot tell you which way the future of martech (including CustomerLake) breaks and at this point, no one else can be sure of it either.
And here is the thing I most want you, marketer, to take from this. It is not just CustomerLake. Every major move in martech right now is courting marketers but all can cut both ways. Each one can pull marketing closer to the customer data or push it further away, and which one happens is rarely decided by the technology itself, but by who is in the room when the layer gets designed and governed. I had access to customer data because I was at that table. I helped define how the data was structured and how it would be activated. The architecture did not hand me access. Being in the room where it was discussed did. That is the part you control, no matter which way the technology goes.
Let me walk through the moves and its tension.
You are reading The Experimental Marketer Newsletter.
What you get: every week, one martech or AI concept broken down
with real examples, step-by-step walkthroughs, and the career case for why it matters.
Created by a Marketer, for Marketers.
The CDP collapsing into the data layer
Start with the launch itself. David Raab, who founded the CDP Institute, said the quiet part out loud in his coverage: bringing the CDP under the corporate umbrella is a real improvement, but it can also mean IT gains more control that marketers may not appreciate. He called this tension between IT and marketing “a tug of war we do not talk about in polite society”.
Matthew Niederberger, who got an early look at the product, named what changed hands. Writing on Martech Therapy, he stripped CustomerLake down to one sentence: it is the marketing interface built on the data itself, and what the platform took back is not your data, it is the layer between you and your data. Every CDP before it rented you that layer. Databricks built it and kept it.
Read that two ways, because both are live. If marketing helped design how that layer governs access, this type of martech consolidation is very beneficial for marketers. The data is finally unified, governed, and usable, exactly the upside I lived. If marketing was not in that conversation, the same consolidation means the layer between you and your customer now answers to someone else, and your access becomes a request rather than a given. Same architecture. Opposite outcomes. The difference lies in who set the terms.
The convergence Brinker has been mapping
Databricks is not an isolated event. It is one visible instance of a shift Scott Brinker has tracked for two years on chiefmartec: application platforms are becoming infrastructure platforms, and now an infrastructure platform is becoming a marketing application platform. Both directions arrive at the same place, the governed data layer. Salesforce and HubSpot walk toward it from the application side. Databricks and Snowflake from the data side. They meet in the middle, and the middle is where your customer data lives.
Brinker also makes the point that sets the stakes. In the AI era, data is the substrate. Every agent and workflow is only as good as the data and context it can draw on. Point a capable agent at fragmented data and you get confident nonsense.
Here is the two-sided part. An agent is only as useful as the context it runs on, and, when it comes to marketing technology, a lot of that context is not technical, it is marketing knowledge that lives nowhere else. Why a lapsed customer actually churned, as opposed to what the data shows. Which promotion trains customers to wait for a discount and quietly erodes margin. That a spike in support tickets after a launch is a signal to suppress a cross-sell, not an opportunity to send one. Whether a segment is genuinely high value or just high frequency. None of that sits in a schema. It comes from the people who have run the campaigns, talked to the customers, and watched how the audience actually behaves over time, not in the latest snapshot but across the whole album of pictures. That is marketing’s context, and an agent that does not have it will optimize confidently for the wrong thing.
So if marketers own that context and feed it into the layer, this convergence puts them at the center of the most valuable system in the company, because they are supplying the one input that makes the agents correct rather than merely fast. If they do not, the agents get their context from whoever is in the room instead, usually defined in technical terms by people optimizing for what is measurable rather than what matters, and marketing becomes a downstream consumer of decisions made by a layer it never touched. The technology is the same either way. What differs is whose knowledge is baked into it.
The scramble over identity
You can watch the industry “price” this in real time. In May, Publicis agreed to buy LiveRamp. Within weeks, before that deal even closed, Hightouch, a leader in composable customer data platforms, made a play for LiveRamp’s identity assets, its RampID and Connect products. Identity resolution is the single highest-value function inside the data layer, the connective tissue that turns scattered records into one usable customer, and its worth climbs as signals get noisier and scarcer.
Two-sided again, and the axis that matters is whether this type of identity stays vendor-agnostic or becomes vendor-captive. If the matching layer is agnostic, the marketer can sit close to it, build intelligence on top of it, and carry that intelligence across a vendor change instead of rebuilding it. The identity spine stays portable. That is the upside Hightouch is selling when it argues the matching layer should not live inside a single agency holding company. The other version is identity sitting inside Publicis and LiveRamp alone, where the most valuable layer of your customer asset is tied to one owner, with all the lock-in that implies for how much of your accumulated intelligence actually travels with you if you leave.
The tension here is between brand-side marketers and external vendors (such as agencies), instead of the marketing versus IT we saw previously.
The trap inside the good advice
This is a red flag I want to raise. Gartner is advising CMOs to treat Databricks CustomerLake as a data infrastructure decision rather than a traditional CDP purchase, and to reassess long-term contracts before renewing into 2027 and beyond. From an economic standpoint, that advice is very hard to argue against. A standalone CDP about to be commoditized by the data platform is not worth a three-year lock-in.
But watch what the reframe does when it comes to the different team’s dynamic. The moment a CMO accepts that this is infrastructure and not martech, the natural logic of the organization says infrastructure belongs to IT only. The reclassification that saves money can quietly cost the access to customer data. A CMO who hears “this is plumbing now” and steps back from the architecture conversation has not delegated a procurement decision. They have handed over the customer data and called it efficiency.
The CMO’s job at this moment is to stay in the room precisely because the decision got reclassified, not to leave because it did.
Read the courting correctly
So why is every vendor in this category suddenly speaking to marketers, promising access, and ensuring “for marketers” is in the product copy for platforms that live in what has been always considered to be IT’s domain?
Because your (marketing) work is what makes the data worth anything. A unified customer profile can be useless until someone turns it into a decision, a campaign, a relationship, a number on the revenue line. The data platform can govern the data. It cannot, on its own, realize its own return on investment (ROI). When it comes to marketing technology that is marketing’s job, and the vendors know it. They are courting you because they need you to realize the return on all of this. Without the marketer, the martech ROI does not exist.
That is your standing to be in the room. Not a favor, not an invitation you wait to receive. The courting is the proof that your presence is required for any of this to have value to the company. So the question is whether you treat it as a compliment or as leverage.
Leverage unused is leverage lost. If marketers read the access story, feel flattered, and lean back, the provisioning and permissions and cost controls settle with IT and procurement by default, and “access for marketers” can mean “marketers may request access through a ticket.” That is the failure mode. Not a hostile takeover but marketing being simply handed an invitation and not reading the terms.
So trust the invitation enough to show up. Do not trust it enough to skip the fine print. Being courted is the opening of a negotiation, not the conclusion of one.
What survives whichever way it breaks
If you cannot predict which way any of these moves land, what do you invest in? Two things, and neither depends on the architecture going your way.
The first is the definitions. Brinker calls it the semantic layer, the agreed meaning that keeps a thousand agents from answering with a thousand interpretations. What counts as an active customer. What churn means in your business. Which segment is high value and why. These are not IT decisions and they are not data-engineering decisions. They are marketing decisions, as much as brand guidelines are, and they determine what every downstream agent does. IT cannot define them without you. Claim that work loudly, now, before someone less equipped fills the vacuum.
The second is trust. The human credibility, the relationship, the judgment about what to do with what the data says. Niederberger makes this point from the platform side, worth hearing from someone who studied the product up close. The thing a warehouse cannot buy, he writes, is the thing that was always hardest. The agents can surface the next best action. They cannot own the customer relationship or carry the accountability for it. That stays human, and in most organizations that human is in marketing.
Marketing access to the data layer can be given or withheld. Ownership of what the data means, and of the trust the whole system is built to earn, is a competency no reorganization removes. One you negotiate for. The other you already hold and you should act like it.
What you can do on Monday
Reading this and nodding is not the point. Here is where to start this week, in order.
Find out who owns provisioning. Before the next data-platform conversation, learn exactly which team controls access to the unified customer profile today, and who will control it after any consolidation. If you do not know the name of the person who can grant or deny marketing’s access, that is your first gap to close.
Get yourself named in the governance conversation. Not cc’d. Named. Ask to be a required party in the data-platform architecture and access decisions, on the record. The reason is simple and you can say it out loud: marketing is accountable for the customer outcome, so marketing has to be in the room where customer-data access is decided.
Write down your definitions before someone else does. Draft the marketing definitions for your top five customer metrics, if you haven’t done already. Active, churned, high-value, engaged, qualified. Put them in a shared document and circulate them as marketing’s contribution to the semantic layer. This is the highest-leverage hour you will spend this quarter, because it claims the one piece of the data layer that is unambiguously yours.
Read the access terms, not the access pitch. When a vendor or an internal team says “this gives marketers more access,” ask three concrete questions. Access to do what, specifically. Granted by whom. Revocable how. If the answers are vague, the access is decorative.
Audit what you would lose tomorrow. List the data and the tools you touch today that would move into the data platform under consolidation. For each one, note whether your access travels automatically or has to be re-granted. That list is your negotiation agenda.
The shape of it
I cannot tell you whether CustomerLake brings the customer asset closer to marketing or pushes it away. I cannot tell you whether the identity scramble ends with a cleaner spine for marketers or a locked one. I cannot tell you whether the convergence Brinker maps puts marketing at the center of the data layer or leaves it downstream. None of these has landed yet.
What I can tell you is which marketers will be in a better position whichever way the coins fall. Not necessarily the ones with the most technical depth, but the ones who made sure they were in the room before the question got answered for them. The ones who treated being courted as proof they belonged at the table, and negotiated the terms instead of waiting to be told them.
That is the whole move, and it works regardless of the architecture. Show up to the conversation you used to be left out of. Claim the definitions and hold the trust. The courting is real, and the leverage is real, and both of them expire the moment you decide this is someone else’s decision to make.
What does this look like inside your organization right now? Reply and tell me where you sit in this, because I think a lot of us are closer to that moment than we are admitting.
End Notes
Databricks CustomerLake: the data lakehouse is now the CDP — Matthew Niederberger, Martech Therapy. The closest read on what CustomerLake actually changes, from someone who previewed the product: the platform took back the layer between you and your data, not the data itself.
Meet the Newest Martech Member: Databricks via CDP — Dom Nicastro, CMSWire. The launch coverage where David Raab names the marketing-versus-IT tug of war, and where Gartner’s “treat it as infrastructure procurement” guidance appears.
The 2nd-Order Effects of Generative AI on Marketing and Martech, 3 Years Later — Scott Brinker, chiefmartec. The application-meets-infrastructure convergence and the semantic layer as marketing work. Brinker writes and maintains the Martech Supergraphic at chiefmartec.
Databricks, Adobe, and a Tug-of-War Over LiveRamp: Three Signals, One Direction — Ian Kim. Background on the Publicis–LiveRamp deal and Hightouch’s bid for the RampID and Connect identity assets, and the neutrality argument for keeping the matching layer out of a single holding company.