If the same unwanted website, app, or YouTube placement keeps appearing across campaigns, copying the exclusion into each campaign creates more than busywork. One missed list can expose the account again, while an old list can continue restricting delivery after everyone has forgotten why it exists.
Google Ads can now apply one account-level placement exclusion list across Performance Max, Demand Gen, YouTube, and Display campaigns. That gives you a central brand-safety boundary, but it also increases the impact of every exclusion decision. The useful approach is to centralize only the rules that truly belong to the whole account.
Decide what deserves an account-wide exclusion
An account-level exclusion is effectively a non-negotiable instruction: this placement must not receive spend from any eligible campaign in this Google Ads account. Use that scope only when the rationale remains valid regardless of the campaign’s audience, creative, offer, or objective.
Before moving a placement to the account level, ask four questions:
- Have you identified the exact website, app, or YouTube placement that should be blocked?
- Does the reason apply to every Performance Max, Demand Gen, YouTube, and Display campaign in the account?
- Would you keep the exclusion if a new eligible campaign launched tomorrow?
- Can the decision be justified as an account-wide brand-protection or relevance rule, rather than one campaign’s temporary performance problem?
If any answer is no or uncertain, keep the decision closer to the affected campaign or ad group until its scope is clear. Centralization improves consistency; it does not turn a contextual judgment into a universal one.
| Situation | Best scope | Reason |
|---|---|---|
| A placement violates a firm-wide brand-safety standard | Account level | The rule should hold across every eligible campaign |
| A placement is irrelevant only to one product, audience, or campaign | Campaign or ad-group level | The reason depends on local context |
| The same placement is excluded everywhere for the same documented reason | Candidate for account level | Centralization can remove duplication and reduce omissions |
| The placement merely produced disappointing results in one context | Do not broaden yet | Weak local performance does not establish an account-wide prohibition |
| Different campaigns treat the placement differently | Resolve the conflict first | A universal exclusion would erase an intentional exception |
This distinction matters because low quality and poor fit are not always permanent properties of a placement. An account-wide block is a binary policy control. It should not become a substitute for understanding why one campaign struggled.
Consolidate existing lists without importing every old mistake
The tempting migration method is to combine every campaign and ad-group list, remove duplicate rows, and publish the result at the account level. That creates a complete list, but not necessarily a correct one. It preserves the exclusions while discarding the context that originally limited them.
Treat consolidation as a classification exercise:
- Inventory the current rules. Collect the active placement exclusions from eligible campaigns and ad groups. Record where each one is applied before changing its scope.
- Normalize each entry. Capture the exact placement, whether it is a website, app, or YouTube placement, and the stated reason for blocking it. Deduplicate exact matches, but do not assume related properties deserve the same treatment.
- Assign one of three scopes. Mark each exclusion as universal, campaign-specific, or unresolved. Only the universal group should move directly to the account level.
- Investigate conflicting treatment. If one campaign excludes a placement while another allows it, do not automatically promote the strictest rule. Determine whether the difference is intentional or simply the result of inconsistent maintenance.
- Review the proposed central list. Compare it with the universal group, confirm that every entry has an account-wide rationale, and have the person responsible for brand safety approve the result.
- Apply and verify before cleaning up. Confirm that the relevant Performance Max, Demand Gen, YouTube, and Display campaigns are covered and that the blocked placements no longer receive spend. Keep narrower exclusions in place until that verification is complete, then remove only the redundancy you have confirmed.
Record the account’s delivery pattern before applying a large list. An account-level block that is too broad can unintentionally limit reach, so you need a baseline that makes an unexpected contraction visible. The goal is not to preserve every impression; it is to distinguish an intended brand-safety effect from an accidental loss of useful inventory.
Avoid the three most expensive scope errors
Using the central list as a bin for weak performers
A placement that performed poorly in one campaign may be unsuitable for that campaign without being unsuitable for the account. Before broadening the exclusion, separate the observed result from the proposed policy. Poor campaign-level results support a local decision; an account-level decision requires a reason that survives changes in audience, creative, offer, and objective.
A useful test is to finish this sentence: We prohibit this placement across the account because ____. If the answer is only that it did not work last month, you have a performance observation, not an enduring account rule.
Turning a partial rule into a universal rule
Suppose an app is irrelevant to one specialized campaign. Excluding it there may be sensible, but moving that exclusion to the account level also removes it from otherwise eligible automated, video, demand, and display activity covered by the central control. The original rationale no longer supports the larger consequence.
Watch especially for legacy lists named after broad concerns such as quality or relevance. A label is not evidence of scope. Inspect the entries and their reasons individually before treating the list as account-wide policy.
Assuming a central control can govern itself
Performance Max and Demand Gen make central boundaries especially useful because campaign delivery is highly automated. The exclusion list tells that automation where it cannot spend; it does not decide which boundaries are commercially or strategically correct.
Do not judge the list by its size. A larger exclusion count is not inherently safer, and a shorter list is not inherently more efficient. Judge it by two outcomes: prohibited inventory is consistently blocked, and acceptable reach is not being removed without a documented reason.
Run the exclusion list as an account policy
Once a placement list affects several campaign formats, it is no longer just a setup detail. It is a shared account control with a larger operational impact. Give it an owner, a change record, and a defined review trigger.
For every account-level entry, retain:
- The exact placement and whether it is a website, app, or YouTube placement.
- The date it was added.
- The specific reason for the exclusion.
- Why that reason applies across the entire account.
- The requester and approver.
- The event that should trigger reconsideration, such as a business change, a resolved brand concern, or an unexpected reduction in reach.
Assign one person or team to maintain the central list. Campaign managers can still propose additions, but the account owner should check whether the reason is universal before approving them. That small approval boundary prevents a local troubleshooting action from quietly changing every eligible campaign.
After a material change, inspect Performance Max, Demand Gen, YouTube, and Display separately. Confirm that excluded properties are not receiving spend, then look for delivery changes that were not part of the plan. If an unwanted placement still appears, verify its exact identity and the campaign’s eligibility before adding broader exclusions. If reach contracts unexpectedly, inspect the latest additions first and move contextual rules back to the narrower level where they belong.
Review the list when the account’s business scope changes, when a new campaign introduces a materially different audience or offer, or when an entry no longer has a defensible rationale. Trigger-based review is more useful than a vague instruction to check the list regularly.
Key takeaways
- One account-level placement exclusion list can prevent spend on selected websites, apps, and YouTube placements across Performance Max, Demand Gen, YouTube, and Display campaigns.
- Use the account level for permanent, universal rules rather than campaign-specific performance judgments.
- Do not build the central list by taking the union of every legacy list. Classify each exclusion as universal, contextual, or unresolved first.
- Verify both sides of the change: prohibited placements should stop receiving spend, and useful reach should not disappear without an intentional reason.
- Give the list an owner and preserve the rationale, scope, requester, approver, and review trigger for every entry.
Start with the placements already repeated across several eligible campaigns. Move only those whose rationale remains true everywhere, verify the result, and leave contextual exclusions close to the campaigns that need them. That gives you one dependable brand-safety boundary without turning centralization into unnecessary reach loss.
Leave a Reply