> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/consent-management-platform-cmp/frameworks-regulations/iab-tcf/publisher-restriction.md).

# Publisher restriction

When an IAB vendor registers with the IAB Transparency and Consent Framework (TCF), they declare the purposes, special purposes, features, and special features for which they process data and the legal basis (consent or legitimate interest) used to process that data. These declarations are recorded in the IAB TCF Global Vendor List (GVL).

Despite these declarations, your organization can utilize publisher restriction to override certain aspects of what is recorded in the GVL for the IAB vendor and alter the vendor's behavior on your property. In this article, we will cover:

* [Publisher restriction overview](#publisher-restriction-overview)
* [Publisher restriction rules](#publisher-restriction-rules)
* [Configure publisher restriction](#configure-publisher-restrictions)

{% hint style="warning" %}
**Note**: Due to the TCF v2 technical specifications, publisher restrictions can be large and will increase the size of your `euconsent-v2` cookie. In some cases, the cookie will be too large for a browser, which generally has a 4096 byte limit.

As a result, the browser may be unable to store the cookie and TCF v2 will not work properly (this explains why you could encounter errors related to publisher restrictions in your browser console).
{% endhint %}

***

### Publisher restriction overview

In the table below, review the possible restrictions your organization can place on an IAB vendor associated with your IAB TCF consent notice:

{% hint style="info" %}
The following publisher restrictions are not available for every declaration made by an IAB vendor. Please see [Publisher restriction rules](#publisher-restriction-rules) for more information. 
{% endhint %}

<table><thead><tr><th width="232">Restriction</th><th>Description</th></tr></thead><tbody><tr><td>Allow purpose for selected vendors only</td><td>Allow the selected vendors to process data for the specified purpose</td></tr><tr><td>Do not allow purpose for selected vendors</td><td>Do not allow the selected vendors to process data for the specified purpose</td></tr><tr><td>Require consent for selected vendors</td><td>Only allow the selected purpose to be processed with consent as a legal basis for the specified vendor(s)</td></tr><tr><td>Require legitimate interest for selected vendors</td><td>Only allow the selected purpose to be processed with legitimate interest as a legal basis for the specified vendor(s)</td></tr></tbody></table>

### Publisher restriction rules

When configuring publisher restrictions, your organization will want to keep the following rules in mind:

<table data-header-hidden><thead><tr><th width="174"></th><th></th></tr></thead><tbody><tr><td>Purposes</td><td><p>For Purpose 1: Store and/or access information on a device, there are no publisher restrictions available</p><p></p><p>For Purpose 3-6, which are listed in order as:</p><ul><li>Purpose 3: Create profiles for personalised advertising</li><li>Purpose 4: Use profiles to select personalised advertising</li><li>Purpose 5: Create profiles to personalise content</li><li>Purpose 6: Use profiles to select personalised content</li></ul><p>declared legal basis for these purposes will always be consent. Your organization can only apply the following restrictions:</p><ul><li>Allow purpose for selected vendors only</li><li>Do not allow purpose for selected vendors</li></ul></td></tr><tr><td>Special Purposes</td><td>No publisher restrictions are available for vendor special purposes</td></tr><tr><td>Features</td><td>No publisher restrictions are available for vendor features</td></tr><tr><td>Special Features</td><td><p>Declared legal basis for special features (always consent) cannot be restricted. Your organization can only apply the following restrictions:</p><ul><li>Allow purpose for selected vendors only</li><li>Do not allow purpose for selected vendors </li></ul></td></tr></tbody></table>

### Configure publisher restrictions

{% hint style="info" %}
**Mobile Applications**

If you wish to use publisher restrictions on a Mobile application, please update your SDK to at least:&#x20;

* 1.25.0 (Android)
* 1.37.0 (iOS)
  {% endhint %}

In order to configure a publisher restriction, click **Consent notices** on the left-hand panel and then select your consent notice that utilizes the IAB TCF framework.

<figure><img src="/files/3BPZ3poeqOcsmJqtXE7k" alt="" width="563"><figcaption></figcaption></figure>

Ensure the **Regulations** tab and **Regulations** sub-tab are selected and click **Edit Vendors & Purposes** inline with GDPR.

<figure><img src="/files/JwxYpanx90r0z4cQ1qg4" alt="" width="563"><figcaption></figcaption></figure>

Navigate to the **TCF settings** section on the subsequent page and click **Add restriction**.

<figure><img src="/files/34XSuthBflEdfz6UOaEs" alt="" width="563"><figcaption></figcaption></figure>

Use the provided **Purpose** field in the modal to select a purpose/special feature for which you are implementing the restriction.

<figure><img src="/files/TAZNyzyoegXpYkH8U7rO" alt="" width="375"><figcaption></figcaption></figure>

Once a purpose is selected, select the vendor(s) to which the restriction on the purpose will be applied.&#x20;

<figure><img src="/files/EeguRFuEil0JRIfUA0Ly" alt="" width="375"><figcaption></figcaption></figure>

With the purpose and specified vendors configured, use the provided toggles to select the restriction your organization wishes to implement.

{% hint style="info" %}
Refer to the [publisher restriction rules](#publisher-restriction-rules) for the available options for each purpose, special purpose, feature, and special feature.&#x20;
{% endhint %}

Click **Save** when finished.

<figure><img src="/files/kP0bZZACR3z7f5EDeYRb" alt="" width="375"><figcaption></figcaption></figure>

All configured publisher restrictions will be listed in the **IAB TCF Publisher Restrictions** accordion of the **TCF settings** section.

<figure><img src="/files/75UtbxPV6iCHM93v21Ax" alt="" width="563"><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.didomi.io/consent-management-platform-cmp/frameworks-regulations/iab-tcf/publisher-restriction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.