Mailchimp and Salesforce, including consent
Marketing sends from Mailchimp. The customer record lives in Salesforce. Salesforce Mailchimp integration keeps the audience current and, more importantly, keeps consent consistent in both directions.
Most pages on this subject treat it as a contact sync. The part that actually carries risk is the opt-out.
What syncs between Mailchimp and Salesforce
Audience data out, engagement data back.
- Contacts and leads flow from Salesforce into Mailchimp audiences, so segments reflect current CRM data.
- Field updates propagate, so a changed job title or region reaches the segmentation.
- Opens, clicks and bounces come back and land against the Salesforce record.
- New subscribers from Mailchimp forms can create Salesforce records.
- Unsubscribes sync both ways and update the Salesforce email opt-out field.
That last item is the one that matters most, and it is the one most implementations treat as an afterthought.
Which way the data flows between Mailchimp and Salesforce
Two-way, and the consent direction is not optional.
⇆ Two way→ Out of Salesforce← Into Salesforce
Consent has to be genuinely two-way and prompt. Where someone unsubscribes in Mailchimp and Salesforce does not know, the next campaign built from a Salesforce segment emails a person who has withdrawn consent. That is a UK GDPR exposure, not a tidiness problem.
What a Mailchimp integration gives you
Campaigns that reach the right people, and a defensible consent position.
- Audiences reflect reality. Segments built from live CRM data rather than an export from last quarter.
- Sales sees engagement. The rep knows what the contact has opened before picking up the phone.
- One consent position. Opt-out respected wherever it was given, promptly.
- No manual list building. The export, filter and upload cycle disappears, along with its errors.
- Attribution becomes possible. Campaign engagement sitting alongside pipeline means marketing can show contribution.
How we connect Mailchimp to Salesforce
The question to settle before you build the Mailchimp integration
Where is consent recorded, and how fast does it travel?
Consent can be given or withdrawn in either system. A form on the website writes to Salesforce; an unsubscribe link writes to Mailchimp. Both are legitimate. Each has to reach the other quickly.
The question is not whether to sync it but how fast, and what happens in the gap. A nightly sync means someone who unsubscribes on Monday morning can be emailed on Monday afternoon from a segment built in Salesforce.
We would rather design for near-real-time consent and batch everything else, than batch consent because it was simpler to build.
The unsubscribe that arrived too late
Someone clicks unsubscribe on Monday morning. Marketing builds a segment in Salesforce on Monday afternoon and sends. The opt-out had not propagated, so a person who withdrew consent receives another email.
That is a UK GDPR exposure rather than an untidy list, and it is entirely a design decision. Consent can be given or withdrawn in either system: a website form writes to Salesforce, an unsubscribe link writes to Mailchimp. Both are legitimate. Each has to reach the other quickly.
The question is not whether to sync consent but how fast, and what happens in the gap. A nightly batch leaves a window of up to twenty-four hours in which exactly the scenario above can occur. We would rather design consent to propagate as close to real time as the platforms allow and batch the less critical data instead.
The rest is more ordinary and still valuable. Contacts and leads flow to audiences so segments reflect live CRM data rather than an export somebody took, and opens, clicks and bounces come back so the rep knows what a contact has read before dialling.
If you take one thing from this page, make it the consent direction. Everything else here is convenience; that one is compliance.
Connect Mailchimp to Salesforce
Straightforward for the contact data, and worth doing carefully for the consent data.
Whatever you run alongside it, if it has an API it can be connected, so get in touch and we will tell you what is realistic.
Salesforce Mailchimp integration: frequently asked questions
Yes. Contacts and leads flow from Salesforce into Mailchimp audiences, and engagement data such as opens, clicks and bounces flows back to the Salesforce record. Unsubscribes sync in both directions and update the Salesforce email opt-out field.
Unsubscribe status must sync in both directions and promptly. If someone opts out in Mailchimp and Salesforce is unaware, a later campaign built from a Salesforce segment can email a person who has withdrawn consent. We design consent to propagate as close to real time as the platforms allow, and batch less critical data instead.
Yes. New subscribers acquired through Mailchimp forms can create corresponding leads or contacts in Salesforce, with matching rules applied so you do not create duplicates of people you already know.
Yes. Field updates and new records propagate, so audiences reflect current CRM data rather than an export somebody took. This removes the export, filter and upload cycle and the errors that come with it.
No. Some clients keep an internal owner and buy specialist depth around them, others hand the platform to us entirely. Both work.