Klaviyo to BigQuery

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

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

• AMAmperity

  Reads from Klaviyo

  Klaviyo → Amperity

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

  Docs ↗

  Sends to BigQuery

  Amperity → BigQuery

  Google BigQuery (destination). Gets Amperity data into Google BigQuery by sending Parquet or CSV files to cloud storage first, then loading them for analysis.

  Docs ↗

  Amperity ⇄ BigQuery

  Google BigQuery (Amperity Bridge). Shares data both ways between Amperity and Google BigQuery through Amperity Bridge, using BigQuery sharing exchanges rather than file exports.

  Docs ↗
• BLBloomreach

  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.

  Docs ↗

  Sends to BigQuery

  Bloomreach → BigQuery

  Loomi BigQuery. Exports Bloomreach events every 6 hours and customer properties daily into a read-only Google BigQuery dataset through Loomi BigQuery, for custom SQL analysis and BI tools.

  Docs ↗
• BLBlueConic

  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.

  Docs ↗

  Sends to BigQuery

  BlueConic ⇄ BigQuery

  Imports BigQuery tables into BlueConic profiles and timeline events and exports profile and timeline data to BigQuery tables, replacing or partitioning a table on each batch run.

  Docs ↗
• CHChord

  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.

  Docs ↗

  Sends to BigQuery

  Chord → BigQuery

  Writes data from Chord's CDP to a BigQuery dataset in a Google Cloud project, authenticated with a service account key given as JSON, a JSON string or a file path.

  Docs ↗
• IOInsider One

  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.

  Docs ↗

  Sends to BigQuery

  Insider One → BigQuery

  Export. Gets Insider One events, their parameters and chosen user attributes into BigQuery by exporting CSV files to your Google Cloud Storage bucket for your own pipeline to load.

  Docs ↗
• LYLytics

  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.

  Docs ↗

  Sends to BigQuery

  Lytics ⇄ BigQuery

  Imports BigQuery tables into Lytics and exports user profiles, events, audience changes and definitions, metrics and system events from Lytics to BigQuery tables.

  Docs ↗
• SESegment

  Reads from Klaviyo

  Klaviyo → Segment

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

  Docs ↗

  Sends to BigQuery

  Segment → BigQuery

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

  Docs ↗
• TATreasure AI

  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.

  Docs ↗

  Sends to BigQuery

  Treasure AI → BigQuery

  Export v1. Writes Treasure Data job results into a BigQuery table that matches a predefined schema, in append, replace, replace backup or delete mode, with server-to-server API authentication.

  Docs ↗

  Treasure AI → BigQuery

  Export v2. Uploads large Treasure Data result sets to BigQuery as Parquet files through BigQuery load jobs, with append, replace, replace backup or truncate modes and JSON key or WIF sign-in.

  Docs ↗

  Treasure AI → BigQuery

  Open Catalog Access. Exposes Treasure Data's Iceberg tables to BigQuery as a federated dataset through BigQuery Omni, an experimental Open Catalog Access option that is not enabled by default.

  Docs ↗

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

• ACActionIQ

  Reads from BigQuery

  BigQuery → ActionIQ

  BigQuery

  Sends to Klaviyo

  ActionIQ → Klaviyo

  Klaviyo
• AMAmperity

  Reads from BigQuery

  Amperity ⇄ BigQuery

  Google BigQuery (Amperity Bridge). Shares data both ways between Amperity and Google BigQuery through Amperity Bridge, using BigQuery sharing exchanges rather than file exports.

  Docs ↗

  Sends to Klaviyo

  Amperity → Klaviyo

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

  Docs ↗
• BLBloomreach

  Reads from BigQuery

  BigQuery → Bloomreach

  Import. Imports customers, events, catalogs and vouchers from Google BigQuery tables or SQL queries into Bloomreach with service-account credentials, and runs SQL Reports on BigQuery data in place.

  Docs ↗

  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.

  Docs ↗
• BLBlueConic

  Reads from BigQuery

  BlueConic ⇄ BigQuery

  Imports BigQuery tables into BlueConic profiles and timeline events and exports profile and timeline data to BigQuery tables, replacing or partitioning a table on each batch run.

  Docs ↗

  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.

  Docs ↗
• DIDinMo

  Reads from BigQuery

  BigQuery → DinMo

  Connects a BigQuery project to DinMo through a Google Cloud service account, with DinMo datasets for segments, statistics and predictions and optional daily alerts on unusual billed usage.

  Docs ↗

  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.

  Docs ↗

  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.

  Docs ↗

  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.

  Docs ↗

  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.

  Docs ↗
• FAFivetran Activations

  Reads from BigQuery

  BigQuery → Fivetran Activations

  Source. Reads BigQuery tables and views for Fivetran Activations syncs through IAM roles for viewing data and running unload jobs, with an optional read-only mode.

  Docs ↗

  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.

  Docs ↗
• HIHightouch

  Reads from BigQuery

  BigQuery → Hightouch

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

  Docs ↗

  BigQuery → Hightouch

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

  Docs ↗

  Sends to Klaviyo

  Hightouch → Klaviyo

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

  Docs ↗
• LYLytics

  Reads from BigQuery

  Lytics ⇄ BigQuery

  Imports BigQuery tables into Lytics and exports user profiles, events, audience changes and definitions, metrics and system events from Lytics to BigQuery tables.

  Docs ↗

  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.

  Docs ↗
• MPmParticle

  Reads from BigQuery

  BigQuery → mParticle

  Warehouse Sync. Imports user and event data from a BigQuery dataset into mParticle through a Google Cloud service account with read access, as one-time or scheduled syncs.

  Docs ↗

  Sends to Klaviyo

  mParticle → Klaviyo

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

  Docs ↗

  mParticle → Klaviyo

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

  Docs ↗
• RURudderStack

  Reads from BigQuery

  BigQuery → RudderStack

  Source. Syncs BigQuery tables or SQL models to downstream tools with RudderStack Reverse ETL, on a schedule or on demand.

  Docs ↗

  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.

  Docs ↗

  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.

  Docs ↗
• SESegment

  Reads from BigQuery

  BigQuery → Segment

  Data Graph. Gives Segment's Data Graph a BigQuery service account that reads entity tables for Linked Audiences and Linked Events and keeps checkpoints in its own dataset (in active development).

  Docs ↗

  BigQuery → Segment

  Reverse ETL source. Reads BigQuery tables through a service account so Segment Reverse ETL can sync query results onward, granted either broad predefined roles or a narrower custom role.

  Docs ↗

  Sends to Klaviyo

  Segment → Klaviyo

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

  Docs ↗

  Segment → Klaviyo

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

  Docs ↗
• SDSimon Data

  Reads from BigQuery

  BigQuery → Simon Data

  Extracts data from Google BigQuery into Simon Data using a project name and service account JSON credentials that hold the Data Viewer, User and Job User roles.

  Docs ↗

  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.

  Docs ↗
• TETealium

  Reads from BigQuery

  BigQuery → Tealium

  Google BigQuery (cloud data source). Imports a Google BigQuery table or view into Tealium attributes through a service account holding the Data Viewer and Job User roles, with STRUCT columns flattened through a view.

  Docs ↗

  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.

  Docs ↗
• TATreasure AI

  Reads from BigQuery

  BigQuery → Treasure AI

  Composable Audience Studio. Sets up Composable Audience Studio on BigQuery with a GCP service account key and a zero-copy catalog, so Treasure Data segments are built on BigQuery data without copying it.

  Docs ↗

  BigQuery → Treasure AI

  Import v1. Imports BigQuery tables or query results into Treasure Data with the original BigQuery connector, whose connections can also serve exports unless they use OAuth.

  Docs ↗

  BigQuery → Treasure AI

  Import v2. Imports BigQuery tables or query results into Treasure Data with version 2 of the connector, which signs in with a service account JSON key or Workload Identity Federation, not OAuth.

  Docs ↗

  BigQuery → Treasure AI

  Live Connect zero-copy. Queries BigQuery tables in place from Treasure Data's Trino engine as Live Connect zero-copy federated queries, with no ETL, after the feature is enabled for the account.

  Docs ↗

  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.

  Docs ↗