engineer, engineering, electrical engineer, electrical engineering, science, research, vehicle, cars, automobile, computer, laptop, software, testing, engineer, electrical engineering, software, software, software, software, software
Photo by This_is_Engineering on Pixabay

Inventory Quality

Part of Programmatic brand suitability

Avoiding unnecessarily broad blocklists

Audit domains, apps, channels, categories and keywords so brand suitability exclusions match the reason for each rule.

This is an editorial pen name used by the publication, not a claim of an independently verified personal identity. Original editorial credit: Measurement Desk.

undefined

A useful blocklist excludes contexts the brand has decided to avoid while leaving suitable supply available. Review each entry at the level where it operates: a page, domain, app, channel, category or keyword can affect very different amounts of inventory.

In Display & Video 360, inspect site, app and channel entries in “App, channel, and website targeting”, and keyword entries in “Keyword targeting”. Each of these areas lists the entries it holds, so open them one at a time and compare every entry with the brand policy before changing anything.

Keep the reason for each entry and narrow or retire it when that reason no longer fits. Record the entry, its reason, approver and review date so the next audit can check the same decision.

Find entries wider than their reason

Compare the current list with the approved brand policy. For each entry, identify the requirement that prompted it and check whether that requirement applies to everything the entry covers. One unsuitable article rarely establishes that an entire publisher is unsuitable.

Open the channel in “App, channel, and website targeting”: a channel may contain many sites or apps, and its name will not tell you which ones. Review the members it covers rather than inferring scope from the label, and do not assume a channel-level entry has been checked against its individual members.

Take particular care where one entry covers more than one app, which is what a bundled ID does. Check each individual app ID against the app's own store listing before you rely on the broader exclusion.

Review negative keywords separately from page and domain entries. A word such as “disaster” could affect reporting the brand accepts as well as content it avoids. Inspect possible matches in “Keyword targeting” rather than assuming every match is unsuitable.

Judge an entry by what it reaches, not by how long it has been in the list: an entry is overbroad when it covers contexts the written policy does not name. A whole-domain exclusion added after one unsuitable article is the common case. If the concern is confined to that topic, keep the page-level or keyword entry and retire the domain entry.

Prioritise a useful review

Start with inherited rules and large groups where a change may have the broadest effect. Little recent spend is not, by itself, a reason to remove an exclusion, and a long-standing entry is not proof that its scope is still right.

Work through one entry at a time and ask what it covers. A whole-domain entry should stand only if the concern applies throughout the property. An app or bundled ID entry needs the individual app IDs the brand wants excluded. A channel entry stands while its members still fit the rule.

A broad category entry stands or falls on its definition: keep it when the definition matches the requirement, otherwise choose a narrower available control or accept the trade-off explicitly. A negative keyword goes when the related content it would affect is content the brand already accepts.

For a site, app or channel entry, verify the actual property, app ID or channel members in “App, channel, and website targeting”. For a keyword entry, inspect possible matches in “Keyword targeting”. For a category entry, read the category definition against the content the brand accepts and ask whether a narrower available control would express the requirement more closely.

LinkedIn, for example, lets advertisers set up category-level blocking based on the IAB's publisher category taxonomy to prevent ads appearing on certain types of publishers in its network (disinfocode.eu). A category entry is rarely narrow: one web filtering database lists 120M+ domains in 59 web filtering categories (packagist.org).

Check the delivery trade-off

Record the proposed change, approver and review period. Before you apply it, check that the newly eligible contexts meet the written policy, and note the current placement mix and the campaign's filtered bid reasons and auction losses for a comparable period.

Where practical, make one change at a time, then compare placement mix, filtered bid reasons and auction losses across comparable periods. Note other campaign changes so the comparison has context.

Display & Video 360 provides troubleshooting for deals and line items. If expected placements do not appear, other eligibility or auction conditions may still prevent delivery.

Keep an entry when its scope matches a current requirement, narrow it when a smaller rule expresses that requirement, and remove it when its reason has expired. Record the reason, approver and review date with each change so the next review starts from the same record.

Key Metrics to Monitor Before and After Changes

Current placement mix
Baseline view of where ads are running.
Filtered bid reasons
Identify why bids were filtered out pre-change.
Auction losses
Measure how many auctions were lost due to eligibility.
Newly eligible contexts
Confirm they meet brand suitability policies.

More from Inventory Quality