Unsubscribe people who ask to stop hearing from you
An opt-out request reaches Mailchimp on its own, so the member stops receiving the mail they asked to leave behind.
New submission on an opt-out or email preferences form
Unsubscribe Email or update the subscriber's groups in the chosen Mailchimp audience
One-directional. A submission triggers the action — nothing is written back into your form.
An opt-out that sits in an inbox until somebody gets to it is the request most likely to turn into a complaint. Wiring the form straight to Mailchimp closes the gap: the status or the interest group changes as soon as the request is made, and the reason is kept on the record.
Membership bodies and associations use it most, where leaving one programme rarely means leaving the organisation, and the difference between the two has to be visible in the audience.
Setting it up
- 1
Publish the cancellation request form in formformform and link it from the footer of your member emails, not only from the account page.
- 2
Decide first what leaving means here: a full unsubscribe from the audience, or removal from one interest group while the member still gets general announcements.
- 3
Set the Zap's trigger to New Submission on this form, then map Email Address as the value every Mailchimp step keys on.
- 4
For a full stop, add Mailchimp's Unsubscribe Email action and select the audience the member receives campaigns from.
- 5
For a partial stop, use Add/Update Subscriber instead and clear only the interest groups tied to the programme they are leaving, so the rest of their preferences survive.
- 6
Add an Add Note to Subscriber step carrying Primary Reason for Cancellation and Additional Feedback (optional), so the reason is still readable after the contact goes quiet.
- 7
If Requested Cancellation Date matters, put a Zapier delay in front of the Mailchimp step and tell the member on the confirmation screen when it takes effect.
- 8
Test with your own address, confirm the status or groups changed in the audience, then publish the link everywhere a request might be made.
What maps where
Using the Membership Cancellation Request as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Mailchimp |
|---|---|
| Email Address | The address Mailchimp unsubscribes, or looks up to change interest groups |
| Primary Reason for Cancellation | First line of a note on the subscriber, so the reason outlives the unsubscribe |
| Additional Feedback (optional) | The rest of that note |
| Member ID | A merge field, for reconciling against your membership system later |
| Requested Cancellation Date | A merge field, or the input to a Zapier delay before the unsubscribe runs |
Variations worth knowing
Most people asking to stop hearing about a single mailing still want the annual notice. Clear that programme's interest group with Add/Update Subscriber and leave the subscriber active, rather than unsubscribing them from everything.
The Mailchimp step only handles email. Add a second action in the same Zap — a row in your membership sheet, a task for the administrator — so the membership itself is dealt with. Marketing status and membership status are different things.
If something isn't arriving
Compare the send time with the submission time first, because a campaign already in the queue still goes out. Then check the address on the form matches the one on the audience; people often type a personal address when the mail goes to a work one.
The action errors when there is nothing to unsubscribe, which is common if the person sits on a different audience or was never subscribed. Add a filter, or accept the error: the request is recorded, and that address is not being emailed anyway.
Frequently asked questions
Can one form unsubscribe someone from several audiences?
Only by adding a Mailchimp step per audience in the same Zap. Each Unsubscribe Email action targets one audience, so an organisation running three of them needs three steps, all mapped from the same Email Address value.
Is an automated unsubscribe enough for GDPR?
It handles the mechanics, in that the request is acted on and the timing is recorded. Consent, retention and how you answer a deletion request remain yours to manage. EU hosting and GDPR compliance cover the form side of it.
Should I still show Mailchimp's own unsubscribe link?
Yes. The footer link is required in campaigns and takes effect instantly. This form covers people who ask another way — a reply to support, a member who wants to explain why they are going. The two do not conflict.
Related automations
- Add newsletter signups to your Mailchimp audience
A signup on your site becomes a subscribed Mailchimp contact straight away, topics and all, with no list maintenance between campaigns.
- Attach survey scores to the subscriber as a note
The score and the comment land on the contact record in Mailchimp, where whoever writes the next campaign will actually see them.
- Build a launch list from pre-orders with merge fields filled in
Pre-order signups arrive in Mailchimp with merge fields populated, ready for a launch email that names the product they asked for.
- Start a Mailchimp journey when someone registers for a webinar
A registration applies a dated tag, and that tag is what starts the Mailchimp journey sending the confirmation and the reminders.
- Tag new leads with the offer they came from
Each lead joins the audience carrying a tag for the offer they filled in the form for, so segments stay honest without manual clean-up.
- Add buyers to a customers list after each order
Each order form submission adds the buyer to a Customers list in Constant Contact for updates and repeat-purchase emails.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free