Databricks on Databricks: Marketing with CustomerLake, the new Agentic CDP
Overview
| Experience | In Person |
|---|---|
| Track | Customer Data Platform (CDP) |
| Industry | Enterprise Technology |
| Technologies | Lakeflow, Databricks Agents |
| Skill Level | Intermediate |
| DOWNLOAD SESSION SLIDES | |
In this marketing practitioner deep dive, the Databricks Marketing Technology and Engineering teams walk through how we built and launched a fully agentic, embedded CDP on the Lakehouse — and used it to automate real marketing campaigns that are already in-market.
We’ll reverse-engineer the live demo you saw during the keynote, and show how onboarding, segmentation, activation, execution, and performance insights are carried out by the Databricks Marketing Team. Attendees will see how agents interact with governed data, how automation layers plug into the Lakehouse, and how marketers can deploy campaigns without fragile point-solution tooling.
Session Speakers
Melanie Chow
/Senior Software Engineer
Databricks
Paul Volk
/Marketing Technology Solution Architect
Databricks
Full Summary
Inside Databricks on Databricks: How agentic marketing replaces the 8-week campaign
Databricks' marketing team shares how unifying data on the Databricks Platform solved analytics but not execution, and why they built Databricks Customer Lake to close that gap. The session argues that centralized data is only a prerequisite, and that the real unlock comes from agentic campaign execution that lets marketers and data teams work in one loop, not through tickets and handoffs. Customer Lake, embedded in the Databricks Platform for customer data, aims to compress an eight-week campaign cycle into a single collaborative workflow. Teams exploring how this fits into a broader stack will find the case for agentic analytics as the next frontier of data-driven marketing directly relevant to the execution bottlenecks discussed throughout the session.
FAQ
Customer Lake is an agentic customer data platform embedded in the lakehouse on the Databricks Platform. It uses the same tables data teams already maintain, pairs marketer-facing tools with agents for planning, audience building, content support, and activation, and keeps governance, lineage, and query logs in place.
Traditional CDPs sit outside the data platform and require copying sensitive data. Customer Lake runs inside the lakehouse, so data is not duplicated, governance is native, audiences register in Unity Catalog for analysis, and activation is channel agnostic with logged, auditable syncs.
No. Marketers set goals, frequency caps, suppressions, quiet hours, and content standards. Agents surface assumptions, show sources and reasoning, and keep humans in the loop for review and approval before launch.
For most use cases, yes. The speakers argue many teams struggle to adopt reinforcement learning or bandits due to cost, tuning time, and opacity. LLM-based agents can handle the bulk of decisions while still allowing teams to plug in models where needed.
Customer Lake is in private preview with design partners. Pricing will be consumption-based rather than a traditional software license fee.