secureprivacy.ai

Secure Privacy Support Center

Search for any help questions or topics.

[CMP v1] How to enable IAB 2.0

[CMP v1] After enabling the IAB in Secure Privacy, you will notice some changes to the cookie consent banner. The text has been aligned with the approved IAB 2.0 message
Avatar
Andrew Sidorkin
Updated 2 months ago

IAB TCF 2.0 – the latest release, is completely revamped and significantly expands publishers’ bidstream options for collecting and assigning consent. Companies must disclose specific kinds of data they use or collect and their role in ad campaigns to register for the TCF.  That means publishers need finer controls over consent data, not just on or off options.


Steps to Enable IAB in Secure Privacy 

  1. Login to your account and go to the GDPR menu

  2. Click on Settings where you will see the IAB Framework tab. Click on it. 

  3. Here you will see a toggle Enable IAB banners switch. Turn it on to enable IAB on your account (see below).

Updates done to the Preference center: After enabling the IAB 2.0, your preference center will be updated accordingly. You will have new tabs like “Partners”.


Note: you can rename all tabs by clicking on them (please select the language first).

You can also change different IAB messages under the “Edit IAB message” tab:

Updates done to the cookie consent banner: After enabling the IAB, you will notice some changes to the cookie consent banner. The text has been aligned with the approved IAB 2.0 messages, and can be changed with the WYSIWYG editor (not recommended, however, as the text is already pre-approved by IAB). See below:


Below is an example of how a standard IAB 2.0 cookie consent banner will look like. This can be customized and restyled to fit your corporate branding and styles.


IAB Consent String: When a user clicks on the accept or reject button, a new IAB 2.0 consent string is created. And can be viewed in the browser’s console. This string can be decoded via the link below:

https://secureprivacy.mgr.consensu.org/cmp/docs/#/decode


IAB 2.0 consent string would look like this in the developers console:

 

Was this article helpful?
😞 😐 😃