Suppression List

A list of addresses or domains deliberately excluded from sending or logging. The mechanism that keeps competitors, colleagues and private correspondence out of your marketing and your CRM.

Also called: Never-Log List, Do Not Email List

What a suppression list actually governs

A suppression list is the record of who must not be contacted and on what grounds. The grounds matter more than the list: an unsubscribe, a legal deletion request, a competitor, an existing customer in an onboarding window and a named account owned by another rep are five different exclusions with five different lifespans, and collapsing them into one flag destroys the information needed to maintain them.

The practical consequence is that a suppression list is a governance artefact rather than a marketing one. It sits between a legal obligation and a routing rule, and it is usually owned by nobody in particular — which is why it tends to work until the day it does not.

One flag is not enough

A single boolean loses the reason. When the list is rebuilt during a migration, a contact suppressed for a legal request and one suppressed for being a competitor are indistinguishable, and the safe assumption for one is the wrong assumption for the other.

How to structure one that survives a migration

  1. Record the reason as a category, not a flag. At minimum: legal or consent, commercial, lifecycle, ownership, and quality. These have different review cycles and different consequences for getting them wrong.

  2. Record the source and the timestamp. An exclusion nobody can trace to an event is an exclusion nobody will be willing to remove, so the list only ever grows.

  3. Decide expiry per category. Consent suppressions generally do not expire; a lifecycle suppression such as 'in onboarding' must, or the contact is excluded permanently by accident.

  4. Suppress at the point of send, not at the point of list build. A list built on Monday and sent on Thursday has three days of new suppressions it does not know about.

  5. Reconcile against every system that can send. A suppression enforced in the marketing platform and not in the sales engagement tool is not enforced.

The diagnostic

Take the last month of outbound sends and join them against your suppression list as it stood on the send date. Any hit is a live failure. Then do the same join against the list as it stands today — the difference between the two counts tells you whether your problem is enforcement or latency, and those have different fixes.

Where it misleads

  • A suppression list that only grows is a sign the reasons are not categorised. Legitimate lists shrink at the edges as lifecycle suppressions expire.

  • Suppression at the contact level misses the account. Excluding one buyer at a competitor while emailing four colleagues is the same failure in practice.

  • Counting the list size tells you nothing. A large list built mostly from expired lifecycle rules is worse than a small one that is accurate, because it quietly removes addressable market.

  • Consent and suppression are not the same thing and should not share a field. Consent is a positive permission with a legal basis; suppression is an operational exclusion. Conflating them makes both unauditable.

RELATED TERMS

COMMON QUESTIONS

What is a suppression list?
A record of the people or accounts who must not be contacted, together with the reason each one is excluded. The reason is the important half: an unsubscribe, a legal deletion request, a competitor and an account in an onboarding window are all suppressions with different lifespans and different consequences, and a list that records only a flag cannot distinguish them.
How is a suppression list different from an unsubscribe list?
An unsubscribe list is one category of suppression — a consent withdrawal, usually permanent and legally grounded. A suppression list is broader and includes commercial and operational exclusions such as competitors, existing customers mid-onboarding, or accounts owned by another rep. Treating them as the same field is a common design error, because it makes the consent record unauditable.
Where should suppression be enforced?
At the point of send, in every system capable of sending, and checked against the list as it stands at that moment. Enforcing it at list-build time means anything suppressed between build and send goes out anyway, and enforcing it in the marketing platform but not the sales engagement tool means it is not enforced at all.
Should suppressions expire?
It depends entirely on the category, which is why categories are necessary. Consent-based suppressions should not expire. Lifecycle suppressions — in onboarding, in an active support escalation — must expire or the contact is excluded permanently by accident, which quietly removes addressable market that nobody ever notices is gone.

Build the capability

Definitions are the vocabulary. The courses are where you learn to operate it, with the interactive audit tools.

See the courses