In this guide
A blocklist can outlive the reason it was created. A temporary exclusion from an old campaign gets copied into a new one, an ambiguous keyword blocks unrelated content, and nobody can explain which rule is responsible for lost reach.
Brand suitability is the judgment about whether an advertising environment fits a particular advertiser. Turning that judgment into targeting requires definitions, evidence, and an owner who can approve changes.
The goal of a review is to make those choices explicit. More available inventory is useful only if it still meets the campaign’s requirements.
Find every place an exclusion can apply
Start with the effective configuration, including inherited account settings, campaign lists, verification rules, publisher restrictions, and placement-specific controls.
For each rule, record the owner, reason, scope, review date, and whether it is mandatory or discretionary. If nobody knows why it exists, flag it for review rather than removing it during a delivery incident.
A simple inventory of controls often reveals conflicts. A campaign may explicitly target a publisher while a separate list excludes its domain. Another rule may exclude a whole content category even though the brief permits selected contexts within it.
Review context, not just matching words
Consider the word “shot.” It can appear in reporting about violence, photography, sport, or medical treatment. Whether an environment is suitable depends on more than the presence of the word.
Ask the classification partner what is evaluated: a page, domain, video, app, or another unit. Check what happens when content cannot be classified and how recently the classification was updated.
IAB Tech Lab’s Content Taxonomy provides categories for describing content. Confirm the taxonomy version and category mapping used by each partner. A shared label does not guarantee that two systems classify the same material identically.
Taxonomy alignment also does not make a placement suitable by itself. The advertiser still needs an approved policy for the resulting categories and contexts.
Use a sample to test a suspected problem
Suppose delivery reports show that one exclusion removes a large share of otherwise eligible inventory. Select a representative sample where the reporting permissions allow it.
For each example, compare the actual content, applied classification, advertiser requirement, and reason for exclusion. Include examples that should remain blocked as well as potential false positives. Reviewing only acceptable pages would bias the result.
Do not present a few screenshots as a measurement of the entire campaign. State the sample size, how it was chosen, and what remains unknown.
If page-level evidence is unavailable, ask the partner for a reproducible explanation. Avoid treating an opaque classification as either unquestionably correct or automatically wrong.
Test an approved change within a defined scope
Agree on the specific rule to change, the permitted inventory, monitoring period, and reversal condition. Keep unrelated safety and quality controls in place.
Measure both the additional eligible delivery and its quality. Useful checks include where ads appeared, whether the original concern recurred, and whether the change affected the campaign objective. Spend alone cannot demonstrate a successful suitability decision.
For a deal with low delivery, the private-deal troubleshooting guide helps establish whether exclusions are actually the bottleneck before anyone revises them.
Leave the list understandable
Document the decision in language the next operator can use: the original concern, evidence reviewed, approved exception or retained restriction, owner, and next review date.
Remove obsolete copies through the normal approval process and keep a version that can be restored. The result should be a set of controls someone can explain, maintain, and defend when the campaign changes.
AdOpsNow Editorial
Examples use illustrative data. See our editorial standards or report a correction.