Clean a Mailchimp Audience: Remove Bounces Before They Cost You

To clean a Mailchimp audience before the next campaign, connect your Mailchimp API key on SimpleVerifier's Integrations page (/connect), pick an audience or segment and press Verify leads. Each subscribed contact is checked and tagged with an sv_status merge field (tag SVSTATUS): valid, risky or invalid. To keep invalid addresses out of the send, tick Archive invalid contacts before you start. Nothing is unsubscribed or archived unless you tick it.

Why clean before the send, not after

Mailchimp cleans an address after it hard bounces, which means the bounce has already happened on your account. Mailchimp does not publish a bounce-rate threshold, so there is no number to stay under: the safe aim is to send only to addresses that should not bounce. Checking before the campaign moves the bounce from your sending record to a verification run.

Step 1: copy the whole API key

In Mailchimp, open your profile, then Extras > API keys, click Create A Key and copy it. Paste the whole key, including the part after the dash (like us21). That suffix is your datacenter, and the integration needs it to reach your account. Mailchimp's Marketing API docs describe the endpoints; the Mailchimp integration page lists the ones we call.

Step 2: pick an audience or segment

Connect the key on Integrations and pick an audience, or a segment inside one. Only subscribed contacts are pulled. Unsubscribed and cleaned contacts are skipped, since your campaign will not reach them anyway. The confirm screen shows the checks the run uses before it starts: one per distinct address.

Step 3: choose the write-back

Option	Default	What happens in Mailchimp
Set the sv_status merge field	On	Writes valid, risky or invalid to SVSTATUS. If the audience does not have it, it can be created as a hidden text field.
Unsubscribe invalid contacts	Off	Marks them unsubscribed in this audience. Mailchimp does not let an API resubscribe them later without consent.
Archive invalid contacts	Off	Archives them in this audience. They stop counting toward your contact limit, keep their history and can be added back.

For most audiences, tag plus archive is the right choice. Archiving is reversible and can lower the contact count you pay for. Unsubscribing is permanent through the API, so use it only when you are sure.

Write-back goes through Mailchimp's batch endpoint, 500 changes per batch, which Mailchimp processes in the background. Counts in Mailchimp can lag a few minutes behind the run.

Step 4: segment on SVSTATUS

With the merge field in place:

• Risky contacts (catch-all domains, role addresses, servers that would not confirm a mailbox) can go in their own segment. Send to them separately, or leave them out of a campaign where bounces matter most.
• Valid contacts go to the main send.
• Invalid contacts are the ones to archive if you did not tick it in the run.

Risky never becomes valid on our side. For the reasons, see email verification statuses explained and should you email catch-all addresses.

Run 100 free checks on a small segment to see SVSTATUS in your audience before you clean the whole list.

Related

For the manual export route, read how to clean your Mailchimp list before your next campaign. On paid plans, Auto-verify new leads daily checks new subscribers it has not seen in that audience once a day; see pricing.