Category: TCF and Vendors
Publisher Restrictions
Also known as: Google Publisher Restrictions
Simply put
In the context of Google's advertising products, publisher restrictions identify website, page, or app content that is restricted from receiving certain sources of advertising. When content is labeled in this way, the range of ads that can appear against it is limited. The term is used by Google Ad Manager and Google AdSense to help publishers keep their inventory compliant with Google's policies.
Formal definition
As used in Google Ad Manager and Google AdSense, publisher restrictions are labels applied to content (pages, apps, or inventory) that flag it as ineligible to receive certain advertising sources or demand. Content identified with an applicable inventory or content label has its advertising eligibility constrained accordingly, which publishers use to align their monetized inventory with Google Publisher Policies and restriction requirements. The concept as documented in the evidence is a Google advertising-eligibility mechanism and should not be assumed to be identical to any similarly named parameter in other frameworks; the evidence provided does not establish the technical relationship, if any, between this Google feature and consent-signaling frameworks such as the IAB TCF. Readers requiring detail on how advertising eligibility interacts with consent obligations under the ePrivacy rules or the GDPR should consult separate guidance, as those requirements are out of scope for this definition.
Why it matters
For publishers who monetize their websites and apps through Google's advertising products, publisher restrictions are a practical tool for keeping inventory aligned with Google Publisher Policies. When content is labeled as restricted, the range of advertising sources eligible to serve against it is constrained, which affects both the revenue a page can generate and the compliance posture of the inventory. Understanding how these labels are applied helps publishers anticipate why certain ads may not appear and how to keep their monetized content within Google's policy requirements.
Who it's relevant to
Publishers and website operators using Google ad products
Publishers who monetize inventory through Google Ad Manager or Google AdSense encounter publisher restrictions directly, because these labels determine which sources of advertising are eligible to serve against particular content. Understanding them helps publishers keep pages, apps, and other inventory aligned with Google Publisher Policies.
Ad operations and monetization teams
Teams responsible for managing ad inventory and revenue need to understand how restriction labels constrain advertising eligibility, since a restricted label can limit the demand that competes for a given placement. This informs troubleshooting when expected ads do not appear.
Compliance and privacy professionals
Privacy and compliance staff may need to distinguish this Google advertising-eligibility mechanism from consent-signaling frameworks that use similar terminology. Because the evidence here does not establish how publisher restrictions interact with ePrivacy or GDPR consent obligations, those requirements should be assessed separately rather than assumed to be covered by this feature.
Inside Publisher Restrictions
Purpose Restriction
A mechanism by which a publisher can restrict the legal basis or permitted use of a specific processing purpose for vendors operating on its property. Within the IAB Transparency and Consent Framework (TCF), for example, a publisher may restrict a purpose to consent only, restrict it to legitimate interest only, or disallow it entirely.
Vendor Scope
The set of third-party vendors (such as advertising or measurement providers) to which a given restriction applies. Publisher restrictions may be applied broadly across all vendors or narrowed to specific vendors, depending on the system in use.
Legal Basis Override
The ability to narrow or override the legal basis a vendor would otherwise rely on for a purpose. This is relevant because the ePrivacy Directive governs the placing of and access to information on a device, while the GDPR governs the subsequent processing of personal data; a publisher restriction typically signals a constraint on the latter.
Signal Propagation
The technical means by which restrictions are communicated to downstream parties. In a consent management context this often involves encoding the restriction in a consent string or equivalent signal that vendors and consent management platforms (CMPs) read and are expected to honor.
Platform-Specific Controls
Some advertising platforms use the label 'Publisher Restrictions' to describe controls over which ads, ad categories, or advertising technologies are eligible to serve on a publisher's inventory. These controls address advertising eligibility and are distinct in function from framework-based legal-basis restrictions, though the two may operate alongside each other.
Common questions
Answers to the questions practitioners most commonly ask about Publisher Restrictions.
Are publisher restrictions a feature that exists only within the IAB Transparency and Consent Framework (TCF)?
No. While the TCF does provide a publisher restrictions mechanism that lets a publisher constrain how vendors may process data or which legal bases they may rely on, the term is not exclusive to the TCF. Google's advertising products, such as Google Ad Manager and AdSense, also use "publisher restrictions" as a label in the context of advertising eligibility and controls. When you encounter the term, it is important to identify which system is being referenced, because the underlying mechanics, scope, and effects differ between them.
Does setting a publisher restriction on its own make our cookie and data processing practices compliant?
Not by itself. A publisher restriction is a technical control that constrains how vendors are signaled to process data or their eligibility to serve, but it does not replace the underlying legal obligations. In most EU jurisdictions, the placing of and access to information on a device is governed by the ePrivacy rules, while any resulting processing of personal data is governed by the GDPR, and valid consent where required must still be freely given, specific, informed, and unambiguous. Restrictions can support your compliance posture, but legal judgment about your specific facts and applicable jurisdictions remains necessary.
How do we configure a publisher restriction within the IAB TCF?
Within the TCF, publisher restrictions are typically configured through your consent management platform (CMP), which allows you to restrict specific purposes for specific vendors, for example limiting a vendor to a particular legal basis or disallowing a purpose entirely. The exact configuration steps depend on your CMP's interface and version of the framework it supports. Because implementation details vary between CMPs and evolve with framework updates, consult your CMP's current documentation and confirm that the resulting signals reflect the outcome you intend.
How can we tell whether a publisher restriction we set is actually being applied?
You can generally verify application by inspecting the signal your CMP produces and confirming that downstream vendors receive and respect it. In a TCF context, this means checking the encoded consent string and the restrictions it carries; in a Google advertising context, it means reviewing the relevant controls and reporting within the ad product. Verification should also include testing across the geographies and configurations you serve, since behavior may differ. Note that whether a given vendor honors a restriction in practice is a matter you may need to confirm through your own testing and contractual arrangements.
What is the relationship between publisher restrictions and the consent choices a user makes?
Publisher restrictions and user consent operate at different levels. User consent (or, where applicable, an objection or opt-out) reflects the individual's choices, while a publisher restriction reflects constraints the publisher imposes across the board, independent of any single user's selection. The two interact: a restriction can narrow what is permitted even where a user might otherwise have consented. Because the interaction depends on the specific system and configuration, review how your CMP or ad product reconciles the two before relying on the outcome.
Should publisher restrictions be applied uniformly across all jurisdictions we operate in?
Not necessarily. Cookie consent and data processing obligations vary between the EU, the UK, individual US states such as California under the CCPA and CPRA, and other regimes, with some relying on opt-in and others on opt-out approaches. A restriction configuration appropriate for one jurisdiction may not fit another. Many organizations tailor restrictions to the applicable legal scope, and you should assess each relevant jurisdiction rather than assume a single configuration is suitable everywhere. This entry does not resolve which configuration is lawful for your specific circumstances.
Common misconceptions
Publisher restrictions is a single, standardized feature that works the same way across all systems.
The term is used in more than one context. Within the IAB TCF it refers to a publisher constraining the legal basis or use of a processing purpose for vendors, whereas advertising platforms such as Google Ad Manager and AdSense also use 'Publisher Restrictions' to describe advertising-eligibility controls. Practitioners should confirm which system and meaning is being discussed, because the mechanics and effects differ.
Applying a publisher restriction is sufficient on its own to ensure lawful cookie use.
A restriction is a signal or configuration that supports compliance but does not replace legal judgment. Valid consent under the GDPR must generally be freely given, specific, informed, and unambiguous, and the placing of cookies is separately governed by the ePrivacy Directive as implemented nationally. A restriction does not guarantee that either requirement has been met.
Downstream vendors are technically forced to comply with whatever a publisher restricts.
Publisher restrictions rely on vendors and intermediaries reading and honoring the signal. They express the publisher's intended constraints, but enforcement depends on those parties respecting the signal and on the surrounding contractual and technical arrangements; the restriction itself is not a self-executing technical block in all cases.
Best practices
Clarify which system's 'Publisher Restrictions' you are configuring, for example a TCF legal-basis restriction versus an advertising-platform eligibility control, since they serve different functions and are not interchangeable.
Ensure that any legal-basis restriction is consistent with your underlying compliance analysis, treating the ePrivacy consent requirement for placing cookies and the GDPR requirement for processing personal data as separate obligations.
Verify that your consent management platform (CMP) correctly encodes and propagates the restrictions you configure, and test that the resulting signal reflects your intended settings.
Document the rationale for each restriction you apply, including the vendors and purposes affected, to support consent record-keeping and demonstrate accountability.
Do not rely on a restriction alone to establish lawful basis; confirm that valid consent (where required in EU and UK contexts) or an appropriate opt-out mechanism (where relevant under US state laws) is actually in place.
Review restriction settings periodically, because vendor lists, platform features, and data protection authority guidance evolve over time.
