Google & TCF
      Back to home
      1. Help Center
      2. IAB TCF
      3. Google & TCF

      Set up Google Ad Manager and Additional consent mode

      How to set up Google Ad Manager and Google Additional Consent Mode as part of the TCFv2 framework

      Google Ad Manager

      Step 1 - Add Google vendor in Didomi console

      Didomi had a direct integration with Google Ad Manager; if you have this old integration, we recommend disabling it as Google Ad Manager currently relies on the IAB TCF V2.2 for getting the user status.

      Google is part of the TCFv2 framework as vendor ID 755. Google Ad Manager, AdSense and AdMob are part of the "Google Advertising Products" vendor in the framework and in the Didomi Console:

      Google Advertisng products (Vendor)

      The ID for the Google vendor on the Didomi platform is still "google" and we recommend using this one instead of 755 in case of anything custom.

      On your CMP it looks like this:

      Capture d’écran 2021-04-20 à 18.28.52.png

      Please note that only advertising products from Google are part of the TCF.
      You can create another "Google" vendor to manage consent for non-advertising Google products like Google Analytics. You can follow this guide to do so.

      Step 2 - Enable IAB TCF Integration

      In the Didomi Console, ensure that the IAB TCF integration is enabled for your notice.
      You can activate the integration in "2. Customization" => "Integration"

      Additional consents

      For your mobile applications, you need to configure your settings by following this documentation.

      Consent for Google Ad Tech Providers is automatically collected and shared with Google Ad Manager through the Additional Consent Mode and the addtl_consent parameter. No extra configuration is required in the Didomi Console.

      On web, Additional consent mode is automatically enabled when the Google Advertising Products vendor is enabled in the Console.

      Technical Ad Delivery

      Behavior of Technical Ad Delivery

      Technical Ad Delivery relies on the IAB TCF v2.2 Special Purpose 2 (SP2) to serve ads when consent and legitimate interest are not available for the Google Advertising Products vendor or its purposes in the IAB TCF v2.2

      Technical Ad Delivery relies on Google Ad Manager collecting the user status from the Didomi CMP via the IAB TCF.

      Ads can be delivered under Technical Ad Delivery when:

      • The user has disagreed to everything (no purpose or vendor enabled).
      • The user has made granular choices that exclude the Google Advertising Products vendor and/or its associated purpose. In some limited cases of granular choices, Limited Ads can be served instead of Technical Ad Delivery-eligible ads.

      Enable Technical Ad Delivery 

      To enable Technical Ad Delivery:

      • On your website, ensure that Google Ad Manager ad requests are not paused or configured to not be sent when user consent is denied. Ads must be loaded in all cases irrespective of the user choices for Technical Ad Delivery ads to be served.
      • In your Google Ad Manager account, ensure that the Technical Ad Delivery option is enabled and that your account is correctly configured to support ads served via Technical Ad Delivery.

      Once Technical Ad Delivery is configured, you can confirm that it is correctly enabled by generating a dedicated report in Google Ad Manager.

      Once the tag is in place, you can monitor errors from Google Ad Manager. You can also read more about troubleshooting Google Ad Manager in the TCFv2.