Deliverability Case Study: "List Hygiene"
Track 08 of Click Through is the companion to Track 07. Segmentation identified who belongs on Marcus's active list. List hygiene removes everyone who does not. The track covers three distinct hygiene operations in sequence: hard bounce removal, soft bounce thresholding, and sunset policy. Together they reduce a list from fifty thousand to something Marcus can look at without flinching.
The central insight is in the bridge: "a thousand clean beats fifty thousand more." This is not a consoling metaphor — it is a deliverability fact. Smaller, cleaner lists produce higher engagement rates, lower complaint rates, and better sender reputation than large, passive ones.
Verse 1: Bounce Handling
"Hard bounce logged — that address is done / Soft bounce hits three times in a row / At five consecutive — I let it go"
Bounce handling is the most operationally basic form of list hygiene. It is also the most neglected in practice.
Hard bounces are permanent delivery failures: the address does not exist, the domain does not exist, or the receiving server has permanently rejected the address. A hard bounce code (typically 5xx) means the address is and will remain undeliverable. It must be removed from the active send list immediately — on the same day, ideally within hours of the bounce report arriving. Hard bounces that sit on a list accumulate, and as domains are abandoned they are repurposed as recycled spam traps by ISPs and
blocklist operators.
Soft bounces are temporary delivery failures: the mailbox is full, the receiving server is temporarily unavailable, or the message was temporarily deferred. Most ESPs handle soft bounces automatically, retrying delivery over 24–72 hours. The question for the sender is when to treat a persistent soft bounce as permanent:
- Three consecutive soft bounces across separate campaigns is a reasonable first threshold for flagging the address as problematic.
- Five consecutive soft bounces with no successful delivery in between is the standard threshold for suppression. An address that has soft-bounced five times in a row is functionally undeliverable for most practical purposes.
The specific numbers in the lyric (three flags, five removes) are not universal constants — different ESP platforms apply different defaults — but the principle is correct: apply a threshold, enforce it consistently.
Verse 2: The Sunset Policy
"Ninety days no click — I run the query / Sunset window closing — no more mercy"
A sunset policy is an automated process for suppressing subscribers who have stopped engaging. It is the most important long-term list hygiene practice a sender can implement, and it is the one most frequently skipped because it requires deliberately shrinking a metric (list size) that is often used as a proxy for program health.
The operational logic:
- Define the inactivity threshold — typically 90 days of no clicks for a consumer list, 60 days for a transactional or high-frequency list.
- When a subscriber crosses the threshold, move them to a re-engagement segment.
- Send one re-engagement campaign: a single email with a clear value proposition and a direct question ("Do you still want to hear from us?"). No hard sell, no discount bait — a genuine permission check.
- If the subscriber clicks or replies, return them to the active list and reset their engagement clock.
- If they do not respond, suppress them permanently.
Subscribers who cross the 90-day inactivity window without a re-engagement response are not potential buyers. They are potential spam reporters, recycled
spam trap hosts, and
complaint rate contributors. Removing them is not losing subscribers — it is removing inbox-placement risk.
Bridge: The Arithmetic of Clean Lists
"A thousand clean beats fifty thousand more"
This is the core deliverability argument for aggressive list hygiene. A list of one thousand subscribers who click at 10% produces one hundred click-throughs per send. A list of fifty thousand subscribers who click at 0.2% produces one hundred click-throughs per send — and the fifty-thousand-name list has fifty times the complaint rate exposure, fifty times the spam trap surface area, and a reputation profile that reflects the behavior of forty-nine thousand disengaged subscribers dragging down the signal from the one thousand who actually want the mail.
The math favors the clean list. The deliverability outcome, the ISP reputation signal, and the revenue per send all favor the clean list.
