Guide to enabling the IAB Consent Management Provider Framework
About the IAB Framework:
(or go directly to the tutorial)
The IAB Europe Transparency & Consent framework is an initiative of IAB Tech Lab — a non-profit organization made up of digital publishers, ad-tech companies, marketers, and other companies involved in interactive marketing. The board is made up of some pretty well-known brands such as Google, AppNexus, LinkedIn, Microsoft and others.
This Framework and the associated Consent Management Provider API was developed as a way to “give the publishing and advertising industries a common language with which to communicate consumer consent for the delivery of relevant online advertising and content”.
It’s made up of an ever-growing list of publishers and advertisers that have agreed to be bound by its standards and use the framework to facilitate user choice via a convenient, easy to use interface.
The framework is, ideally, meant for first-party publishers who work with third-party advertisers (i.e publishers who run ads on their website). It’s actually it’s highly recommended that you enable this feature if you fall within this category as some advertising networks may limit access to their network if not implemented, which could, in turn, potentially decrease your ad revenue.
How it works
Vendors that register on the Global Vendor & CMP List (List) are assigned a vendor ID which allows them to retrieve and interpret user consent preferences in regards to their and other vendors’ services. The actual framework standardizes the process of getting users’ consent and allows for the seamless signaling of users’ consent preferences across the advertising supply chain.
In the middle, helping to facilitate this process are the companies operating as Consent Management Providers (CMPs). CMPs can read and/or set a user’s consent status for the vendors, and make this information available to vendors that publishers choose to work with. In regards to the Cookie Solution, iubenda operates as the CMP; once the feature is enabled, we facilitate this process automatically and painlessly for our users.
Additionally, this feature of the Cookie Solution automatically blocks the scripts of advertisers that are a part of the IAB Vendor Network (provided that the individual advertisers adhere to the standards of the of the network) prior to receiving user consent.
Despite being a relatively new initiative, the IAB Framework is rapidly becoming the industry standard with many huge vendors such as Google, Adobe and AdRoll involved in it’s implementation.
Publishers stand to benefit from this initiative in that it makes it easier to be more transparent with users and allows you as the data controller, to have more control over how your users’ data are processed and for which purposes.
We’ve worked hard to ensure that our Cookie Solution integrates seamlessly with this Framework, hereby giving you, our users, the additional option to easily enable and use it for your website and apps.
The Cookie Solution gives you the option to allow your users to customize their advertising tracking preferences directly from your website. This feature is optional as hosting the actual mechanisms for toggling preferences is not mandatory under the applicable Cookie Law.
To enable this feature, head to your dashboard and click on the website that you’d like to update. Next, click the <>EMBED button in the Cookie Solution area:
This will take you to the embed section for the Cookie Solution.
For now, the feature we’re about to enable is only available on the beta channel, therefore, this channel is automatically selected when the IAB CMP Framework is enabled. To enable, scroll to the bottom of this section and click the checkbox on the bottom left (as pictured below):
To function properly, the embedding code must be added at the very beginning of the
HEAD, right after the <HEAD> tag opening.
As mentioned above, this feature of the Cookie Solution also automatically blocks the scripts of advertisers that are a part of the IAB’s Vendor Network (provided that the individual advertisers adhere to the standards of the of the network), prior to receiving user consent.
This means that when the IAB CMP framework is enabled in the Cookie Solution, there is no need to set-up the prior blocking mechanism for the particular third parties that are a part of the IAB Vendor network.
If you’re running other scripts related to third-parties that are not included on the IAB’s Vendor List, you’ll still need to set up prior blocking for those scripts using another method.
If you installed the Cookie Solution with the IAB CMP framework activated before the addition of the of the IAB Vendor auto-blocking feature, you will need to replace the old Cookie Solution code on your website/app with the new embed code. To check if you need to do this, take a look at the Cookie Solution code currently on your site and look for the
stub.js snippet as can be seen in the image here. If the stub portion is not there, then you will need to replace that code with the current code.
Again, please remember that in order to function properly, the embedding code must be added at the very beginning of the
HEAD, right after the <HEAD> tag opening.
Note: All cookies are of course “turned off” by default as a positive affirmative/ “Opt-in” action is required for valid consent.
Launch live demo