Which martech and adtech tools integrate with CustomerLake?

Summary

• CustomerLake Campaign Agents deliver audiences to two documented kinds of destinations: advertising destinations, which activate audiences across ad platforms, and marketing engagement destinations, which activate audiences across channels.
• Databricks describes these as "the martech, adtech and customer experience tools your teams already use," and the Deliver data downstream page in the CustomerLake documentation lists the available destinations by name.
• Each destination uses a connector, which stores the credentials for one destination account, and a sync, which maps your fields to the destination's fields and runs on demand or on a schedule.
• Connector rules, CustomerLake roles, and email alerts control and monitor what each sync sends.
• CustomerLake is a preview product: Databricks announced it in Private Preview on June 16, 2026, and documents Campaign Agents as Beta.

Which martech and adtech tools integrate with CustomerLake?

CustomerLake Campaign Agents deliver audiences to advertising destinations and marketing engagement destinations. The documentation says advertising destinations "activate audiences across ad platforms" and marketing engagement destinations "activate audiences across channels." The CustomerLake product page says audiences sync "to the martech, adtech and customer experience tools your teams already use." The Deliver data downstream page in the CustomerLake documentation lists each available destination by name, so check it, or ask your Databricks account team, for a specific tool.

What is CustomerLake Campaign Agents?

CustomerLake is "an agentic customer data platform (CDP) embedded in Databricks." Campaign Agents are the component that marketing and data teams use to build audiences from data governed by Unity Catalog and activate those audiences to marketing and advertising platforms. Databricks announced CustomerLake in Private Preview on June 16, 2026. The documentation labels CustomerLake Campaign Agents Beta, and a workspace admin turns it on from the Previews page.

What kinds of integrations does CustomerLake document?

Integration type	What the documentation or product page says
Advertising destinations	Connect to advertising destinations to activate audiences across ad platforms
Marketing engagement destinations	Connect to marketing engagement destinations to activate audiences across channels
Source data	Campaign Agents read Unity Catalog tables, including managed, external, and federated tables, views, and materialized views
Data ingestion	The product page lists "ingestion with Lakeflow" among the Databricks functionality CustomerLake uses. Lakeflow Connect organizes managed connectors by source type (database, SaaS, file, and streaming), and its docs say connectors are in various release states.
Third-party data and identity	The product page lists a Third-Party Identity Hub that enriches profiles with third-party data and identity graphs through Databricks-managed integrations

How does an integration work in CustomerLake?

Delivery takes two objects:

• Connector. It stores the credentials for one destination account. You enter the credentials or sign in to the destination, the credentials are stored encrypted, and many syncs can reuse the same connector. One destination can have multiple connectors, such as production and staging.
• Sync. It sends an audience to a destination through a connector. You choose the audience, the connector, and the destination asset, such as users, a list, or a segment. You then map your fields to the destination's fields and run the sync on demand or on a schedule.

Each run reconciles the destination with the current audience. It adds new members, updates members whose mapped fields changed, and, where the destination supports it, removes members who left the audience. Syncs do not remove global objects, such as customer profiles, from a destination. Use the destination's own tools for that.

What controls apply to data sent to a destination?

A connector rule uses an audience to allow or block members before any rows reach the destination, for example to suppress members who opted out of marketing. CustomerLake roles divide the work: a Connector Admin manages connector credentials, destination configuration, and connector rules, and a Sync Operator configures and runs syncs with existing connectors. A CustomerLake role does not grant Unity Catalog access to the underlying data, and role assignments are not enforced until role enforcement is enabled for your workspace. Each sync run has a detail page with its start time, duration, trigger, and total, success, and failure counts, and the row inspector shows both successful and failed records. Email alerts cover failed sync runs, rejected rows, long-running syncs, and unhealthy connectors.
The documentation also warns that connectors send data outside the Databricks environment to external services that Databricks does not provide. Those services are subject to separate terms from their providers.

FAQs

Do I have to replace my existing martech tools to use CustomerLake?

Not necessarily. The product page says CustomerLake is "open and composable, and designed to work with the marketing, advertising, analytics, and customer experience tools teams already use."

Can one audience go to several destinations?

Yes. The documentation describes defining a single segment and syncing it to an email platform and multiple advertising networks at the same time, so the same audience stays consistent across every destination.

What does a sync send?

A sync sends the members of an audience, with your fields mapped to the fields the destination expects. A connector rule can filter the audience first.

Who can connect a destination?

By default, only workspace admins can access CustomerLake Campaign Agents. They assign roles to other users and account groups, and managing connector credentials and destination configuration takes the Connector Admin role.

Is CustomerLake generally available?

No. Databricks announced it in Private Preview on June 16, 2026, and the documentation labels CustomerLake Campaign Agents Beta.