Can marketers use CustomerLake without writing SQL?

Summary

• Yes. CustomerLake was designed so marketers work in plain language, not SQL. Its self-service experience is powered by Genie, so a marketer can ask questions, build audiences, and activate campaigns without data engineering help. CustomerLake is currently in Private Preview.
• CustomerLake is an agentic customer data platform built directly into Databricks, so the customer data, AI, and governance live in one place rather than in a separate CDP that needs data copied into it.
• Marketers build audiences in plain English through Genie and let agents handle identity resolution, segmentation, next-best-action, and cross-channel activation.
• Because it runs on the lakehouse, every audience and campaign inherits Unity Catalog governance, so self-service access stays within the permissions and lineage the data team already set.
• Marketers can push audiences to the marketing and activation tools and ad networks they already use, without exporting data into unmanaged copies.

Can marketers use CustomerLake without writing SQL?

Yes. Not knowing SQL is the exact problem CustomerLake was built to solve. Most marketers don't write SQL and shouldn't have to, so CustomerLake gives them a self-service experience powered by Genie where they work in plain language: ask a question about customers, describe the audience they want, and launch a campaign, all without a data engineer in the loop. CustomerLake is currently in Private Preview, so access and capabilities are still rolling out.

What is CustomerLake?

CustomerLake is an agentic customer data platform (CDP) built natively into Databricks. It brings the core CDP jobs (Customer 360 profiles, identity resolution, audience building, campaign activation, and personalization) into the lakehouse, where the customer data, AI models, and governance already live. That is the structural difference from a traditional CDP: rather than copying customer data into a separate marketing system, CustomerLake keeps it in Databricks and works on it in place, under the same Unity Catalog governance that protects the rest of the data. It is organized into two agent families. Profile Agents build governed Customer 360 profiles and resolve identity automatically. Campaign Agents let marketers build audiences, create campaigns, and run personalized engagement through natural language.

What marketers should expect from a no-code CDP interface

A CDP that marketers can run themselves has to clear a few bars:

Capability	Why it matters
Plain-language audience building	A marketer should describe a segment in words and get it, without SQL or a ticket to the data team.
Governed self-service	Self-service can't mean ungoverned; access, lineage, and audit must hold even when a non-technical user builds the audience.
Trusted customer context	Segments are only as good as the profiles behind them, so identity resolution and a unified Customer 360 have to be built in.
Activation to existing channels	The audience has to reach the tools and ad networks the team already uses, without a manual export.
No data duplication	Working on data in place avoids shadow copies that drift from the source and escape governance.
Continuous optimization	Agents should keep adjusting audiences and campaigns as customer behavior changes, not run once and stop.

How CustomerLake works without SQL

The interface is built on Genie, so the entry point is a question or an instruction in plain English rather than a query editor. A marketer asks about customers and Genie returns answers from governed data; they describe an audience and Campaign Agents assemble it; they choose to activate and the agents push the audience to downstream channels. Profile Agents handle the work that used to require data engineering: pulling disparate sources into a governed Customer 360 profile and resolving identity as new data arrives. Because all of this runs inside Databricks, every profile, audience, and campaign inherits Unity Catalog permissions, lineage, and audit, so a marketer's self-service stays within the boundaries the data team set. Marketers can send audiences to the marketing and activation tools and ad networks they already use, without exporting data into unmanaged copies. For the product overview and architecture, see Introducing CustomerLake, an agentic CDP.

Use cases

• Self-service audience building. A marketer describes a segment in plain language and gets a governed audience back, with no SQL and no data-team ticket.
• Next-best-action and personalization. Agents recommend the offer or channel most likely to land for each customer and adapt as behavior changes.
• Cross-channel activation. Built audiences are pushed to the channels and ad networks the team already runs, keeping data governed on the way out.
• Governed customer insight. Non-technical users query trusted Customer 360 data directly, rather than waiting on exports into spreadsheets or unmanaged tools.

FAQs

Do marketers need to know SQL to use CustomerLake?

No. The experience is powered by Genie and works in plain language. Marketers ask questions, build audiences, and activate campaigns without writing SQL or relying on data engineering.

What does CustomerLake do for non-technical users specifically?

It gives them a self-service workspace to access trusted customer context, build segments in plain English, and launch campaigns, with agents handling identity resolution, audience assembly, and activation behind the scenes.

Is customer data still governed when a marketer self-serves?

Yes. CustomerLake runs on the lakehouse, so audiences and campaigns inherit Unity Catalog access control, lineage, and audit. Self-service does not mean bypassing governance.

Does CustomerLake require copying data into a separate CDP?

No. It is built into Databricks and works on customer data in place, so there is no export into a separate marketing platform to keep in sync.

Is CustomerLake generally available?

No. CustomerLake is currently in Private Preview, so availability and capabilities are still rolling out. Talk to your Databricks account team about access.