Databricks CustomerLake is a customer data platform (CDP) embedded in the Databricks Lakehouse. The product creates unified customer profiles, resolves identities, builds audience segments, and activates customer data across marketing and advertising systems without requiring a separate CDP data store.

CustomerLake uses software agents to assist with profile preparation, audience creation, campaign execution, and personalization. Customer data, predictive models, business rules, and marketing workflows remain subject to the governance controls of the underlying Databricks environment.

Key Capabilities

Customer 360 Profiles: CustomerLake combines transactional, behavioral, product usage, commerce, loyalty, support, operational, and third-party data into consolidated customer records.
Agentic Identity Resolution: The product uses deterministic rules, probabilistic models, and agent-assisted workflows to link identifiers and merge records associated with the same customer.
Profile Agents: These agents prepare source data, identify data-quality issues, support third-party enrichment, and convert raw records into business-ready customer profiles.
Audience Segmentation: Marketing teams can define audience groups using governed customer attributes, behavioral signals, predictive models, eligibility requirements, and other business rules.
Campaign Agents: These agents assist with audience selection, recommend next-best actions, activate campaigns across connected channels, and adjust campaign decisions based on performance signals and defined objectives.
Cross-Channel Activation: Customer profiles, audiences, and related signals can be sent to advertising, marketing automation, and customer engagement platforms through native integrations and reverse extract, transform, load (reverse ETL) pipelines.
Personalization: CustomerLake uses customer context and business constraints to select content, offers, channels, or actions for individual customers.
Federated Data Access: Lakehouse Federation allows the product to query customer data held in Databricks, Snowflake, Google BigQuery, cloud object storage, operational databases, and other supported systems.
Data Governance: Unity Catalog applies access controls, lineage, discovery, and governance policies to the data and models used by CustomerLake.
Human-Defined Controls: Marketing and data teams establish campaign goals, strategies, eligibility rules, and operational guardrails. Software agents perform supported execution and optimization tasks within those constraints.

Audience & Use Cases

Audience: CustomerLake is intended for enterprise marketing teams, customer analytics teams, data engineers, data scientists, and marketing technology administrators using Databricks.
Use Cases: The product supports customer profile unification, identity resolution, audience development, customer segmentation, campaign activation, next-best-action recommendations, cross-channel personalization, and continuous campaign adjustment.

Technical Specifications

Product Type: Customer data platform
Deployment Model: Embedded in the Databricks Lakehouse
Core Agent Types: Profile Agents and Campaign Agents
Governance Layer: Unity Catalog
External Data Access: Lakehouse Federation
Data Movement: Native integrations and bidirectional reverse ETL pipelines
Identity Methods: Deterministic, probabilistic, and agent-assisted resolution
Supported Data Locations: Databricks, Snowflake, Google BigQuery, cloud object storage, operational databases, and supported enterprise systems
Integration Areas: Identity, audience activation, measurement, advertising, and customer engagement

Databricks CustomerLake

What is Databricks CustomerLake?

Categories & Use Cases

Databricks CustomerLake Alternatives