New: The Agentic CDP

·Read the analysis

Connect · Data warehouse

Klaviyo to Snowflake

Directory data as of October 23, 2026

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

9CDPs can carry Klaviyo data into Snowflake
15CDPs can carry Snowflake data to Klaviyo
2Snowflake listings in Klaviyo's own catalog
35of 44 CDPs list Snowflake

Klaviyo's own Snowflake integrations

2 listings

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

Klaviyo → Snowflake

Pushes Klaviyo profiles and events into a Snowflake instance, letting you choose either or both and filter out events from integrations already sending to Snowflake.

Snowflake → Klaviyo

Data warehouse import. Imports profile and event data from Snowflake tables or views into Klaviyo on a schedule through a key-pair user, with a Klaviyo Advanced KDP subscription.

All Klaviyo integrations →

CDPs that can carry Klaviyo data into Snowflake

9 CDPs

Each of these CDPs lists a connector that reads from Klaviyo and one that sends data to Snowflake. 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 Snowflake

    Amperity ⇄ Snowflake

    Shares data both ways between Amperity and Snowflake through Amperity Bridge, using Snowflake Secure Data Sharing so nothing is copied or exported.

  • Reads from 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.

    Sends to Snowflake

    Bloomreach ⇄ Snowflake

    Imports Snowflake customers, events and catalogs into Bloomreach over a key-pair connection with change-tracking syncs, and covers loading Bloomreach exports into Snowflake via Google Cloud Storage.

  • 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 Snowflake

    BlueConic ⇄ Snowflake

    Moves profiles and timeline events between BlueConic and Snowflake in batches via an S3 or GCS bucket or Secure Data Sharing, which adds groups, and imports profiles in real time.

  • Reads from Klaviyo

    Klaviyo → Chord

    Source. Ingests Klaviyo flows, campaigns, metrics, lists, segments and events into Chord with a read-only private API key, while profile tables stay off unless Chord enables them.

    Sends to Snowflake

    Chord → Snowflake

    Outbound share. Delivers a brand's raw and transformed Chord data to its own Snowflake account as a private listing, with Chord covering replication costs for a yearly maintenance fee.

  • 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 Snowflake

    Insider One → Snowflake

    Export. Shares Insider One engagement events and user data with your Snowflake account through a data share that syncs as often as you set, up to 24 hours, with one export per account.

  • 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 Snowflake

    Lytics ⇄ Snowflake

    Loads Snowflake tables or views into Lytics and exports events, full audiences, audience changes and platform metrics to Snowflake tables in batches.

  • Reads from Klaviyo

    Klaviyo → Segment

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

    Sends to Snowflake

    Segment → Snowflake

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

  • Reads from Klaviyo

    Simon Data ⇄ Klaviyo

    Keeps Klaviyo lists in step with Simon Data segments, sends custom events with properties that can start Klaviyo flows or campaigns, and adds contacts to Klaviyo's global exclusions.

    Sends to Snowflake

    Simon Data → Snowflake

    Outbound share. Gives your Snowflake account read-only access to Simon Data results, such as flow adds and actions, events and the customer table, through a Snowflake share for BI reporting.

    Simon Data ⇄ Snowflake

    Connected deployment. Runs Simon Data on your own Snowflake account in a Connected deployment, reading the tables you grant to a dedicated role and building its own schemas, views and tasks in a database you create.

  • 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 Snowflake

    Treasure AI → Snowflake

    Export. Writes Treasure Data job results to a Snowflake table, creating it when needed and optionally adding missing columns, under a chosen Snowflake role.

    Treasure AI → Snowflake

    Open Catalog Access. Lets Snowflake read Treasure Data's Iceberg tables in place through a catalog-linked database on the AWS Glue Iceberg REST catalog, with no copies, once Open Catalog Access is enabled.

The other way: Snowflake to Klaviyo

15 CDPs

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

  • Reads from Snowflake

    Snowflake → ActionIQ

    Uses customer data where it sits in Snowflake, with no migration project, so Snowflake customers can activate it across marketing channels from ActionIQ's composable CDP.

    Sends to Klaviyo

    ActionIQ → Klaviyo

    Klaviyo

  • Reads from Snowflake

    Amperity ⇄ Snowflake

    Shares data both ways between Amperity and Snowflake through Amperity Bridge, using Snowflake Secure Data Sharing so nothing is copied or exported.

    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 Snowflake

    Bloomreach ⇄ Snowflake

    Imports Snowflake customers, events and catalogs into Bloomreach over a key-pair connection with change-tracking syncs, and covers loading Bloomreach exports into Snowflake via Google Cloud Storage.

    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 Snowflake

    BlueConic ⇄ Snowflake

    Moves profiles and timeline events between BlueConic and Snowflake in batches via an S3 or GCS bucket or Secure Data Sharing, which adds groups, and imports profiles in real time.

    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 Snowflake

    Snowflake → Chord

    Inbound share. Shares database objects from a brand's Snowflake account with Chord through a direct share in the same region or a private listing that Snowflake replicates across regions.

    Sends to Klaviyo

    Chord → Klaviyo

    Events. Sends Chord track events that include an email or phone to Klaviyo and upserts profiles from identify calls, using a private API key with Events write access.

  • Reads from Snowflake

    Snowflake → DinMo

    Connects Snowflake to DinMo with a service user, key pair authentication and a dedicated warehouse, feeding models, segments and predictions and writing DinMo tables to a dedicated Snowflake database.

    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 Snowflake

    Snowflake → Fivetran Activations

    Source. Reads Snowflake tables and views for Fivetran Activations syncs through a dedicated user, role and compute warehouse, with key-pair sign-in recommended over deprecated passwords.

    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 Snowflake

    Snowflake → Hightouch

    Iceberg source. Reads Apache Iceberg tables managed in Snowflake as a Hightouch source.

    Snowflake → Hightouch

    Source. Connects Snowflake to Hightouch as a source, with models built in SQL, dbt, Looker, Sigma, a table selector or Customer Studio.

    Sends to Klaviyo

    Hightouch → Klaviyo

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

  • Reads from Snowflake

    Lytics ⇄ Snowflake

    Loads Snowflake tables or views into Lytics and exports events, full audiences, audience changes and platform metrics to Snowflake tables in batches.

    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 Snowflake

    Snowflake → mParticle

    Warehouse Sync. Pulls user attributes and events from Snowflake tables into mParticle in single, on-demand or repeating runs, signing in as a dedicated user with a key pair.

    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 Snowflake

    Snowflake → RudderStack

    Source. Activates Snowflake tables, SQL models and audiences in downstream tools with RudderStack Reverse ETL.

    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 Snowflake

    Snowflake → Segment

    Data Graph. Connects Snowflake to Segment's Data Graph through a key-pair user that reads warehouse entities for Linked Audiences and Linked Events, on the Business tier.

    Snowflake → Segment

    Reverse ETL source. Runs Reverse ETL model queries in Snowflake and syncs the results to Segment destinations, with key-pair sign-in only (Segment marks it as in active development).

    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 Snowflake

    Simon Data ⇄ Snowflake

    Connected deployment. Runs Simon Data on your own Snowflake account in a Connected deployment, reading the tables you grant to a dedicated role and building its own schemas, views and tasks in a database you create.

    Snowflake → Simon Data

    Inbound share. Brings Snowflake tables into Simon Data through a secure data share you create and grant to Simon's Snowflake account, an optional premium feature arranged with your account manager.

    Sends to Klaviyo

    Simon Data ⇄ Klaviyo

    Keeps Klaviyo lists in step with Simon Data segments, sends custom events with properties that can start Klaviyo flows or campaigns, and adds contacts to Klaviyo's global exclusions.

  • Reads from Snowflake

    Snowflake → Tealium

    Audience Discovery app. Builds audiences inside Snowflake with Tealium's native Snowflake app, using point-and-click filters or Cortex queries, then loads them into Tealium through a Snowflake data source.

    Snowflake → Tealium

    Cloud data source. Polls chosen Snowflake tables or views into Tealium attributes, connecting with a custom role that has USAGE privileges and an RSA key pair generated in or uploaded to Tealium.

    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 Snowflake

    Snowflake → Treasure AI

    AI Studio connection. Lets Treasure AI Studio agents query and visualize data in a Snowflake warehouse during a chat, through an OAuth security integration created in Snowflake.

    Snowflake → Treasure AI

    Bulk unloading import. Imports Snowflake tables or views into Treasure Data through a high-volume bulk unloading path that uses Snowflake stages, with incremental loading, in a connector labeled beta.

    Snowflake → Treasure AI

    Composable Audience Studio. Builds Treasure Data audience segments directly on Snowflake tables with Composable Audience Studio, which sends federated queries so data never leaves Snowflake, over key pair authentication.

    Snowflake → Treasure AI

    Import. Imports data from Snowflake tables or views into Treasure Data, with incremental loading by timestamp or numeric columns and options for handling invalid values.

    Snowflake → Treasure AI

    Live Connect zero-copy. Lets Treasure Data query Snowflake tables through a Live Connect zero-copy source defined by role, warehouse and database, in federated Trino queries, when enabled.

    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 Snowflake. 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 Snowflake 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, Snowflake or any platform listed.

Getting Klaviyo data into Snowflake?

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