MailChimp
📬 Mailchimp Destination Setup – Connecting Mailchimp to AudienceSync
🧠 Overview
Mailchimp is a powerful marketing automation platform. Integrating Mailchimp with AudienceSync enables you to sync subscriber data, personalize campaigns, segment contacts, and support regulatory compliance.
✅ Prerequisites
To integrate Mailchimp with AudienceSync, ensure you have:
- A Mailchimp account with admin access
- Access to:
- API Key
- Audience (List) ID
- Email Template ID
🔧 Step-by-Step Setup
1. Access AudienceSync
- Log in to your AudienceSync account.
- Navigate to the Destinations section.
2. Create a New Destination Connector
- Click Add Destination
- Select Mailchimp from the list of available destinations.
3. Configure Connection Settings
Provide the following Mailchimp details:
- API Key
→ Get it via Account → Extras → API Keys
- List ID (Audience ID)
→ Go to Audience → Manage Audience → Settings → Audience name and defaults
- Email Template ID
→ Retrieve it from the Templates section or via Mailchimp’s API
Fill out these fields and click Continue.
4. Test the Connection
- Use the Test Connection button to verify your setup.
- If successful: You’ll receive confirmation.
- If unsuccessful: Double-check API Key, List ID, and Template ID.
5. Finalize Setup
- Save the connector to complete the Mailchimp destination setup.
🧱 Setting Up a Model for Mailchimp
To send structured data to Mailchimp, create a model from your source data:
➤ Review Source Data
- Identify key fields:
email,first name,last name,tags, etc.
➤ Create the Model
- Select the necessary fields and map them to Mailchimp-compatible names, such as:
merge_fields.FNAMEmerge_fields.LNAMEtags.0
➤ Validate and Save
- Ensure your data is clean and formatted correctly.
- Save the model before proceeding.
➤ Sync to Mailchimp
- Map your model fields to Mailchimp parameters when creating the sync.
🔁 Mailchimp Field Mapping Guide
🧩 Core Parameters
Field | Description | Purpose |
email | Subscriber’s email address | Required for identification |
status | Subscription status | Supports compliance & segmentation |
Options: subscribed, unsubscribed, cleaned, pending |
🎯 Personalization Fields
Field | Description | Purpose |
first_name | Contact's first name | For personalization |
last_name | Contact's last name | Adds formality |
merge_fields.FNAME | Merge tag for first name | Used in email templates (e.g., “Hi, |FNAME|!”) |
merge_fields.LNAME | Merge tag for last name | Enables dynamic content personalization |
🧠 Segmentation Fields
Field | Description | Purpose |
tags.0 | Tag label | For grouping/segmenting contacts |
vip | true/false flag | Marks high-priority contacts |
language | Language preference (e.g., en, fr) | Supports localized messaging |
📋 Compliance & Tracking Fields
Field | Description | Purpose |
ip_opt | IP at opt-in | Tracks consent origin |
ip_signup | IP at signup | Used for analytics & location-based compliance |
timestamp_opt | Timestamp of opt-in (ISO 8601) | Regulatory audit trail |
timestamp_signup | Signup date/time (ISO 8601) | Enables lifecycle tracking |
Did this answer your question?
😞
😐
🤩
Last updated on August 6, 2021