Adtech and Martech Were Never Two Industries. They Were Two Copies of the Customer.

On this page

The partner sheet is the argument · The Custody Partition · Correct the record before building on it · Governed Customer Memory · The cadence split was billing, not strategy · The collapse runs on old pipes · The market has not priced this yet · The org-chart war · Lock-in swap, round two · The void at the boundary · Orchestration after the wall

The partner sheet is the argument

Read the partner list in CustomerLake’s launch announcement the way you’d read a seating chart. The identity spine is there: LiveRamp, Acxiom, Epsilon, TransUnion, Adstra. Adtech’s execution layer is there: Meta, The Trade Desk, Magnite, Snap, Unity, IAS. Martech’s engagement layer is there: Adobe, Braze, Iterable, Bloomreach, Twilio. Three rows that have spent twenty years billing as two industries — one that buys attention from strangers, one that manages relationships with customers — all wired into a single hub inside a single data platform, feeding from and writing back to the same governed context.

Adtech and martech were never two industries. They were two copies of the customer. Call it the Holistic Collapse — the moment the industry’s oldest partition, adtech versus martech, paid versus owned, acquisition versus retention, stops making operational sense because both sides read and act from one context. The wall did not fall because vendors integrated. It fell because the customer state moved underneath both of them.

Two industries, one table.

Not one physical table. One governed customer state.

The Custody Partition

The adtech/martech split was never a strategy. It was the Custody Partition — a divide born of who held the customer record: paid surfaces rented other people’s view of the customer, owned surfaces held your own, and those two custodies calcified into two vendor categories, two budgets, two trade presses, two org charts. Nobody chose it; it precipitated out of data plumbing, and then everyone built careers on either side and called the residue a discipline.

The wall’s best defense is the claim that the two jobs were genuinely different, so be precise about what each side actually did. Adtech bought access to audiences the brand did not own — anonymous users, modeled segments, rented inventory, attention priced by a media market. Martech activated relationships the brand already had permission to manage — subscribers, members, customers, consented records on owned channels. Both reached people; email and SMS reach people all day. The difference was never the reaching but the commercial and data relationship behind it: adtech was reach through rented access, martech was reach through owned relationships. One found demand; the other managed demand once the relationship was earned. Which is exactly why the partition dissolves under one governed memory: when the same context holds both the rented introduction and the earned relationship — and the same loop decides whether the next touch is a paid impression or an owned message — finding demand and managing it stop being departments and become phases of one decision.

Don’t take my word for it. Take Databricks’. The founders’ manifesto — Argyros, Ghodsi, Xin, published June 17 — dismisses every prior CDP, bundled and composable alike, as “middleware of the marketing stack, sitting between data platforms and execution tools.” Databricks ↗ An infrastructure vendor wrote the epitaph for the category it had just entered, and the epitaph is precise: middleware occupying the between is exactly what held the two custodies apart. Databricks did not end the adtech/martech split. It exposed how little of it was strategic.

Vendor categories and marketing org charts are downstream of where the customer record lives, and when the record moves, the categories reorganize around it. June’s essay in this series traced three generations fighting over that question — DMP, packaged CDP, composable CDP — and ended with data that stopped moving. Generation four is what happens once it has stopped: the record stays put, and everything else moves instead.

Correct the record before building on it

Databricks was not first to the agentic CDP. Hightouch published the category name a day earlier, on June 15. The functionality — agents autonomously deciding content, timing, and channel on warehouse-native customer data — had been shipping since August 2024 at Hightouch, then across Adobe, Zeta, Salesforce, Treasure, and Amperity through 2025 and early 2026. Smaller vendors like Aampe and GrowthLoop wore the label earlier still. CustomerLake’s one surviving first is narrower and more interesting: it is the first agentic CDP embedded natively inside a major data platform — a lakehouse workload governed in place — and it is a firstness Databricks itself never claims.

What Databricks did supply was compression: Hightouch named the category on June 15, Databricks shipped CustomerLake on June 16, and BlueConic bought Blueshift as an agentic-CDP foundation on June 17 — a category that would once have taken years to congeal took a business week. Even the referees decline to call it: CDP.com’s glossary credits no coiner, noting only that the term “entered industry vocabulary in mid-2026, with multiple vendors adopting it simultaneously” — a glossary bylined by a combatant, Treasure AI’s CEO.

When I call this the fourth generation, that is this essay’s continuing count from June — DMP first, then packaged, then composable, then agentic. MarTech and CDP.com count three because they omit the DMP. Databricks uses no numbering at all. The arithmetic is mine; the lineage argument doesn’t depend on it.

The category also forked at birth — embedded inside the platform, layered above it, headless beneath external agents — which is why the collapse must be credited to where the operators consolidate, not to the label.

Governed Customer Memory

Here is the mechanism. Call it Governed Customer Memory — once one governed memory is the only place agents read, write, and learn against customer state, every surface — paid or owned — demotes from department to endpoint of the same loop. The wall never needed demolishing; it needed a single source of state on both sides, at which point it stopped being load-bearing.

What makes the memory worth writing to is Databricks’ most useful coinage. Golden Context — their term, their claim — adds what the Golden Record never carried: “what the business is trying to accomplish right now, and what’s already been tried with this customer and how they responded.” The strategic asset shifts from identity to memory. Even the category’s designated skeptic, perform.digital, concedes the core while hunting for agent-washing: the customer profile stops being something a marketer reads and becomes something software acts on.

Both namers of the category even agree on the counterfeit. Hightouch warns that much of what will ship under the label is “a chat interface stapled to a system of record” Hightouch ↗; Tasso Argyros, presenting the CustomerLake launch, insists the agentic CDP “is not about putting a chat box in the UI of an existing CDP” but about “making the agent the core infrastructure piece” [Vendor-claimed — launch video]. When two vendors racing each other for a category spend launch week warning against the same imitation, the category has a definition before it has a market.

The lineage argument compresses into one career. Tasso Argyros founded ActionIQ, the archetypal packaged CDP, and now co-signs the manifesto declaring both packaged and composable CDPs “simply not designed for an era of agents” Databricks ↗ — a founder countersigning his own category’s obituary from inside a data-infrastructure company.

And once software is the actor, the partition’s last defense — headcount — dissolves too. Adtech and martech were, operationally, two workforces at two consoles reading two copies of the same customer; that staffing arrangement was the wall’s payroll, not its justification.

Agents that share one memory do not respect channel org charts.

Row by row, the operating model rewrites:

The cadence split was billing, not strategy

If custody was the wall’s foundation, rhythm was its daily enforcement. Acquisition ran discrete campaigns — brief, flight, wrap report. Retention ran always-on lifecycle — triggers, journeys, drips. Two cadences meant two planning cycles, two measurement vocabularies, two P&Ls, and a permanent excuse never to merge the teams.

Ghodsi’s launch line, from the press release, is aimed straight at that seam: “marketing stops being a series of campaigns and becomes a continuous loop.” Infinity Campaigns — Databricks’ branding, currently a Private Preview promise rather than a documented behavior — don’t so much abolish the cadence split as show it was never structural: one loop that adapts message, timing, and channel continuously, indifferent to whether the touch it selects is a paid impression or an owned email.

The pricing is the tell. The campaign was always a unit of billing as much as a unit of work, and CustomerLake ships with “a value-aligned consumption model rather than a traditional software license” — no numbers, meters, or SKUs published. Martech Therapy’s Niederberger and Kihlstrom read it as no platform fee, with revenue captured through compute. But a vendor that monetizes the loop rather than the license has told you which one it thinks survives.

The collapse runs on old pipes

The collapse is less total than the keynote implied. By Databricks’ own launch blog, activation runs on “native integrations and Reverse ETL” Databricks ↗ — bi-directional pipelines to marketing tools, ad platforms, identity graphs, engagement channels. That is the composable era’s last mile, verbatim, carried forward intact under the flagship of the fourth generation. The break is in the operator, not the plumbing. June’s essay closed by predicting the activation layer becomes the agent’s execution surface; three weeks in, that prediction is vindicated in operation and still premature in architecture.

The execution side is already positioning for it. The Trade Desk’s launch quote — Jay Goebel, VP of Data Partnerships — describes the DSP as “connecting trusted, deterministic data and agentic AI with media execution”: the open internet’s largest buying platform volunteering to be the endpoint, not the department.

The more telling move is IAS. Verification vendors were the wall’s border police — they existed to audit what happened on the paid side and report back to the owned side. IAS’s launch integration inverts that: media-quality and attention signals, drawn from a claimed 300-billion-plus daily media transactions, flow through partner clean-room connections directly into CustomerLake as profile-level audience inputs rather than post-campaign reports. Measurement, the function that policed the partition, moves inside the shared context.

The gaps are confirmed absences: no incrementality framework appears anywhere in CustomerLake’s launch materials, and no Databricks Clean Rooms integration is documented — clean rooms arrive only through partners. The collapse has a measurement-shaped hole in it.

The market has not priced this yet

The market has not yet priced the implication — a weaker claim than “the defenders are silent,” and the honest one, because absence of coverage proves little by itself. But the texture is worth recording. Across AdExchanger, Digiday, Ad Age, ExchangeWire, and Marketecture — checked by site-restricted search as of July 5 — the lone response to an infrastructure vendor calling the partition middleware is one Adweek piece, paywalled and unresolved. No holdco has commented. And the services bench on the launch sheet — Accenture, Deloitte, Slalom, Stitch, Lovelytics — is consultancies, not one media agency. Databricks is routing around the agency layer to the brand’s data organization.

The identity rows carry their own quiet irony. Post-Publicis–LiveRamp, the identity marketplace inside the “neutral” lakehouse is largely holdco-owned — Epsilon is Publicis, Acxiom is Omnicom, LiveRamp is Publicis pending. The holdcos are inside the tent as data assets while absent from it as agencies. Meanwhile CustomerLake’s own Agentic Identity Resolution — deterministic, probabilistic, and agentic matching, per the product page — quietly moves first-party resolution in-house, relegating the external graphs to enrichment and match-key translation. The spine is being federated and hollowed at the same time.

Even the loudest missing chapter — Circle K sits in the private preview, Magnite and Unity and Snap sit on the partner list, and no one has said the words retail media — goes unremarked. None of this proves the implication; it does suggest it simply hasn’t been read yet.

The org-chart war

Budgets follow standing, and standing is what moves first. Losing it:

• Media agencies that own execution but not customer state
• Legacy martech vendors that own workflow but not data gravity
• Identity vendors demoted from control points to enrichment layers
• Campaign-ops teams whose value was moving data between systems
• Measurement vendors that stay outside the customer context

Gaining it:

• Brands with strong first-party foundations
• Data-cloud teams, who now hold the operating state
• Vendors that write learning back into governed context
• Agencies that reinvent as agent-governance and experimentation partners
• Measurement providers that become feedback infrastructure rather than reporting vendors

Lock-in swap, round two

June’s essay showed the composable generation relocating lock-in from the CDP vendor to the warehouse. The collapse moves it again — from custody to operation.

Custody does not get worse. Your tables were already in the lakehouse; “if you stop using CustomerLake, your data doesn’t go anywhere,” as Datawhistl’s analysis puts it. What stops being portable is the state above the tables: the Golden Context memory your agents accumulate, the always-on Infinity loops mid-flight, the governance semantics encoded in Unity Catalog. The composable era’s exit cost was rewriting SQL. This era’s exit cost is an organization’s institutional memory.

So the renewal conversation needs a new question. Call it the State Exit — the exit interview that asks not whether your data can leave, but whether your agents’ memory, loops, and policies can. Ask it of CustomerLake today and you get silence: the product is in Private Preview with no public documentation of whether agent state is exportable. Currently unanswerable is not the same as no, but it is nowhere near yes.

Even the marketed hedge deepens the bet. Lakehouse Federation reaches into Snowflake and BigQuery, but — per Niederberger and Kihlstrom — a rival’s data pulled through federation still runs across Databricks’ control plane, its governance, and its bill. The hedge enlarges the perimeter it claims to soften.

“Deepens” is architecturally reasoned, not operationally demonstrated. CustomerLake’s autonomy is still a Private Preview promise: the launch demo shows real gates — marketer approval of the agent-drafted campaign brief, a pre-launch simulation with per-decision reasoning logs — and the launch blog’s one firm governance sentence is that humans still define “the strategy, goals, and guardrails” [Vendor-claimed — launch materials]. But demo gates are not audited gates. The direction is confirmed across a dozen vendors; the shipped, verified behavior of this product is not.

The void at the boundary

Inside the walls, the collapse is complete: one context, one loop, every surface an endpoint. At the edge of the walls, it is undefined. Across all five primary Databricks sources — launch blog, founders’ manifesto, product page, press release, launch video — there is zero mention of MCP, A2A, or AdCP. Confirmed absence. The only interop claim on record is secondhand: briefing-derived coverage reporting that third-party agents can plug in via APIs or Model Context Protocol.

Which leaves the most consequential moment in the whole architecture unspecified: the moment the brand’s buying agent meets a seller’s agent. That handshake is AdCP’s territory — I sit on an AdCP working group, so weight my interest accordingly — and it is where this series’ Friday polls have already been pointing: in agent-to-agent commerce, trust is conferred, not computed, and something like a Delegate Audit Record is what conferral will demand of a loop that acts without asking.

The manifesto deleted the middleware between data and execution. The between that remains — between one company’s agents and another’s — cannot be deleted, only standardized. The one wall left standing is the one nobody at the launch mentioned.

Orchestration after the wall

The budget question changes shape. For twenty years it was: which side of the partition does this dollar sit on? Now it is: which layer commands the agents? Three directives follow.

First, ask every vendor the State Exit question before renewal. Any vendor that answers about data is answering last generation’s question.

Second, staff where the buying center already moved. Both named launch champions hold data-org titles — HP’s Global Head of Marketing Technology and AI Enablement, Getnet’s Chief Data and AI Officer — not CMO titles, and David Raab’s warning lands on exactly that seam: “IT gains more control, which marketers may not appreciate.” The collapse has an org-chart cost, and pretending otherwise just means paying it unprepared. Scott Brinker — disclosure: he published a research report in partnership with Databricks in March — frames the new marketing-ops job as engineering Golden Context. He’s right, and the job posting belongs in the data organization.

Third, plan for coexistence. “It’s unlikely either approach wins,” as MarTech’s verdict put it MarTech ↗, and the fork is real: embedded suits the data-mature enterprise, the layer-above suits the CMO-led one. The partition can die while the vendors that grew up on either side of it live on as layers. Categories are mortal; companies are stubborn.

But hold the two claims apart, because both are true. The vendors survive. The wall does not. And the fight that replaces it is not adtech versus martech — it is who owns the operating state: the data cloud, the engagement cloud, the ad platform, the agency, or the brand. The CMO question rewrites accordingly, from which channel owns this budget? to which agent is allowed to act, with what memory, under which policy, against which proof?

Against which proof is not a compliance afterthought — it is the engine of the context economy: permissions are a relevance signal, and the governed memory that stores consent, provenance, and scope is what tells an agent which moment matters in the first place.

That is what the fourth generation actually is. The CDP category is not just becoming agentic — it is absorbing the operating boundary between paid and owned media, because both sides now read from, write to, and learn against the same governed customer memory. Two industries, one table. The only question left is who sits at the head of it.