New: The Agentic CDP

·Read the analysis

Connect · Data warehouse

Klaviyo to Databricks

Directory data as of October 23, 2026

Klaviyo's own catalog lists Databricks, moving data both ways (1 listing). Beyond that, 6 of the 44 CDPs in the CdpHub directory list both a connector that reads from Klaviyo and one that sends data to Databricks, so they can sit between the two, and 13 go the other way, from Databricks to Klaviyo.

6CDPs can carry Klaviyo data into Databricks
13CDPs can carry Databricks data to Klaviyo
1Databricks listing in Klaviyo's own catalog
26of 44 CDPs list Databricks

Klaviyo's own Databricks integration

1 listing

Klaviyo is one of the CDPs in the directory, and its own catalog lists Databricks: the two connect directly, with no other platform in between.

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 →

CDPs that can carry Klaviyo data into Databricks

6 CDPs

Each of these CDPs lists a connector that reads from Klaviyo and one that sends data to Databricks. A route is a possible path, not a tested one: what travels depends on each connector, so check the documentation links.

  • Reads from Klaviyo

    Klaviyo → Amperity

    Source. Pulls email and SMS engagement metrics and list membership from Klaviyo into Amperity through its events API.

    Sends to Databricks

    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.

  • Reads from Klaviyo

    BlueConic ⇄ Klaviyo

    Pulls changed Klaviyo profiles and their events into BlueConic and exports segment profiles to Klaviyo in scheduled batches with an API key, once BlueConic installs the connection.

    Sends to Databricks

    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.

  • Reads from Klaviyo

    Klaviyo → Insider One

    Brings Klaviyo profiles, events and subscription updates into Insider One with a private API key, running each of the three incremental syncs on its own schedule.

    Sends to Databricks

    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.

  • Reads from Klaviyo

    Lytics ⇄ Klaviyo

    Adds Lytics audience members to Klaviyo lists in real time and imports Klaviyo profiles with campaign activity such as opens and clicks into Lytics every hour.

    Sends to Databricks

    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.

  • Reads from Klaviyo

    Klaviyo → Segment

    Source. Sends Klaviyo events into Segment as they happen, ready to route to other tools.

    Sends to Databricks

    Segment → Databricks

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

  • Reads from Klaviyo

    Klaviyo → Treasure AI

    Import. Imports Klaviyo metrics, events, profiles and list members into Treasure Data with a private API key, using only Klaviyo's stable API.

    Sends to Databricks

    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.

The other way: Databricks to Klaviyo

13 CDPs

Each of these CDPs lists a connector that reads from Databricks and one that sends data to Klaviyo.

  • Reads from Databricks

    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.

    Sends to Klaviyo

    ActionIQ → Klaviyo

    Klaviyo

  • Reads from Databricks

    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.

    Sends to Klaviyo

    Amperity → Klaviyo

    Destination. Keeps Klaviyo lists matched to Amperity queries by email and updates profile properties through Klaviyo's REST API.

  • Reads from Databricks

    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.

    Sends to Klaviyo

    Bloomreach ⇄ Klaviyo

    Imports Klaviyo profiles daily and consent and campaign events every two hours into Bloomreach, and sends Bloomreach segments and consent to Klaviyo lists by webhook, where enabled.

  • Reads from Databricks

    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.

    Sends to Klaviyo

    BlueConic ⇄ Klaviyo

    Pulls changed Klaviyo profiles and their events into BlueConic and exports segment profiles to Klaviyo in scheduled batches with an API key, once BlueConic installs the connection.

  • Reads from Databricks

    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.

    Sends to Klaviyo

    DinMo → Klaviyo

    Contact lists. Keeps Klaviyo lists aligned with DinMo segments, adding and removing existing profiles by email, phone or Klaviyo ID while updating their existing profile attributes.

    DinMo → Klaviyo

    Contacts. Creates and updates Klaviyo profiles from DinMo segments by email, phone or Klaviyo ID, including new custom attributes, and stops updating people who leave the segment.

    DinMo → Klaviyo

    Profile events. Sends new rows of a DinMo event model to Klaviyo profiles as events, linked by email or phone, carrying event time, value, currency, an event ID and custom properties.

    DinMo → Klaviyo

    Subscriptions. Opts existing Klaviyo profiles into email, SMS or both as they join a DinMo segment and out when they leave, using a double opt-in list unless you set it to single opt-in.

  • Reads from Databricks

    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.

    Sends to Klaviyo

    Fivetran Activations → Klaviyo

    Upserts Klaviyo profiles, mirrors list membership and sends events from Fivetran Activations, using a private API key plus the public key or site ID.

  • Reads from Databricks

    Databricks → Hightouch

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

    Sends to Klaviyo

    Hightouch → Klaviyo

    Creates and updates Klaviyo profiles from purchases, signups and other warehouse data for e-commerce email.

  • Reads from Databricks

    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.

    Sends to Klaviyo

    Lytics ⇄ Klaviyo

    Adds Lytics audience members to Klaviyo lists in real time and imports Klaviyo profiles with campaign activity such as opens and clicks into Lytics every hour.

  • Reads from Databricks

    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.

    Sends to Klaviyo

    mParticle → Klaviyo

    Audiences. Keeps Klaviyo lists in step with mParticle audiences, adding and removing members as they change.

    mParticle → Klaviyo

    Events. Sends mParticle events and profile data to Klaviyo through its Create Event API, for email and SMS flows.

  • Reads from Databricks

    Databricks → RudderStack

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

    Sends to Klaviyo

    RudderStack → Klaviyo

    Bulk upload. Bulk-loads customer profiles from your warehouse into Klaviyo with RudderStack Reverse ETL, creating or updating them for segmentation and flows.

    RudderStack → Klaviyo

    Events. Sends RudderStack profiles and events to Klaviyo for ecommerce email and SMS flows, in cloud mode or on the web in device mode.

  • Reads from Databricks

    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.

    Sends to Klaviyo

    Segment → Klaviyo

    Actions. Sends Segment data to Klaviyo through Actions such as Upsert Profile, Order Completed and Track Event.

    Segment → Klaviyo

    Classic. Sends identify and track calls from Segment to Klaviyo for email marketing in cloud or device mode.

  • Reads from Databricks

    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.

    Sends to Klaviyo

    Tealium → Klaviyo

    Creates and updates Klaviyo profiles and attributes and adds users to or removes them from lists, in real time or batched, from AudienceStream.

  • Reads from Databricks

    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.

    Sends to Klaviyo

    Treasure AI → Klaviyo

    Export. Adds Treasure Data profiles to Klaviyo lists or removes them and records email or SMS marketing consent with a private API key, through a connector listed as beta.

Get an email when these routes change

CdpHub Pro will alert you when a CDP adds, renames or retires a connector between Klaviyo and Databricks. Join the waitlist for early access.

Join the Pro waitlist →

Klaviyo and the other warehouses

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. A route counts a CDP that lists a connector reading from one end and another sending data to the other: a possible path, not a tested one. What travels, how often and in which format depends on each connector and its plan, so follow the documentation links. Klaviyo is a CDP in the directory too, so its own listings for Databricks come first. Counts are updated as catalogs change; this page reflects the directory as of October 23, 2026. CdpHub is independent and not affiliated with Klaviyo, Databricks or any platform listed.

Getting Klaviyo data into Databricks?

Vendor-neutral help choosing the route that fits your stack, and getting the connection running.

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

C
CdpHub × LiveAvatar
Early Access: CdpHub's AI guide draws from our integration directory but may occasionally provide incomplete or inaccurate information. We're actively improving it — your patience and feedback are appreciated. When you use the mic, your voice is transcribed so Ed can answer.
Ed, CdpHub's AI guide

CdpHub · Powered by Claude + LiveAvatar

Ask Ed