Will CDPs, AI decisioning platforms, and marketing automation platforms converge?

Summary

• Databricks' position is that agents need "context, intelligence, and execution in the same place." CustomerLake, its agentic CDP, is built to put customer data, identity resolution, audience building, campaign automation and activation on the lakehouse. Whether the wider market converges is a forecast that Databricks' documentation can't settle.
• CustomerLake is in Private Preview. Databricks announced it on June 16, 2026, and points interested teams to their Databricks account team.
• Databricks says existing CDPs "sit outside of the company's core Data and AI platform," which "creates another system to integrate, govern, and reconcile." CustomerLake is embedded in the lakehouse and governed by Unity Catalog.
• Convergence in this design doesn't mean replacing every tool. Databricks says CustomerLake is open and composable, and it syncs audiences and signals to the martech, adtech and customer experience tools teams already use.
• Feedback is part of the design. Databricks says that in an agentic model "measurement becomes part of the decision loop," and that Campaign Agents continuously optimize experiences around business goals.

Will CDPs, AI decisioning platforms, and marketing automation platforms converge?

Databricks' position is that customer data, decisioning and execution belong in one environment, and CustomerLake is the product it built on that premise. Nobody can confirm that the whole market will follow, so treat convergence here as a design direction that Databricks documents, not a settled outcome. CustomerLake is in Private Preview, announced on June 16, 2026.

Why do these categories overlap today?

The launch post lists the customer data infrastructure that enterprises have built up: data warehouses, data lakes, CDPs, CRMs, marketing automation platforms, identity providers, advertising platforms, and analytics tools. It says the problem is "architecture, not strategy." Its specific complaint about CDPs is where they sit: existing CDPs "help unify customer profiles and activate audiences, but they sit outside of the company's core Data and AI platform."
A later Databricks post adds measurement. In many organizations, it says, measurement "arrives after the fact as a report on what a campaign delivered." In an agentic model, it "becomes part of the decision loop."

What does CustomerLake combine in one platform?

The press release says CustomerLake "consolidates customer data, identity resolution, audience building, campaign automation, and activation into a single AI-native foundation." The table maps each job to what Databricks says CustomerLake does.

Job	What Databricks says CustomerLake does
Customer profiles	Profile Agents turn raw customer data into business-ready Customer 360 profiles directly in Databricks.
Identity resolution	Agentic Identity Resolution combines deterministic, probabilistic and agentic matching to create golden Customer 360 records from fragmented identity data.
Audiences	Marketers create and refine segments in natural language with Genie.
Decisioning	Campaign Agents use governed customer context to recommend next-best actions.
Campaign automation	Campaign Agents activate across channels and continuously optimize experiences around business goals.
Activation	Native integrations and reverse ETL sync audiences and signals with martech, adtech and customer experience tools.
Governance	Unity Catalog provides centralized control over access, lineage and auditability across customer data, audiences and AI assets.

How does the data stay in one place?

Databricks says CustomerLake is "built natively in Databricks," so teams can build and activate customer intelligence on the governed foundation they already use "without copying sensitive data into a separate CDP or proprietary application." Through Lakehouse Federation, teams can reach customer data where it already lives in other systems. The Databricks docs describe Lakehouse Federation as "governed, read-only access to external data through Unity Catalog foreign catalogs."
Audience data does reach destinations. The launch post describes bi-directional pipelines to marketing tools, advertising platforms and customer engagement channels. So "without moving data" describes where the CDP runs, not whether audience data ever reaches a destination.

What stays outside the platform?

Asked whether CustomerLake replaces existing martech tools, the Databricks FAQ answers "Not necessarily." It describes CustomerLake as "open and composable, and designed to work with the marketing, advertising, analytics, and customer experience tools teams already use." The launch post says teams can "activate audiences and signals back into the tools marketers use every day."

How does feedback reach the next decision?

Databricks describes feedback in two places. Agentic Identity Resolution includes "LLM and human review workflows for edge cases, and an agentic learning loop that recommends improvements to matching logic." For campaigns, Campaign Agents "optimize or suppress based on performance signals," and "Humans still define the strategy, goals, and guardrails."

What should you confirm before consolidating?

• Lifecycle stage. CustomerLake is in Private Preview, and the launch post gives no general availability date. Contact your Databricks account team.
• Destinations. Ask whether each martech, adtech and customer experience tool you use is a supported destination, and which fields leave Databricks for each.
• Where your data lives. Data in Databricks is used where it sits. Data in other systems is reached through Lakehouse Federation, which is read-only.
• Commercial terms. The launch post mentions a consumption model but publishes no rates, so get terms in writing.

FAQs

Does CustomerLake replace my existing marketing tools?

Not necessarily, according to Databricks. Its FAQ calls CustomerLake open and composable and says it is designed to work with the marketing, advertising, analytics and customer experience tools teams already use. It also positions CustomerLake for brands that want to reduce martech complexity and consolidate spend.

Can CustomerLake use customer data that isn't in Databricks?

Yes, according to Databricks. Through Lakehouse Federation, teams can access customer data where it resides, including cloud object storage, operational databases and other warehouses. Databricks documents Lakehouse Federation access as governed and read-only.

What lifecycle stage is CustomerLake in?

Private Preview. Databricks announced it on June 16, 2026 with the sentence "CustomerLake is now available in Private Preview," and tells interested teams to contact their Databricks account team. Confirm the current stage with them before you plan a rollout.