Contact-Level vs Domain-Level Suppression

Start with the decision boundary: scope suppression to the narrowest reliable unit, then escalate to a broader block only with evidence, owner approval, and an audit trail. is evidence for a sending decision, not a guarantee of acceptance, inbox placement, relevance, permission, or replies. Keep the original value, the observation time, and the rule that converted evidence into an action. This makes a list change explainable when a later event disagrees.

A practical workflow

1. Define the event scope

An address-level unsubscribe, a person-level objection, a domain abuse pattern, and a campaign exclusion are different controls. Store scope explicitly rather than writing every event into one global blocklist.

2. Assess blast radius

Before applying a domain rule, estimate legitimate recipients, business-critical mail, subsidiaries, shared infrastructure, and exceptions. One complaint does not establish that every mailbox at a domain should be blocked.

3. Require escalation evidence

Use repeated or confirmed signals, provider evidence, and an owner-approved rule to widen scope. Set an expiry or review date for broad rules where appropriate.

4. Test before send

Run the audience against every scope, report which rule excluded each row, and sample exceptions. Keep contact-level preferences enforced even when a broader rule is later removed.

Decision table

Situation	Evidence to retain	Default action
Single address objection	Address, channel, scope, timestamp	Suppress that covered contact/channel
Person-level request	Identity evidence and scope	Suppress known contact records
Domain-level risk	Pattern, evidence, approver, review date	Hold or block domain under policy
Campaign exclusion	Campaign ID and rule version	Exclude only that campaign

Edge cases and guardrails

Domain-level suppression can over-block shared providers, subsidiaries, customers, and legitimate role addresses. Conversely, a domain block should not be used to bypass an address-level preference. Keep exception handling explicit and never let a later import erase the narrower record.

How this fits with list operations

Use outbound suppression rules for precedence and email verification statuses to keep role or catch-all flags separate from blocks. Run the list hygiene checklist before approving a broad campaign rule. Start with the lead-generation academy, then use the list hygiene checklist for the audience gate, the verification status model for technical outcomes, and the outbound suppression rules for cross-system enforcement.

A scope field should be queryable and visible in the send preview. Before a broad rule is activated, review a sample of included and excluded addresses and record the approver’s reasoning so later operators can distinguish a deliberate block from a bad join.

Sources

• Amazon SES account-level suppression list
• UK ICO: Respect people’s preferences