How to Plan DTC Exclusions and Suppression Rules

A purpose-based exclusion register fixes that.

Four reasons to exclude

Every exclusion should serve at least one purpose:

1. Protection. Avoid reaching people who should not receive the message, such as minors, or placing ads in contexts that could cause distress.
2. Compliance. Honor opt-outs, privacy choices, and platform or legal restrictions.
3. Relevance. Avoid messages that do not apply, such as acquisition ads to current patients.
4. Efficiency. Stop spending on people who have seen enough.

If an exclusion does not serve any of these, question it. If a purpose has no exclusion, you may have a gap.

The exclusion register

Adding an owner and a review date is what turns a list into governance.

Sensitive contexts

Some contexts deserve exclusion regardless of brand safety scores. News about tragedies, content about serious illness for unrelated conditions, and content aimed at children are common examples. Brand safety tools help but are not perfect. Review placement reports regularly and add specific exclusions for problems you find.

Existing patients

Suppressing current patients from acquisition messages saves money and avoids confusing them. It requires a lawful and appropriate way to identify them, usually through the brand's own opt-in programs. Do not build suppression from data you are not permitted to use for that purpose. The distinction between consent, permission, and fitness for use matters here.

Frequency as an exclusion

Frequency caps are a form of suppression. Once someone has seen enough, stop showing the ad. See frequency caps in pharma programmatic for how to set and revisit them. For CTV, household frequency needs special handling; see CTV frequency management.

Test that exclusions work

Exclusions fail silently. A misconfigured segment or a partner that ignores a list will not raise an alert. Check placement and audience reports after launch to confirm excluded contexts and segments are not receiving impressions. Include this in your prelaunch QA.

Watch for over-exclusion

Too many exclusions can shrink reach and push delivery into lower-quality inventory. If reach collapses after adding rules, review whether each still serves its purpose.

Practical takeaway

Build the register before launch. For every exclusion, write the purpose, owner, and review date. Check delivery reports against it within the first week.

Editorial note. Analysis and frameworks are the author's own and do not represent Acxiom or any current or former employer, client, or named platform. Examples labeled hypothetical or illustrative are not results from real campaigns. Nothing here is legal, regulatory, or medical advice.