Send your event data from RudderStack to Mailchimp.
5 minute read
Mailchimp is a popular email marketing automation platform used worldwide by thousands of businesses. Built specially for eCommerce and retail, Mailchimp allows you to build your audience and send them personalized campaign and marketing messages through web or mobile.
RudderStack supports Mailchimp as a destination to which you can seamlessly send your event data. Also, you can add people to your Mailchimp list via a simple identify call.
Find the open-source transformer code for this destination in our GitHub repository.
Once you have confirmed that the source platform supports sending events to Mailchimp, follow these steps:
From your RudderStack dashboard, add a source. Then, from the list of destinations, select Mailchimp.
Assign a name to the destination and click Continue.
Connection settings
To successfully configure Mailchimp as a destination, you will need to configure the following settings:
Mailchimp API Key: Enter your Mailchimp API Key.
It is recommended to create a new API key for the RudderStack destination. Mailchimp restricts each API key to a maximum of 10 concurrent requests. Hence, creating a dedicated key for RudderStack ensures maximum throughput for the outgoing calls. Refer to the Mailchimp documentation for more detaails.
Mailchimp Audience ID: Enter your Mailchimp Audience ID.
Mailchimp DataCenter ID: Enter your Mailchimp DataCenter ID.
Enable Merge fields: Enable this setting if you want to add merge fields while updating a subscriber.
Refer to the FAQ section for more information on how to get the above details.
Identify
The identify call captures the details about the visiting user along with the properties associated with that user.
Every time an identify call is made including an email address, RudderStack performs the following steps:
RudderStack first checks with Mailchimp whether that specific email address exists for the listId provided in the destination settings.
If the email address does not exist in the list, RudderStack subscribes the associated user to the list immediately. If the doubleOptIn setting is enabled, Mailchimp sends a confirmation email to that user, and that email is tagged with a pending subscriber status. The subscriber status automatically changes to subscribed once the user confirms the email.
If the user already has a subscriber status such as pending, subscribed, unsubscribed or cleaned, RudderStack will not resubscribe them, but only update their associated user traits.
email is a required field for the identify call. The rest of the fields must match the Merge Field tag in Mailchimp.
Capture custom user traits
You can capture the custom user traits in the Mailchimp list dashboard by creating a custom merge field in Mailchimp.
Mailchimp supports merge tags only up to 10 characters. Hence, every user trait sent inside the identify call is trimmed to the first 10 characters and converted to uppercase before being sent to Mailchimp. Also, the Merge Tags is created by taking the 10 characters (excluding whitespace/special characters) of its Field Label.
For example, if you set the Field Label as Upto 10-Char, the Merge Tag will be UPTO10CHAR. The user.trait inside your identify call, which is, Upto 10-Char, will be converted to UPTO10CHAR before being sent to Mailchimp.
Creating custom merge fields
Create custom merge fields only for the traits you want to see in your list view and not for all user.traits.
To create and send custom merge fields or user traits to Mailchimp, please follow these steps:
Create the merge field in Mailchimp for every trait you want sent to it.
When you make the identify call, the keys that match the traits above will automatically appear in your Mailchimp list.
The identify call will not change in this case.
Overriding listId
If you have multiple lists that your users can subscribe to, you can override the default listId as a parameter to Mailchimp.
The following sample snippet overrides the default listId with esf1rd234a as listId:
RudderStack provides you with the option to manually update the subscription status of a user by passing the subscriptionStatus parameter to Mailchimp.
This setting will NOT work for new users. For new users, the subscription status will always be set as pending or subscribed, depending on the set doubleOptIn setting.
email is a required field for making a track call successfully. You can pass it in either traits.email, ucontext.traits.email, or properties.email. RudderStack hashes the email field and replaces subscriber_hash in the Mailchimp Events API endpoint.
Supported mappings
The following table lists the mappings between the RudderStack and Mailchimp properties:
RudderStack property
Mailchimp property
Notes
event Required
name
Event name must contain 2-30 characters.
properties
properties
-
properties.isSyncing
is_syncing
RudderStack triggers the targeted automations by default. However, you can set isSyncing to true if you don’t want to trigger them.
originalTimestamp
occurred_at
-
RudderStack stringifies all values received in properties[key] as Mailchimp only accepts the string values in properties[key].
FAQ
Where do I get the Mailchimp API Key?
To get the Mailchimp API Key, log in to Mailchimp, and go to Account > Extras > API Keys.
Where do I get the Mailchimp Audience ID?
You can find the Mailchimp Audience ID by logging in to Mailchimp and navigating to Audience > Manage Audience > Settings > Audience name and defaults.
Where do I get the Mailchimp DataCenter ID?
To get the DataCenter ID, please refer to your Mailchimp URL in the browser. For example, if the URL is https://us20.admin.mailchimp.com/lists, the DataCenter ID is us20 in this case.
This site uses cookies to improve your experience while you navigate through the website. Out of
these
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
essential
for the working of basic functionalities of the website. We also use third-party cookies that
help
us
analyze and understand how you use this website. These cookies will be stored in your browser
only
with
your
consent. You also have the option to opt-out of these cookies. But opting out of some of these
cookies
may
have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. This
category only includes cookies that ensures basic functionalities and security
features of the website. These cookies do not store any personal information.
This site uses cookies to improve your experience. If you want to
learn more about cookies and why we use them, visit our cookie
policy. We'll assume you're ok with this, but you can opt-out if you wish Cookie Settings.