Set up Google Advertising Products in the TCF

How to set up Google Ad Manager as part of the TCFv2 framework

Google vendor in the TCF (step 1)

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:

Didomi Compliance Console et 8 pages de plus - Personnel – Microsoft_ Edge 2021-07-02 at 10.35.34 AM

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.

Configuration for Web consent notices 

  1. Follow step 1.
  2. Select the Google Advertizing Products from the vendors list.
  3. Make sure the TCF integration is enabled. 

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.

Didomi integration (obsolete)

The Didomi integration with Google Ad Manager that relies on passing a NPA parameter to ad requests is still available in the Didomi Console. But we do not advise using it.
You can find that integration in the "Integrations" step of your consent notice:

Didomi Compliance Console et 11 pages de plus - Personnel – Microsoft_ Edge 2021-06-28 at 10.55.07 AM


Publishers will be able to continue to use Google Ad technology partners that are not on the TCF Global Vendor List (GVL) since Google supports them through Additional Consent mode. Additional consent mode is automatically enabled when the Google Advertising Products vendor is enabled in the Console.

Configuration for Mobile App consent notices

  1. Follow step 1.
  2. Select the vendors.
  3. Ensure that your SDK version is >= 1.21.0 on Android and >= 1.31.0 on iOS.
There is no other specific configuration for Google on mobile.

Grace period

Google supports "Grace Period" of 90 days from August 15th 2020 to allow publishers to manage errors and misconfiguration. Google provides detailed reporting and troubleshooting information during that period.

Misconfiguration (Grace period 0)

Google will give 30 days to publishers to use the GDPR ad tech provider controls to remedy misconfigurations without impacting monetization. After 30 days, Google will serve non-personalized ads (NPA) for the remaining 60 days of the grace period.

TC string issues (Grace period 1)

For significant flaws in the TC string, Google will only serve non-personalized (NPA) ads during the grace period.

Global scope or out-of-band scope (Grace period 3)

During the grace period, Google will read the TC string to determine whether it has appropriate lawful bases, and if so, will serve ads during the grace period. The grace period should be used to correct this issue.

Google provides more information in their Troubleshooting TCF v2.0 implementation article.

Additional consents

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.