The Email List Hygiene Playbook

Most list hygiene advice reads like a warning label: "keep your list clean or bad things will happen." That's true, but it's not a plan. What follows is a concrete playbook — three moments where verification earns its keep, and how to wire each one into a marketing stack you already run.

1. At signup: validate before it enters your CRM

The cheapest email address to remove is the one you never store. Every modern verification service exposes a real-time API — the client submits the form, your backend hits the API with the email, and you reject typos ("gnail.com"), disposable inboxes, role addresses (info@, support@) and outright invalid syntax before creating the record.

This one step often eliminates 5–8% of what would otherwise become bounces later. It's also invisible to legitimate users — a sub-second API call in the submit handler. Bouncer's real-time endpoint is a drop-in for this and returns a clear verdict (deliverable, risky, undeliverable) plus a suggested correction when the domain looks like a typo.

Fixing bad data at the source is always cheaper than cleaning it up downstream. This is doubly true for email.

2. On a schedule: re-verify the existing list

Even a perfectly clean list decays. People change jobs, close accounts, forward personal email to new addresses, and let old inboxes fill up until the provider deactivates them. B2B lists decay fastest — 20–30% a year is normal for a mid-market audience.

A sensible cadence:

• Monthly if you send more than three campaigns a week.
• Quarterly for weekly senders.
• Before any big send (announcement, product launch, re-engagement) if it's been more than 30 days.

Upload the CSV, run the batch, and split the output into three segments: keep, sunset, remove. Automate the sunset flow so it's a default, not a heroic quarterly project.

3. Pre-send: one last pass on dormant segments

The riskiest campaigns are the ones sent to lists you haven't emailed recently. Cold outbound. Re-engagement flows. That trade-show list someone dropped into HubSpot four months ago. Pre-send verification is insurance: cheap, one-off, and disproportionately effective at preventing exactly the campaigns most likely to blow up your bounce rate.

The workflow is straightforward: export the segment, verify it, re-import with the verification status as a custom property, and exclude anything marked as undeliverable or risky from the send.

What to do with the results

Verification returns categories, not just yes/no. A reasonable policy:

• Deliverable: keep and mail normally.
• Risky / catch-all: keep but limit to your most trusted campaigns; watch bounce and complaint rates.
• Undeliverable / invalid: remove immediately. Don't "test" them.
• Disposable / role: remove or route into a separate low-priority segment.

The lightest possible stack

You don't need a fifteen-tool deliverability stack to do this well. The minimum viable version:

1. A verification API called from your signup form.
2. A monthly or quarterly cron that re-verifies your active list.
3. A sunset flow that removes anyone who hasn't opened in 180 days.
4. A pre-send verification step for any list dormant more than 30 days.

Bouncer covers all four surfaces with a single account — bulk uploads, real-time API, and native integrations for the ESPs and CRMs most teams already use. That matters less than picking any professional service and actually wiring it in. The worst verification workflow is the one you keep meaning to set up.