Google IAB TCF v2 Error Codes & Guidance

Google has joined TCF v2 and publishers / advertisers that use Google Ad Manager or other Google Ads products may receive error messages about their setup and implementation of a TCF v2 CMP.

As we work through Google’s implementation of TCF v2 and the impacts of their integration on publishers. The Quantcast Team will continue to examine the issues that arise around Google error codes for Choice customers integrating with Google on TCF v2. We are working on making this as smooth of a transition as possible. Thanks.

Google has catalogued the error codes they will be providing to their clients here: https://support.google.com/adsense/answer/9999955?hl=en.

Quantcast has cataloged the error codes, reasons they arise with Choice and ways to address them here: https://help.quantcast.com/hc/en-us/articles/360052292554-Google-IAB-TCF-v2-Error-Codes-Guidance

Quantcast has also created additional Google specific help related to Quantcast Choice that can be found here: https://help.quantcast.com/hc/en-us/sections/360009359354-Integration-with-Google-on-TCF-v2

All of the Quantcast Choice documentation can can be found on the help center here: https://help.quantcast.com/hc/en-us/categories/360002940873-Quantcast-Choice

The two primary errors people seem to be seeing are 1.1 and 2.1a.
– 1.1 – If you are seeing this error code it is likely that some users are just not giving Google consent. Unless you are seeing this in an abnormally large % of users it is likely just users not giving consent to google.
– 2.1a – If you are seeing this error code it is likely that you are loading Google tags before receiving are response form Choice with the users consent string and you will likely have to make some updates to prevent your tag from loading before Consent is known. This can be a rather difficult problem to solve due to the number of different ways tags can be added to a website. We are working to provide more detailed guides & examples to help you solve these errors. (On a personal note, having implemented this in WordPress many times I think the easiest setup to use is 1. Adding Choice with the WordPress plugin and using the “send consent signals to the data layer” plugin option. 2. Adding other third party tags with Google Tag Manager after reading consent signals from the data layer. If you implement the IAB Consent and Non-IAB Consent variables from this guide here https://help.quantcast.com/hc/en-us/articles/360052555693 you can now read the consent data, in GTM, that was passed to the data layer by Quantcast Choice and use those signals to create triggers as shown here: https://help.quantcast.com/hc/en-us/articles/360051794434-TCF-v2-GTM-Implementation-Guide-IAB-Vendor-Tag-Blocking).

Solving these issues may be difficult and may require changes in setup to ensure the proper firing of tags to prevent calls before user consent has been established.

• This topic was modified 3 years, 8 months ago by Ryan. Reason: Closing out opening message
• This topic was modified 3 years, 8 months ago by Ryan. Reason: Updating for clarity