> For the complete documentation index, see [llms.txt](https://docs.zellify.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zellify.app/platform-introduction/integrations/mailchimp.md).
# Mailchimp
Capture email leads from your funnels and sync them directly to a Mailchimp audience.
The Mailchimp integration automatically adds users to your Mailchimp audience when they submit their email in a funnel.
Once enabled, you can:
* Capture leads and add them to a Mailchimp audience
* Retarget users who drop off at the paywall
* Send personalized offers to non-purchasers
* Sync funnel answers as merge fields
* Track conversion status to segment purchasers from non-purchasers
If you use Mailchimp for email marketing, this integration ensures every lead captured in your funnels is automatically available for campaigns and automations.
***
### Enabling the Integration
To enable Mailchimp:
Dashboard → Settings → Integrations\
1. Locate **Mailchimp**
2. Toggle the integration on
3. Enter your **Mailchimp API Key**
4. Enter your **Server Prefix**
***
### Finding Your Mailchimp API Key
To find your API key in Mailchimp:
1. Go to your **Mailchimp Dashboard**
2. Navigate to **Account & Billing → Extras → API Keys**
3. Click **Create A Key**
4. Copy the generated API key
5. Paste the key into Zellify
#### Server Prefix
Your server prefix is the part after the dash in your API key.
For example:\
If your API key ends with `-us16`, your server prefix is `us16`.
***
## Syncing Leads to a Mailchimp Audience
The primary use case for this integration is syncing email leads from your funnels directly into a Mailchimp audience.
To enable audience syncing:
1. Open a **Campaign** in the Zellify dashboard
2. Go to **Campaign Settings**
3. Toggle on **Sync email leads to Mailchimp**
4. Enter your **Mailchimp Audience ID**
When a user submits their email in that campaign’s funnel, they are automatically added to the specified Mailchimp audience.
This is configured per campaign, allowing you to route leads from different funnels into different audiences.
***
## What Happens When an Email Is Captured
When a user provides their email in a funnel, Zellify:
* Adds the user to your Mailchimp audience as a subscribed contact
* Tags the user with `conversion_status: unconverted`
* Syncs funnel answers as merge fields on the contact profile
From there, you can:
* Build automations targeting unconverted leads
* Segment contacts based on funnel answers
* Personalize emails using merge field data
***
## Conversion Tracking
When a payment is completed in your funnel, Zellify updates the contact in Mailchimp.
* The `conversion_status` tag is updated to reflect that the user converted
This allows you to:
* Build segments of contacts tagged `conversion_status: unconverted`
* Create automations that send follow-up emails
* Automatically stop campaigns when a user converts
This makes it easy to recover users who dropped off at the paywall without manual work.
***
## Funnel Answers as Merge Fields
All quiz and form responses collected in the funnel are synced to Mailchimp as merge fields on the subscriber profile.
This allows you to:
* Segment users based on quiz responses
* Personalize email content dynamically
* Build targeted campaigns based on specific answers
***
## How Mailchimp Differs From Klaviyo
Both integrations capture email leads for marketing, but they work differently.
**Klaviyo** runs client-side:
* The Klaviyo SDK is loaded on funnel pages
* Events are tracked in the browser in real time
* The user is identified and subscribed from the frontend
**Mailchimp** runs server-side:
* Contacts are synced to Mailchimp when specific events occur (email capture, payment events)
* The Mailchimp API is used with your private API key
* No browser-level tracking is performed
Mailchimp focuses on contact syncing and conversion tracking rather than behavioral event tracking.
{% embed url="" %}
---
# 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.zellify.app/platform-introduction/integrations/mailchimp.md?ask=&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.
