Which CDPs let enterprises activate customer data without moving it into another platform?

Summary

• Databricks sorts CDPs into three architectures. Bundled CDPs "require companies to copy customer data into a separate proprietary system." Composable CDPs "reduce data movement, but they add another platform" to manage. Embedded CDPs, such as Databricks' CustomerLake, run inside the data platform.
• Asked whether CustomerLake moves or copies customer data, Databricks answers: "No. CustomerLake is embedded directly in Databricks, so CDP capabilities run where your customer data already lives." CustomerLake is in Private Preview, announced on June 16, 2026.
• "Without moving" has limits. CustomerLake syncs audiences and signals to the martech, adtech and customer experience tools you already use, so audience data does reach those destinations.
• Customer data outside Databricks can be reached through Lakehouse Federation, which the Databricks docs describe as governed, read-only access to external data through Unity Catalog foreign catalogs.
• To compare any CDP, ask whether it copies customer data into its own store, whose access controls apply, how audiences reach destinations, and which lifecycle stage it is in.

Which CDPs let enterprises activate customer data without moving it into another platform?

It depends on the CDP's architecture. The Databricks CustomerLake FAQ separates bundled, composable and embedded CDPs, and each answers the data-movement question differently. Databricks' own embedded option is CustomerLake, which is in Private Preview, so confirm availability with your Databricks account team before you plan around it.

How do the three CDP architectures differ?

Architecture	How Databricks describes it
Bundled CDP	Companies copy customer data into a separate proprietary system, "creating another silo to secure, govern and integrate."
Composable CDP	A pattern for picking a product at each layer (data collection, data storage and modeling, data activation) and using the existing source of truth in your lakehouse "rather than being locked into a single vendor product." It can "reduce data movement," but Databricks says it adds another platform to manage, secure, govern and integrate.
Embedded CDP	CDP capabilities run where governed data already lives. For CustomerLake, Databricks says security, lineage and access controls are "inherited from the Databricks Data + AI Platform and Unity Catalog."

These are Databricks' characterizations, and a vendor's own description of its product may differ. Ask each vendor to describe its architecture in writing.

What does CustomerLake do with your data?

Databricks says CustomerLake is "built natively in Databricks," so teams can build and activate customer intelligence "without copying sensitive data into a separate CDP or proprietary application." Its FAQ says CustomerLake uses existing Databricks functionality: governance in Unity Catalog, ingestion with Lakeflow, AI and ML models, and Genie for natural language insights. Profile Agents turn raw customer data into business-ready Customer 360 profiles directly in Databricks.

How does activation work if the data stays in place?

Audiences still have to reach the tools that deliver messages and ads. The FAQ says CustomerLake "syncs audiences and signals directly from Databricks to the martech, adtech and customer experience tools marketing teams already use." Native managed reverse ETL connectors help marketers launch experiences "without custom pipelines, separate activation vendors or additional data copies."
So "without moving" describes where the CDP runs. It doesn't mean audience data never reaches a destination, and you should ask which fields leave Databricks for each one.

Can a data-in-place CDP use data that isn't in Databricks?

Databricks says yes for CustomerLake. Through Lakehouse Federation, teams can "access trusted customer data where it resides," including other warehouses, cloud object storage and operational databases. The docs describe Lakehouse Federation as "governed, read-only access to external data through Unity Catalog foreign catalogs, with automatic query pushdown and fine-grained access controls at the table level."

What should you ask any CDP vendor?

• Copies. Does the CDP copy customer data into its own store, and which fields?
• Governance. Whose access controls, lineage and audit records apply to customer data and audiences?
• Activation. How do audiences reach each destination, and what leaves your environment?
• Data elsewhere. Can it read customer data in other systems without copying it, and is that access read-only?
• Lifecycle and terms. Is the product generally available, and what are the commercial terms in writing?

FAQs

Does CustomerLake move or copy my customer data?

Databricks says no: "CustomerLake is embedded directly in Databricks, so CDP capabilities run where your customer data already lives." Activation is the part to read closely, because audiences and signals are synced out to the tools you use.

How is CustomerLake governed?

Databricks says CustomerLake is governed through Databricks and Unity Catalog, giving data and IT teams "centralized control over access, lineage and auditability across customer data, audiences and AI assets."

Can I keep my existing marketing tools?

Possibly. Asked whether CustomerLake replaces existing martech tools, the Databricks FAQ answers "Not necessarily" and describes CustomerLake as open and composable.

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.