> For the complete documentation index, see [llms.txt](https://docs.adpage.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adpage.io/data-and-insights/marketing-integrations/mailchimp.md).

# Mailchimp

Connect Mailchimp so your weekly newsletter volume and clicks feed the Marketing Mix Model.

Connect your Mailchimp account so AdPage knows how much email you sent each week, and how many subscribers clicked. The Marketing Mix Model uses that as part of your baseline. AdPage only reads: nothing is written back to Mailchimp, no audience is changed and no mailings are ever sent.

{% hint style="info" %}
**This is not the Mailchimp tag in your server container.** AdPage also offers a server-side GTM template that sends events *to* Mailchimp, for segmentation. That tag and this integration are independent: the integration reads your campaign reports *from* Mailchimp. You can use either, or both.
{% endhint %}

### Before you start

You need a **Mailchimp API key**. You create it yourself in Mailchimp:

1. Click your profile icon and choose **Profile**.
2. Open **Extras** and choose **API keys**.
3. Select **Create A Key**, give it a name you will recognise later (for example *AdPage*) and copy the key straight away. Mailchimp may only show the full key once.

A Mailchimp API key ends in a dash and the data centre of your account, such as `-us21`. Copy the whole key, including that ending: AdPage uses it to find your account.

{% hint style="warning" %}
Mailchimp has no read-only keys: an API key gives access to the whole account. AdPage only uses it to read your account name and campaign reports. Create a separate key for AdPage, so you can revoke it in Mailchimp at any time without affecting anything else.
{% endhint %}

You also need a container selected in AdPage, and an AdPage login with access to that container. The connection is stored per container, so a customer with several containers connects each one separately.

### Connect Mailchimp

{% stepper %}
{% step %}

#### Open the integrations page

Go to **Integrations** and select the container at the top of the page. Then open the **Mailchimp** tile in the email group. Searching for "newsletter" finds it too.
{% endstep %}

{% step %}

#### Paste the API key

Paste the key into the **API key** field. It is stored encrypted and never shown again: only its last four characters and the data centre stay visible, so you can recognise which key is stored.
{% endstep %}

{% step %}

#### Test and connect

Select **Test & connect**. Before anything is saved, AdPage reads your account and the campaign reports of the last 90 days, to prove the key works. A key that does not work is never stored, so the tile cannot say "connected" while nothing comes in.

Use **Test only** if you want to check the key without saving it yet.
{% endstep %}
{% endstepper %}

The test shows your account name, how many newsletters you sent in the last 90 days and the title of the most recent one. It also says how many RSS campaigns and automations it found, which are not counted (see below), and whether your reports contain e-commerce revenue.

### What you get

Your weekly email activity feeds the **Marketing Mix Model** as a baseline control: the number of delivered emails, and the number of subscribers who clicked. Email carries no media spend, so it is not a channel in the model. But how much email went out is a real driver of your baseline, and the model is better for knowing it: without it, a strong newsletter week can be credited to whichever ad channel happened to spend more that week.

The revenue Mailchimp attributes to a campaign is stored next to it, for comparison, but never used in the model: that revenue is already part of what the model explains.

AdPage loads the history once, when your model is prepared. After that, the last four weeks are refreshed every Monday, because opens and clicks keep coming in for days after a send.

{% hint style="info" %}
There are no Mailchimp widgets in Data Studio yet. For Spotler Mail+ and MailCampaigns there are; Mailchimp will follow.
{% endhint %}

### Reading the numbers

{% hint style="warning" %}
**Only newsletters are counted.** Regular, plain-text, A/B test and multivariate campaigns count. Automations (customer journeys) do not: an automation is triggered by something a customer did, and that visit often came from paid media, so as a control it would take credit away from the ads that caused it. RSS campaigns are left out as well, to rule out counting the same email twice.
{% endhint %}

**Delivered means sent minus bounces.** Delivered is emails sent minus hard bounces, soft bounces and addresses with a syntax error.

**Clicks count subscribers, not clicks.** A subscriber who clicks three links in one email counts once.

**Opens are not used.** Apple Mail Privacy Protection pre-loads images, which inflates opens unpredictably. AdPage stores them but does not give them to the model.

**Weeks follow the Dutch send date.** Mailchimp reports send times in UTC. A newsletter sent on Sunday at 23:30 Dutch time counts in that week, not in the next one.

**A week can be skipped.** If one campaign report in a week comes back without a send count, AdPage leaves that whole week out rather than storing it too low, and says so when the history is loaded.

**Revenue needs a connected store.** Mailchimp only knows campaign revenue when your webshop is connected to Mailchimp. Without it there is simply no revenue, and that does not affect the model.

### Troubleshooting

**"Dit is geen Mailchimp API key" (this is not a Mailchimp API key).** The key must end in a dash and the data centre, such as `-us21`. You probably copied only part of it: copy the whole key again.

**The key is rejected.** The message names what Mailchimp answered. Usually the key was revoked or mistyped. Create a new key in Mailchimp and paste it.

**The test finds no newsletters.** The count covers newsletters sent in the last 90 days. If it says zero while you do see recent campaigns in Mailchimp, the tile lists the fields Mailchimp returned. Send that line to support.

**The tile asks you to reconnect.** Mailchimp is refusing the stored key, usually because it was deleted in Mailchimp. Create a new key and paste it. To swap a working key for a new one, use **Replace key**: the new key is tested first, and if that fails the current key stays in place.

**Disconnecting.** Select **Disconnect** in the tile. That removes AdPage's copy of the key; the key itself stays valid in Mailchimp until you delete it there. The weeks already loaded stay in the model.

{% hint style="warning" %}
**Mailchimp is not covered by the daily connection check**, so a broken connection does not email you. If you replace or delete keys in Mailchimp, check the tile afterwards.
{% endhint %}

Still stuck? Contact <support@adpage.io> and include the container and what the tile showed.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.adpage.io/data-and-insights/marketing-integrations/mailchimp.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
