Source connector

Mailchimp connector

Mailchimp integration for databases, warehouses and BI tools

Email marketing platform with audiences and campaign analytics. Datrise captures Mailchimp entities such as audiences, campaigns, automations, subscribers, and engagement metrics, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Mailchimp Marketing API v3 authenticates with OAuth 2.0, API key, incremental runs key on since_last_changed, and Mailchimp caps calls at 10 simultaneous open connections per account (returns 429 past that); no published requests-per-second ceiling.

Of the 5 objects, 4 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `mailchimp_audiences`) with a schema derived from the Mailchimp API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Mailchimp pipeline page, and join the waitlist to get the Mailchimp connector (Marketing) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Mailchimp data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
audiences	mailchimp_audiences	Upsert by primary key, incremental on updated-at
campaigns	mailchimp_campaigns	Upsert by primary key, incremental on updated-at
automations	mailchimp_automations	Upsert by primary key, incremental on updated-at
subscribers	mailchimp_subscribers	Upsert by primary key, incremental on updated-at
engagement metrics	mailchimp_engagement_metrics	Append-only, incremental by timestamp

Mailchimp API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Mailchimp Marketing API v3
Authentication	OAuth 2.0, API key — An account API key (used as either an HTTP Basic password or a bearer token) suits single-account integrations, while OAuth 2 is required to access another user's Mailchimp account on their behalf.
Pagination	offset — List endpoints (e.g. list members) take `offset`/`count` query parameters; `count` defaults to 10 and maxes out at 1,000 per page.
Rate limit	10 simultaneous open connections per account (returns 429 past that); no published requests-per-second ceiling
Incremental cursor	since_last_changed — `GET /lists/{list_id}/members` accepts `since_last_changed` (and the narrower `since_timestamp_opt`) to filter to records updated after a given timestamp.
Webhooks	Yes — List Webhooks
Bulk export	Yes — Batch Operations
Deletes detectable	Yes — Member `status` moves to `unsubscribed`/`cleaned`/`archived` and stays queryable, but a GDPR "permanently delete" erases the contact outright, so only the `unsubscribe`/`cleaned` webhook events (or a status diff) catch it, and a hard delete is invisible after the fact.

Official API reference

What bites when replicating Mailchimp

The account-wide cap is 10 simultaneous connections shared by every integration and the Mailchimp UI itself, not a per-app quota, so a connector's own concurrency setting can still trip a 429 from unrelated activity on the account.
`since_last_changed` filters `GET /lists/{list_id}/members`, but a member who is fully GDPR-deleted (as opposed to unsubscribed or archived) disappears from every future page with no timestamp trail to catch it.
List page size (`count`) defaults to only 10 and tops out at 1,000, so an unpaginated first call against a large audience silently returns a small slice rather than the whole list.
Webhook deliveries retry on increasing intervals for up to 75 minutes and then stop, and the signing secret shown at webhook creation cannot be retrieved again, so a lost secret means deleting and recreating the webhook and re-verifying signatures.

Compare this against every other documented API

Popular destinations for Mailchimp

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Mailchimp connector FAQ

What Mailchimp data does the connector extract?: 5 objects: audiences, campaigns, automations, subscribers and engagement metrics. Each lands in its own table with types preserved; history-style objects (1: engagement metrics) load as append-only streams.
Is the Mailchimp integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Mailchimp data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Mailchimp → destination pair has its own page with the object-to-table mapping.

Related Marketing sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Mailchimp pipeline with guided onboarding

Join the waitlist to get priority access for Mailchimp integrations with guided setup, schema-aware mapping, and production-grade incremental sync.