ZapBounce and Mailchimp
Mailchimp enforces list quality at the account level. That single fact changes how you should sequence a verification job, because the consequence of getting it wrong is not a paused campaign.
An audience assembled over several years, imported from a previous platform, is the classic case. It looks fine in the dashboard until the first send reports the bounce rate.
The suspension applies to the account, not the campaign
Mailchimp's terms give them the right to suspend or terminate an account for sending practices that generate high bounce and complaint rates. A campaign that trips it does not simply stop; the account stops, and every other audience with it.
Their compliance review is not instant either. Getting a suspended account reinstated takes a support conversation, and if the suspension lands during a product launch week the schedule does not survive it.
Mailchimp also cleans addresses automatically after a hard bounce, marking them as cleaned and removing them from future sends. That protects them, and it happens after the bounce has already been recorded against you.
How the data moves
Export the audience as CSV
Audience, then the export option. You get every merge field alongside the address, and those columns come back untouched in the verified file, so the verdict lands next to the contact rather than in a file you then have to join.
Verify the file, not the API
Mailchimp's API is rate-limited per account and pulling an entire audience through it is slow. Exporting and uploading a CSV is faster and does not consume the API budget your other automations need.
Re-import with the verdict as a merge field
Add a VERDICT merge field before importing. Mailchimp matches on email address, so an import updates existing contacts rather than duplicating them.
Archive rather than delete
Archived contacts stop counting toward your billable audience size and keep their history. Deleting loses the record of what happened, which you want if a suspension conversation ever starts.
Setting it up
- Export the audience from Mailchimp as a CSV, keeping every merge field column.
- Upload it to the file endpoint, naming the email column if the export has more than one address field.
- Wait for the completion webhook, then download the results file with your original columns plus the verdict.
- Create a VERDICT merge field in the audience, then import the results back so it matches on the address.
- Build a segment where VERDICT is valid, and archive the contacts marked invalid.
- Keep catch-all and unknown contacts in a separate segment and send to them on their own schedule.
Mailchimp: common questions
Does Mailchimp verify addresses itself?
It removes an address after it hard bounces, which is after the damage is recorded. There is no pre-send verification on import.
Will verifying reduce my Mailchimp bill?
Only if you archive what you remove. Archived contacts stop counting toward the billable audience size; unsubscribed and cleaned ones do too, but a contact sitting in a segment still counts.
What about an audience with several years of history?
That is the highest-risk import there is. Verify before the first send, and expect the oldest cohort to carry most of the invalid addresses.
Check a Mailchimp export today
100 free checks a month, no card. Unknown results and duplicates are never billed.