Cookiebot and the IAB Consent Framework

To support publishers, technology vendors and advertisers in meeting the transparency and user consent requirements of the GDPR and ePrivacy Directive, IAB Europe (Interactive Advertising Bureau) has created the GDPR Transparency and Consent Framework (TCF v2.0).

As the framework is widely supported by the online advertising industry, Cookiebot is registered and certified with IAB as a consent management provider (CMP id 134) and has adopted the framework as an optional supplement to the core consent framework already included in the Cookiebot solution. The integration also covers Google's "Additional Consent Mode" (Google AC) as a bridge for vendors who are not yet registered on the IAB Europe Global Vendor List (GVL).

Concept

IAB’s consent model is fundamentally different from Cookiebot’s core consent model. In general, IAB’s model puts control in the hands of advertisers and vendors by signaling the user's consent to advertising vendors, whereas Cookiebot can block non-consented vendors and thereby gives control to the publisher, who is liable for all tracking performed by third parties on the publisher’s website. Nevertheless, the two consent models can co-exist on a single website.

With version 2 of TCF, IAB have introduced strict policies on the wording and configuration of the cookie consent banner.  When using the Cookiebot integration with IAB TCF, a standard, non-editable, IAB-certified message will be displayed in your banner before the text that you have defined in the Cookiebot Manager. Read more about the standard message and auto-configuration of the banner here: https://support.cookiebot.com/hc/en-us/articles/360015693200.

An extra panel with the title "Ad Settings" will automatically be available to the end user on the cookie banner:

To ensure that vendors honor the user’s consent, Cookiebot CMP’s scanner monitors all cookies and similar trackers used on the website. If an IAB-vendor does not honor the user’s consent, cookies set by the vendor will be marked up in the scan report with “Prior consent enabled: No”.

Implementation

Enabling the IAB framework with Cookiebot CMP is straightforward: Just add the data-framework attribute to your existing Cookiebot tag with the value “IAB”, e.g.:

<script
  id="Cookiebot"
  src="https://consent.cookiebot.com/uc.js"
  data-cbid="00000000-0000-0000-0000-000000000000"
  data-framework="IAB"
  type="text/javascript"
  async
></script>

If you are using the standard Cookiebot template from the Google Tag Manager Gallery, you can check the "Enable IAB Transparency and Consent Framework" option to enable TCF on your site.

If you are loading Cookiebot via a custom setup in a tag manager, e.g. via a custom HTML tag in Google Tag Manager, which automatically strips all attributes but "src" from the script tag, you can enable the IAB framework by including the "data-framework=IAB" query parameter to the tag src-attribute, e.g. "https://consent.cookiebot.com/uc.js?cbid=00000000-0000-0000-0000-000000000000&data-framework=IAB".

You will also need to add the following line of code above your global site tag or Google Tag Manager snippet on all pages where you have Google Ads tags:

window ['gtag_enable_tcf_support'] = true;

From there, Cookiebot will automatically signal consent to any vendor using the IAB framework on your website.

Publisher restrictions

<script id="CookiebotConfiguration" type="application/json" data-cookieconsent="ignore">
  {
    "Frameworks": {
      "IABTCF2": {
        "AllowedVendors": [2, 6, 8],
        "AllowedGoogleACVendors": [],
        "AllowedPurposes": [1, 2],
        "AllowedSpecialPurposes": [],
        "AllowedFeatures": [1],
        "AllowedSpecialFeatures": [1],
        "VendorRestrictions": [
          {
            "VendorId": 2,
            "DisallowPurposes": [2, 3, 4]
          }
        ]
      }
    }
  }
</script>

For IAB Vendors

__tcfapi('getTCData', 2, (tcData, success) => {
    success && console.log(tcData);
});

__tcfapi('addEventListener', 2, (tcData, success) => {
    success && console.log(tcData);
});