> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking Mailchimp as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/mailchimp

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://app.posthog.com` (app host for links).

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

The Mailchimp connector can link lists, campaigns, reports, and contacts to PostHog.

To link Mailchimp:

1.  Go to the [sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section in PostHog.

2.  Click **\+ New source** and then click **Link** next to Mailchimp.

3.  Next, you need an API key from Mailchimp. Go to your [API keys settings](https://us1.admin.mailchimp.com/account/api/) in Mailchimp. Click **Create A Key**, give it a name, and copy the value of the newly created key. The key should be in the format `key-dc` (e.g., `abc123def456-us6`), where the suffix after the last hyphen is your Mailchimp data center.

4.  Back in PostHog, paste the API key in the `API key` field and click **Next**.

5.  On the next page, set up the schemas you want to sync and modify the method and frequency as needed. Once done, click **Import**.

Once the syncs are complete, you can start using Mailchimp data in PostHog.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `API key` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `lists` | An audience (mailing list) in Mailchimp that contains contacts and their subscription status. | Full refresh | — | — |
| `campaigns` | An email campaign created in Mailchimp, including its settings, recipients, and content. | Full refresh | — | — |
| `reports` | A performance report for a sent campaign, summarizing opens, clicks, bounces, and engagement. | Full refresh | — | — |
| `contacts` | A member (contact) of a Mailchimp audience, including subscription status and engagement. | Incremental, Full refresh | last\_changed | — |
| `automations` | An automation (classic automated journey) in Mailchimp, including its trigger and send settings. | Incremental, Full refresh | create\_time, start\_time | — |
| `templates` | An email template available to the account, either built by the user or provided by Mailchimp. | Incremental, Full refresh | date\_created | — |
| `sms_campaigns` | An SMS or WhatsApp campaign, including its schedule, channel, and recipient count. | Full refresh | — | — |
| `conversations` | A conversation thread between the account and a contact, started from a campaign reply. | Full refresh | — | — |
| `campaign_folders` | A folder used to organize campaigns in the Mailchimp account. | Full refresh | — | — |
| `ecommerce_stores` | An ecommerce store connected to the Mailchimp account. | Full refresh | — | — |
| `ecommerce_orders` | An ecommerce order synced from a connected store, including totals and campaign attribution. | Full refresh | — | — |
| `landing_pages` | A landing page built in Mailchimp, including its publish state and connected audience. | Full refresh | — | — |
| `verified_domains` | A sending domain registered on the account, with its verification and authentication state. | Full refresh | — | — |
| `list_segments` | A segment or tag defined on an audience, including its conditions and current member count. | Incremental, Full refresh | created\_at, updated\_at | — |
| `list_segment_members` | A contact's membership of an audience segment, with the contact's status and engagement. | Full refresh | — | — |
| `list_merge_fields` | A merge field (audience field) defined on an audience, describing how contact data is stored. | Full refresh | — | — |
| `list_interest_categories` | An interest category (group title) on an audience, used to group signup form preferences. | Full refresh | — | — |
| `list_growth_history` | A monthly summary of how an audience grew, one row per audience per month. | Full refresh | — | — |
| `list_activity` | A daily summary of sends, opens, clicks, and subscription changes for an audience. | Full refresh | — | — |
| `campaign_content` | The rendered HTML and plain-text content of a campaign, one row per campaign. | Full refresh | — | — |
| `campaign_feedback` | A team feedback comment left on a campaign while it was being drafted. | Full refresh | — | — |
| `report_email_activity` | Per-recipient open and click activity for a sent campaign, one row per campaign recipient. | Full refresh | — | — |
| `report_open_details` | Members who opened a sent campaign, with open counts and open timestamps. | Full refresh | — | — |
| `report_click_details` | Per-link click performance for a sent campaign, one row per tracked URL. | Full refresh | — | — |
| `report_sent_to` | Every recipient a campaign was sent to, with delivery status and open counts. | Full refresh | — | — |
| `report_unsubscribed` | Members who unsubscribed after receiving a campaign, with the time and stated reason. | Full refresh | — | — |
| `report_abuse_reports` | Abuse (spam) complaints filed against a sent campaign, one row per complaint. | Full refresh | — | — |
| `report_domain_performance` | Campaign performance broken down by recipient email domain, such as gmail.com. | Full refresh | — | — |
| `report_locations` | Campaign opens broken down by the geographic location of the recipient. | Full refresh | — | — |
| `report_ecommerce_product_activity` | Revenue and purchase activity attributed to a campaign, broken down by product. | Full refresh | — | — |
| `automation_emails` | An individual email within an automation workflow, including its delay, content, and performance summary. | Full refresh | — | — |
| `ecommerce_products` | A product in a connected ecommerce store, including its variants and images. | Full refresh | — | — |