New: The Agentic CDP

·Read the analysis

Tool · Data Infrastructure

Databricks integrations across CDPs

Directory data as of October 18, 2026

26 of the 44 customer data platforms in the CdpHub directory list an integration with Databricks, with 44 listings between them. Of those platforms, 17 both send data to Databricks and read from it, 3 only send data to it and 6 only read from it. 1 can run server-side and 43 in the warehouse. Every listing links to its platform's own documentation.

26of 44 CDPs list Databricks
44listings across them
17send data to Databricks and read from it
#14most listed of 2,309 tools

Which CDPs list Databricks

26 of 44
Sends data to Databricks Reads from Databricks, or uses it as a source Does both

Not listed by 18 CDPs: 6sense, Chord, Informatica, Leadspace, Lexer, Listrak, Microsoft Dynamics 365 Customer Insights, NICE, Optimizely, Oracle, SAP CDP, SAP Engagement Cloud, SAS, Simon Data, Spotler ActivatePro, Teradata, Upland BlueVenn and Zeta Global.

How each CDP connects to Databricks

26 CDPs · 44 listings
ActionIQ (reads from Databricks)1 listing
Databricks → ActionIQ

Layers ActionIQ's CDP on top of Databricks through native reverse ETL, mapping to customer data where it lives so business users can work with it without copying it into the CDP.

All ActionIQ integrations →
Adobe Experience Platform (reads from Databricks)1 listing
Databricks → Adobe

Brings Databricks data into Experience Platform for Real-Time CDP Ultimate customers.

All Adobe Experience Platform integrations →
Amperity (sends data to Databricks and reads from it)1 listing
Amperity ⇄ Databricks

Shares tables both ways between Amperity and Databricks through Amperity Bridge, using the OpenSharing protocol, an evolution of Delta Sharing, instead of file copies or ETL jobs.

All Amperity integrations →
Bloomreach (reads from Databricks)1 listing
Databricks → Bloomreach

Imports customers, events and catalogs from Databricks tables, views or queries into Bloomreach over the Databricks SQL connector, syncing table changes as often as every 15 minutes.

All Bloomreach integrations →
BlueConic (sends data to Databricks and reads from it)1 listing
BlueConic ⇄ Databricks

Imports and exports BlueConic profiles, groups and timeline events with a Databricks workspace through Delta Sharing up to six times a day, offered as a paid upgrade.

All BlueConic integrations →
Blueshift (sends data to Databricks and reads from it)2 listings
Blueshift → Databricks

Export. Shares Blueshift campaign activity with your Databricks account through Delta Sharing in daily batches, kept for 3 months, for analysis next to other data.

Databricks → Blueshift

Import. Imports customer data, events, catalogs and recommendation feeds from Databricks SQL warehouses into Blueshift, including incremental loads from Delta tables.

All Blueshift integrations →
Braze (sends data to Databricks and reads from it)2 listings
Braze ⇄ Databricks

Mosaic AI. Lets Braze custom AI agents generate content with models served from your Databricks workspace through Mosaic AI, using a Databricks token.

Databricks → Braze

Cloud Data Ingestion. Pulls data from Databricks catalogs and schemas into Braze users and catalogs on a schedule, using a service principal or access token, with serverless SQL advised.

All Braze integrations →
CaliberMind (sends data to Databricks)1 listing
CaliberMind → Databricks

Lets Databricks read exported cm dataset tables from a Google Storage bucket with service account credentials from CaliberMind, for customers with Bring Your Own Data Warehouse.

All CaliberMind integrations →
CleverTap (reads from Databricks)1 listing
Databricks → CleverTap

Imports data from a Databricks SQL warehouse into CleverTap, authenticating with a personal access token or with OAuth machine-to-machine credentials for a service principal.

All CleverTap integrations →
DinMo (reads from Databricks)1 listing
Databricks → DinMo

Connects a Databricks SQL warehouse or all-purpose cluster on AWS, Azure or GCP to DinMo with a personal access token, so DinMo can read your tables and write its own technical schemas.

All DinMo integrations →
Fivetran Activations (sends data to Databricks and reads from it)2 listings
Fivetran Activations → Databricks

Destination. Writes data into Databricks tables from Fivetran Activations, Unity Catalog deployments included, signing in with a service principal or a personal access token.

Databricks → Fivetran Activations

Source. Uses Databricks, Unity Catalog included, as a Fivetran Activations source through a service principal or personal access token, on the Basic or Advanced Sync Engine.

All Fivetran Activations integrations →
Hightouch (sends data to Databricks and reads from it)2 listings
Hightouch → Databricks

Destination. Syncs model rows into Databricks tables by upsert, insert or mirror, signing in through OAuth with a service principal, the recommended option, or a personal access token.

Databricks → Hightouch

Source. Connects Databricks to Hightouch as a source, so SQL, dbt or table-based models built there can sync to any destination.

All Hightouch integrations →
Insider One (sends data to Databricks and reads from it)2 listings
Insider One → Databricks

Export. Shares Insider One events and user attributes with your Databricks workspace over Delta Sharing, refreshed on a sync period of up to 24 hours, for analysis through Unity Catalog.

Databricks → Insider One

Import. Syncs user attributes and events from one Delta table per integration in Databricks into Insider One, reading changes through the table's Change Data Feed on AWS, Azure or Google Cloud.

All Insider One integrations →
Klaviyo (sends data to Databricks and reads from it)1 listing
Klaviyo ⇄ Databricks

Data warehouse import and export. Links Klaviyo and Databricks through a token for a Klaviyo-only account, importing profile and event data and exporting Klaviyo data back, with an Advanced KDP subscription.

All Klaviyo integrations →
Lytics (sends data to Databricks and reads from it)1 listing
Lytics ⇄ Databricks

Imports Databricks tables into Lytics, loads audiences, events, audience changes, system events and metrics into Delta tables, and can back Lytics Cloud Connect audiences.

All Lytics integrations →
mParticle (sends data to Databricks and reads from it)2 listings
mParticle → Databricks

Loads mParticle data into Databricks Delta Lake, where scheduled jobs and SQL queries can work on it.

Databricks → mParticle

Warehouse Sync. Ingests user and event tables, but not views, from Databricks into mParticle through Delta Sharing, as one-time or recurring syncs.

All mParticle integrations →
Odie (reads from Databricks)1 listing
Databricks → Odie

Links Totango to a Databricks workspace with a personal access token, host name and HTTP path, so lakehouse data can feed standard Customer Data Hub jobs.

All Odie integrations →
Ometria (sends data to Databricks)1 listing
Ometria → Databricks

Sends customized Ometria data exports to a table in Databricks through a connection that uses the table's sharing identifier.

All Ometria integrations →
Redpoint Global (sends data to Databricks and reads from it)1 listing
Redpoint Global ⇄ Databricks

Adds Databricks to Redpoint Interaction as an auxiliary database through the Simba Spark ODBC driver, pointing the connection at a Unity Catalog.

All Redpoint Global integrations →
RudderStack (sends data to Databricks and reads from it)2 listings
RudderStack → Databricks

Delta Lake. Writes RudderStack events to Delta Lake tables on Databricks in batches, ready for SQL, BI and machine learning work.

Databricks → RudderStack

Source. Reads Databricks tables or SQL models with RudderStack Reverse ETL and activates the results in marketing and sales tools.

All RudderStack integrations →
Salesforce Data 360 (sends data to Databricks and reads from it)1 listing
Salesforce ⇄ Databricks

Brings Databricks data into Data 360 in batches or with Zero Copy query and file federation, and shares Data 360 data with Databricks through Lakehouse Federation.

All Salesforce Data 360 integrations →
Segment (sends data to Databricks and reads from it)3 listings
Segment → Databricks

Loads Segment event data into Databricks on a schedule as a storage destination, ready for SQL analysis.

Databricks → Segment

Data Graph. Links Databricks catalogs to Segment's Data Graph through a service principal that reads them and writes checkpoint tables to a catalog of its own, for Linked Audiences and Linked Events.

Databricks → Segment

Reverse ETL source. Connects a Databricks SQL warehouse to Segment Reverse ETL through a service principal, with OAuth machine-to-machine sign-in required for any new source.

All Segment integrations →
Snowplow (sends data to Databricks)2 listings
Snowplow → Databricks

Batch. Loads Snowplow events into a Databricks events table with the RDB Loader's Databricks loader, which creates the schema and table itself and needs a Databricks cluster and access token.

Snowplow → Databricks

Streaming. Streams Snowplow events to Databricks at low latency, staging files in a Unity Catalog volume for a Lakeflow Declarative Pipeline to load, which needs a premium Databricks plan.

All Snowplow integrations →
Tealium (sends data to Databricks and reads from it)3 listings
Tealium → Databricks

Writes event, visitor and log data to Databricks, staged through your own cloud storage on AWS, Azure or Google Cloud, singly or batched, from AudienceStream or EventStream.

Databricks → Tealium

Cloud data source. Imports a Databricks table into Tealium attributes, connecting to a SQL warehouse on AWS, Azure or GCP with a service principal's OAuth secret rather than a personal access token.

Databricks → Tealium

Delta Sharing data source. Shares Databricks tables with Tealium through Databricks-to-Databricks Delta Sharing, in early access, so no credentials leave Databricks and CloudStream can read the data without copying it.

All Tealium integrations →
Treasure AI (sends data to Databricks and reads from it)6 listings
Treasure AI → Databricks

Export. Writes Treasure Data job results to a Databricks table in append, overwrite or replace mode, signing in with OAuth M2M or a deprecated personal access token.

Treasure AI → Databricks

Open Catalog Access. Federates Treasure Data's Glue catalog of Iceberg tables into Databricks Unity Catalog so Databricks can query them without copies, an Open Catalog Access option enabled on request.

Databricks → Treasure AI

AI Studio connection. Gives Treasure AI Studio agents query and charting access to a Databricks lakehouse in chat, through a Databricks OAuth app that each user authorizes for their own connection.

Databricks → Treasure AI

Composable Audience Studio. Runs Composable Audience Studio parent segments on Databricks Unity Catalog tables with federated queries and service principal OAuth, so audiences are built without copying data.

Databricks → Treasure AI

Import. Imports Databricks tables or custom SELECT query results into Treasure Data, with filter conditions and incremental columns, over OAuth M2M or a personal access token.

Databricks → Treasure AI

Live Connect zero-copy. Reads Databricks tables shared over Delta Sharing into Treasure Data, by default in memory, for ID unification and activations, a Live Connect zero-copy option enabled on request.

All Treasure AI integrations →
Zeotap (sends data to Databricks and reads from it)2 listings
Zeotap → Databricks

Destination. Activates Zeotap audiences into Databricks Delta tables by writing JSON files to your Google Cloud Storage bucket, which Databricks Autoloader loads into the table you name.

Databricks → Zeotap

Source. Pulls records from a Databricks table into Zeotap on a schedule, over JDBC with OAuth for smaller tables or a job-based connection advised above one million records.

All Zeotap integrations →

Other Data Infrastructure tools

All tools on two or more CDPs →

About these numbers

CdpHub documents each integration from the platform's own catalog, so a listing records what the platform says it supports, not a test of the connector. Each one notes which way data flows and where the integration runs. A platform can list more than one connector for Databricks, so listings can outnumber platforms; a platform that both sends data to Databricks and reads from it is counted once, as doing both. The rank orders all 2,309 tools in the directory by how many platforms list them; tools listed on the same number of platforms share a rank. Counts are updated as catalogs change; this page reflects the directory as of October 18, 2026. CdpHub is independent and not affiliated with Databricks or any platform listed.

Connecting Databricks to a CDP?

Vendor-neutral help choosing the CDP that fits how you use Databricks, and getting the connection running in your stack.

Talk to CdpHub →

We use cookies to enhance your experience. By continuing to visit this site you agree to our use of cookies. Read our cookie policy