How to set up Google Ad Manager as part of the TCFv2 framework
1- Google vendor in the TCF
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:
The ID for the Google vendor on the Didomi platform is still "google" and we recommend using this one instead of 755.
On your CMP it looks like this:
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.
2- Configuration for Web consent notices
Unlike other TCF vendors, Google Ad Manager or AdSense requires to be loaded once the Didomi CMP is ready and will not wait for the CMP to become ready.
To make sure that Google Ad Manager or Adsense works as expected with the Didomi CMP, remove your current gpt.js / adsbygoogle.js tag and load GAM or Adsense on your page after the CMP is done loading to ensure that the TC string is always available for GAM or Adsense:
Google Ad Manager
Replace your existing gpt.js tag:
<script async src="https://securepubads.g.doubleclick.net/tag/js/gpt.js"></script>
With the following:
Replace your existing adsbygoogle.js tag:
<script async="" src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>
with the following:
The Didomi integration with Google Ad Manager that relies on passing a npa parameter to ad requests is still available in the Didomi Console.
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.
3- Didomi integration
The Didomi integration with Google Ad Manager that relies on passing a npa parameter to ad requests is still available in the Didomi Console. You can find that integration in the "Integrations" step of your consent notice:
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.
4- Configuration for Mobile App consent notices
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.
5- 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.
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.