Mailchimp to BigQuery

Each of these CDPs lists a connector that reads from Mailchimp 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.

• BLBlueConic

  Reads from Mailchimp

  BlueConic ⇄ Mailchimp

  Imports Mailchimp audience members and mail activity into BlueConic and exports segment profiles to selected Mailchimp audiences in scheduled or manual batch runs.

  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 ↗
• KLKlaviyo

  Reads from Mailchimp

  Mailchimp → Klaviyo

  Migrates Mailchimp contacts to Klaviyo in a one-time sync, along with when each contact received, opened and clicked emails, so campaign metrics carry over.

  Docs ↗

  Sends to BigQuery

  Klaviyo → BigQuery

  Sends Klaviyo profile data, event data or both into BigQuery, and can skip events coming from integrations that BigQuery already receives.

  Docs ↗
• LYLytics

  Reads from Mailchimp

  Lytics ⇄ Mailchimp

  Imports Mailchimp subscribers and campaign activity into Lytics every 12 hours and exports Lytics audiences to Mailchimp, with campaigns importable as Lytics Experiences.

  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 ↗
• MPmParticle

  Reads from Mailchimp

  Mailchimp → mParticle

  Feed. Brings Mailchimp email events into mParticle as a feed through a Mailchimp webhook.

  Docs ↗

  Sends to BigQuery

  mParticle → BigQuery

  Audiences. Writes mParticle audience membership to tables in a BigQuery dataset in your Google Cloud project.

  Docs ↗

  mParticle → BigQuery

  Warehouse. Loads incoming mParticle data into a BigQuery dataset so you can query it directly with SQL.

  Docs ↗
• SDSalesforce Data 360

  Reads from Mailchimp

  Mailchimp → Salesforce

  Brings Mailchimp campaigns, audiences, automations and e-commerce orders into Data 360 in batches or through Zero Copy query federation (beta).

  Docs ↗

  Sends to BigQuery

  Salesforce ⇄ BigQuery

  Google BigQuery. Connects Data 360 and Google BigQuery through Zero Copy, querying BigQuery tables in place and sharing Data 360 data back to BigQuery.

  Docs ↗
• SESegment

  Reads from Mailchimp

  Mailchimp → Segment

  Source. Pulls Mailchimp objects into Segment on a schedule for syncing to a warehouse.

  Docs ↗

  Sends to BigQuery

  Segment → BigQuery

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

  Docs ↗
• TETealium

  Reads from Mailchimp

  Mailchimp → Tealium

  Webhook data source. Sends Mailchimp list activity, including subscribes, unsubscribes, profile and email changes, cleaned addresses and campaign events, to Tealium AudienceStream through a list webhook.

  Docs ↗

  Sends to BigQuery

  Tealium → BigQuery

  Google BigQuery. Appends records (singly or batched), sends full event, visitor and log data and runs custom statements in Google BigQuery from AudienceStream or EventStream.

  Docs ↗
• TATreasure AI

  Reads from Mailchimp

  Mailchimp → Treasure AI

  Import. Imports Mailchimp lists with their members and member activity, plus campaigns, into Treasure Data with an API key or OAuth, using batch operations to ease rate limits.

  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 Mailchimp.

• ACActionIQ

  Reads from BigQuery

  BigQuery → ActionIQ

  BigQuery

  Sends to Mailchimp

  ActionIQ → Mailchimp

  Mailchimp
• AEAdobe Experience Platform

  Reads from BigQuery

  BigQuery → Adobe

  Brings Google BigQuery table data into Experience Platform for Real-Time CDP Ultimate customers.

  Docs ↗

  Sends to Mailchimp

  Adobe → Mailchimp

  Event forwarding. Sends events server-side to the Mailchimp Marketing API through event forwarding, where they can trigger emails from campaigns, customer journeys or transactional sends.

  Docs ↗

  Adobe → Mailchimp

  Interest Categories. Sends Real-Time CDP audiences to Mailchimp as interest categories named after each audience, adding or updating contacts and moving them in or out of groups.

  Docs ↗

  Adobe → Mailchimp

  Tags. Sends Real-Time CDP audiences to Mailchimp as tags named after each audience, adding new contacts or tagging existing ones within a chosen Mailchimp audience.

  Docs ↗
• 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 Mailchimp

  Amperity → Mailchimp

  Manages Mailchimp audiences from Amperity through the Mailchimp Marketing API, keyed by email address.

  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 Mailchimp

  BlueConic ⇄ Mailchimp

  Imports Mailchimp audience members and mail activity into BlueConic and exports segment profiles to selected Mailchimp audiences in scheduled or manual batch runs.

  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 Mailchimp

  DinMo → Mailchimp

  Creates Mailchimp segments inside a chosen contact list from DinMo segments and keeps them current by email for existing contacts, rebuilding a segment from scratch on historical refresh.

  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 Mailchimp

  Fivetran Activations → Mailchimp

  Adds and updates Mailchimp audience members by email from Fivetran Activations after you sign in to Mailchimp, with a required status such as subscribed or unsubscribed.

  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 Mailchimp

  Hightouch → Mailchimp

  Keeps Mailchimp audiences in sync with warehouse segments for personalized and automated 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 Mailchimp

  Lytics ⇄ Mailchimp

  Imports Mailchimp subscribers and campaign activity into Lytics every 12 hours and exports Lytics audiences to Mailchimp, with campaigns importable as Lytics Experiences.

  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 Mailchimp

  mParticle → Mailchimp

  Audiences. Keeps Mailchimp lists in step with mParticle audiences through Mailchimp's v3 API.

  Docs ↗

  mParticle → Mailchimp

  Events. Forwards mParticle events and user data to Mailchimp for email campaign targeting and tracking.

  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 Mailchimp

  RudderStack → Mailchimp

  Adds and updates Mailchimp audience members from RudderStack users and records their events.

  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 Mailchimp

  Segment → Mailchimp

  Destination. Sends identify calls from Segment to Mailchimp for email marketing in cloud mode.

  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 Mailchimp

  Tealium → Mailchimp

  Subscribes or unsubscribes Mailchimp list members and upserts e-commerce orders and abandoned carts 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 Mailchimp

  Treasure AI → Mailchimp

  Export. Adds Treasure Data segments to a Mailchimp list or updates existing members by email, filling merge fields and interest groups, signing in with an API key or OAuth.

  Docs ↗
• ZGZeta Global

  Reads from BigQuery

  BigQuery → Zeta Global

  Connects Google BigQuery to Zeta with a service account key so marketers can segment on tables in place with Zero Copy Database Explorer or ingest data through Data Flows.

  Docs ↗

  Sends to Mailchimp

  Zeta Global → Mailchimp

  Pushes Zeta customers to Mailchimp through a Channel Manager channel following the Mailchimp Lists API, authenticated as Mailchimp's developer docs describe, from Experiences.

  Docs ↗