Suppression List

A suppression list sits between the audience query and the sending engine. A campaign first builds its recipient set from segment rules, then the sender subtracts every address that appears on the suppression table before a single message leaves. Matching normally runs on a normalised form of the email, so capitalisation and plus-addressing variants cannot slip past. Each entry carries a reason code such as unsubscribe, hard bounce, complaint or manual block, plus a timestamp, which turns the list into an auditable record of consent decisions.

The list grows on its own from unsubscribes, hard bounces and complaint feedback loops, and grows deliberately when you add competitors, current customers, partner domains or regions you cannot legally mail. Scope is the trade-off. A global list applied to every send is safest but blunt: it can silence contract or account notices the contact never objected to. A per-campaign list is precise but fragments the logic, and fragments are exactly what leak. Most teams keep one global layer plus narrow campaign-level exclusions.

In practice the list lives as its own object in the marketing tool or CRM, keyed by an email hash and synced across every sending channel, so a block in email also applies to SMS. Import files are checked against it before upload, not after. In a quiz funnel the result gives you a natural exclusion signal: respondents who already booked a call, or who scored into a tier you do not sell to, can be written onto the list automatically at submission.

Suppression cannot repair a bad list. If complaint rates are high because the source was scraped, blocking individual complainers only removes the people who spoke up; the rest stay silent and domain reputation keeps sliding. The table also has no sense of context: a contact suppressed for a one-off product launch stays blocked from unrelated onboarding mail unless you scoped that entry. And a suppression that lives in only one of your sending tools is not really a suppression at all.

Watch the suppression list as a share of your total database, and its growth per send. A stable low rate is normal; a jump after one campaign points at the message rather than the audience. Track complaint rate and hard-bounce rate on each send too, because both feed the list and both are the reason it exists in the first place.

The second signal is leakage: the number of messages that reached a suppressed contact, which should be zero. Audit it by sampling send logs against the suppression table after each campaign. Compare the list with your active customer base as well, to see how much reachable audience you have permanently written off and whether a re-permission campaign is worth running.

The usual failure is a second sending tool. A contact unsubscribes in the marketing platform, but the sales sequencer or the SMS provider keeps its own contact table, never sees the block, and mails the same person the following week. Fix it by naming one system the source of truth for suppression, syncing outward on a schedule, and checking every imported CSV against that table before the upload runs.

The second is suppressing too broadly. Teams dump every bounce, including soft bounces from a temporarily full mailbox, into the permanent list and quietly lose reachable contacts forever. Separate hard bounces, which belong there permanently, from soft bounces, which deserve a retry window and a failure threshold first. In the same way, an unsubscribe from one campaign type should never silently block invoices, password resets or other transactional messages.