Set up Publisher restrictions in the Didomi Console [NEW FLOW]

📕 IAB TCF version 2 allows publishers to set restrictions on the purposes and legal basis used by vendors.

Didomi currently supports four types of restrictions:

  • Allow purpose - allow vendors to process data for the specified purpose.
  • Disallow purpose - do not allow vendors to process data for the specified purpose.
  • Require consent - only allow a purpose to be processed with consent as a legal basis.
  • Require legitimate interest - only allow a purpose to be processed with legitimate interest as a legal basis.

If you would like to apply restrictions, you can manage these directly in Didomi's console for  web notices only.

Create a restriction

  1. Go to Consent Notices and click to edit a notice.
  2. Go to  step 1. Regulations, then the Regulations tab, and click on Edit Vendors & Purposes under your chosen regulation, next to the number of vendors and purposes. Capture d’écran 2023-03-29 à 18.19.55
  3. Scroll down to IAB TCF Publisher Restrictions and click on Add restriction
    Capture d’écran 2023-03-09 à 12.35.31
  4. By clicking on Add restrictions +, a new window appears. Choose a purpose and the type of restriction you want to add.
    Capture d’écran 2023-03-09 à 12.36.39
  5. You can choose to apply the restrictions to all IAB vendors or selected vendors.Capture d’écran 2023-03-09 à 12.39.55
  6. You can also choose your restriction, allow or disable a purpose for your selected vendors, or force a legal basis.Capture d’écran 2023-03-09 à 12.39.59
  7. Click on Save.

Capture d’écran 2023-03-09 à 12.41.58

⚠️ Restrictions cannot be applied to Purpose 1 ("Store and/or access information on a device") or to Special Features ("Use precise geolocation data" and "Actively scan device characteristics for identification").

Mobile Applications

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

  • 1.25.0 (Android)
  • 1.37.0 (iOS)

✍️ Please note that, due to TCF V2 technical specifications, publisher restrictions are heavy 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 will 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).

📰 Please also bear in mind that Special Features ("Use precise geolocation data" and "Actively scan device characteristics for identification") do not work based on legitimate interest. For this reason, neither "Require consent" nor "Require legitimate interest"  should be applied to these features.