
Campaign Setup
Part of Programmatic brand suitability
Recording campaign-level suitability exceptions: IAB
Document the reason, scope, approval, platform limits and expiry of a programmatic brand suitability exception.
undefined
A campaign-level suitability exception is a documented decision to treat a context differently for one campaign. Before changing a setting, record the reason, exact inventory, dates, approver, implementation and review plan. “Allow this deal” does not identify which suitability requirement the brand intends to change.
Name the baseline and state the exception
Where advertising or marketing communications are directed to consumers physically present in Australia, the AANA Code of Ethics applies to the advertiser or marketer with reasonable control over the communications; it is technology neutral and includes online and social media. It prohibits the harmful use of sex, sexuality or nudity in advertising and requires such content to be appropriate for the relevant audience (AANA).
Start with the approved advertiser-wide rule. Explain why it is too broad or too restrictive for this campaign’s message. Identify the content, inventory and environments involved. Distinguish a policy exception from a delivery problem: a deal may fail to spend because of creative, bidding or other targeting conditions.
IAB Tech Lab says the Content Taxonomy 2 version is based on the Brand Safety & Suitability Framework released in September 2020 by GARM in collaboration with the 4As’ Advertiser Protection Bureau (APB). Its guide tells buyers to familiarise themselves with the GARM/4A’s APB framework and the Tech Lab Content Taxonomy (IAB Tech Lab).
Record the baseline rule, including its setting and policy; the requested difference, reason and reviewed examples; and the campaign need. Define scope by line items, deals, markets, formats and dates. Name requester, brand approver and implementer. Record remaining controls, when to stop, the register’s location and owner, and saved-setting, delivery and expiry checks.
A hypothetical public information campaign might accept factual reporting on a sensitive event that a product promotion would avoid. Where the reviewed context matches the Content Taxonomy 2 label “Sensitive Social Issues”, name that category and campaign in the record rather than simply writing “news approved”.
Confirm the platform control
Before relying on a platform setting, confirm in current documentation whether it can express the requested exception and what settings it affects. Record the platform and exact control or setting label, saved value, affected campaign, line items and inventory, and whether the control overrides, adds to or leaves inherited exclusions in place. Check eligibility and limitations for the specific campaign and inventory.
Document what the control changes and whether it affects other suitability settings as well as the requested one. Do not assume it changes only the policy in question.
The available control may therefore be wider than the requested policy change. Record that difference and obtain a decision on the actual option. A narrower campaign-level control may add a restriction, but should not be assumed to reverse an inherited exclusion.
Verify and close
Before activation, capture the saved setting and affected deal or line-item IDs. Once delivery begins, inspect placements and relevant filtered-request reasons within the exception’s scope and dates, using reporting available for the campaign. Record the report or verification source and review date alongside the findings. A saved setting alone does not show where ads served.
Give the exception an end date or review trigger. At closure, update the register to record whether the exception was removed, renewed or incorporated into baseline policy, along with the approver and settings checked. Record the register’s location and owner so the decision can be found later. This keeps a temporary decision from becoming an unexplained standing rule.



