- TCF v2.1: We will continue accepting TCF v2.1 strings, but encourage CMPs to follow IAB guidance on implementation milestones as the industry moves over to TCF v2.2.
- Google consent management solutions: Google consent management solutions, available in Ad Manager, AdSense and AdMob's Privacy & messaging tab, plans to support TCF v2.2 for its GDPR consent messages by early November, in alignment with the IAB's updated 20 November 2023 implementation deadline for CMPs.
IAB Europe has finalised v2.0 of its Transparency and Consent Framework developed with IAB Tech Lab and mutual member companies. Google now fully supports TCF v2.0.
To give publishers time to manage errors and misconfigurations related to the launch of IAB Europe’s Transparency & Consent Framework v2.0, Google will provide publishers with a report of errors that we’ve detected and a 150-day grace period in which to resolve the errors.
In this article, you'll find more information about how to address TCF v2.0 implementation errors, including:
- Reminder about the TCF requirement to re-obtain consent every 13 months:
You are required by IAB TCF policy to remind users about their consent choices at least once every 13 months. If the consent decision is more than 13 months old, the TC string will no longer be considered valid by Google and Google will not serve ads to that user. We suggest that you work with your CMP to remind users about their consent choices before the 13-month limit is reached.
- The 3.2 error type has been eliminated. TC strings that were updated in the last 13 months will remain valid.
Fixes for common errors
Troubleshoot some of the most common errors across Ad Manager, AdSense and AdMob by taking the following actions:Consider re-consenting users with TC strings that won't monetise
(Errors 1.1, 3.1, 4.1, 5.1, 5.2 and 6.1)
Consider re-requesting consent from users.
Publishers will benefit from re-requesting consent if they'd previously used out-of-band, globally scoped strings, invalid CMP IDs (from testing), invalid GVL IDs (from testing) or were missing Google as a vendor with proper consent at some point during their implementation.
Errors 1.1, 1.2, 1.3: It's important to check if these errors represent a significant volume of traffic. If so, consider that there might be an issue on the CMP side and make sure that Google is granted consent on the purposes needed as well as being a vendor for consent AND legitimate interest (vendor ID 755).
Per IAB specifications, CMPs may cache consent strings for 13 months.
(Errors 2.1a, 2.1b, 2.2a, 2.2b and 2.2c)
While there’s no longer a timeout requirement, we suggest that CMPs closely review their implementations to ensure that they immediately return calls to
If a CMP doesn’t respond, the request may go unmonetised.
Google adheres to the IAB specification stating that a CMP should reply immediately to the
AddEventListener function. If a CMP doesn’t respond immediately, then the request may go unmonetised.
Additionally, CMP responses are part of the chain of events that influence how soon an ad request can be made. Decreasing the time between page load and ad requests results in fewer lost impressions for the publisher.
Applicable IAB specification: IAB AddEventListener specification (on GitHub)
AddEventListenercallback should be called immediately upon registration with the current TC data, even if the CMP status is
loadingand the CMP has incomplete TC data. This enables the calling script to access its registered
listenerId. Furthermore, on every TC string change, the callback should be called unless it's removed using
We’ll notify publishers in the product user interface if we detect an issue on the TC string associated with one or more of their sites or apps. On the 'EU user consent' page in their account, publishers with errors can click Download TCF error report to download a detailed report of the errors that have been detected over the last seven days.
- Ad Manager: Click Admin EU user consent.
- AdMob and AdSense: Click Blocking controls EU user consent.
The report will contain the following information about each of the detected errors:
- Domain/MobileAppID: The site or mobile app that's misconfigured.
- Ad unit path: The ad unit associated with the error.
- Error code: The code assigned to the error.
- Error count: The number of queries containing the error that were observed during the previous week.
- Last detected date: The last date on which the error was detected.
Publishers can use the error codes listed in the report to find the suggested actions to be taken in the following troubleshooting tables and resolve the errors.
To help publishers fix misconfigured IAB TCF v2.0 integrations, we’ve assembled the following tables of the most common TC string error types as well as corresponding troubleshooting recommendations.
Use the tables to understand the issues occurring at the ad-request level as well as the corresponding system behaviour.
Scenarios 1.1 and 1.3 always result in dropped and unfilled ad requests. Scenario 1.2 will not. All three of these scenarios will always take precedence over misconfiguration errors, even if a given request has multiple errors.
|Scenario||Description||Suggested action to take|
|1.1||Google, as a vendor, isn't allowed under consent or legitimate interest. Ad requests are dropped and unfilled.||Confirm whether the user intentionally rejected Google as a vendor, CMP implementation errors have occurred or there are publisher restrictions.|
|1.2||No consent for Purpose 1 for EEA countries and the UK.||
Confirm whether the user intentionally disallowed Purpose 1 or if this is due to CMP implementation errors.
Publishers in Switzerland should ensure they are setting the
Starting December 2021, we will no longer check for
|1.3||Has consent for Purpose 1, but lacks legal bases for Basic Ads. Ad requests are dropped and unfilled.||
Confirm whether the user intentionally rejected legitimate interests on the other purposes or if this is due to CMP implementation errors.
Ad requests won't be filled while misconfiguration errors exist.
|Error||Description||Suggested action to take|
|2.1a||Tag or SDK isn’t receiving a TC string due to CMP status being
If you're manually invoking the function to request ads, make sure that the response to
If you’re not manually invoking the function to request ads, then work with your CMP to ensure they implement support for
Both conditions are met:
|Ask your CMP to make sure that their APIs are properly implemented based on the IAB TCF tech specification.|
The TC string is not parseable because it isn’t base64 encoded.
|CMPs (or publishers) should only send base64-encoded data in
The TC string is not parseable because of a decoding error.
Example: Includes an incorrect number of bits
|CMP should fix the TC string implementation errors.|
The TC string is not parseable because of a data error.
Example: Incorrect timestamp, vendor ID is too large
|CMP should fix the TC string implementation errors.|
Problems with the TC string associated with an ad request. Ad requests will be dropped and unfilled.
|Error||Description||Suggested action to take|
|3.1||Invalid CMP ID.||
Make sure an IAB-validated CMP is being used and its ID is correctly set in the TC strings.
If a CMP was valid when a TC string was generated but was later deleted by the IAB, you need to reobtain consent using a valid CMP.
|3.2||No longer used.||None. Previous meaning: The TC string creation date was more than 13 months ago.|
Consent must be obtained from the user. If you obtained consent from a user over 13 months ago or using a version of the GVL in which Google was not yet listed, you should re-obtain the user's consent, otherwise ad requests will be dropped and unfilled.
|3.3||The TC string last updated date was more than 13 months ago.||
CMP should delete the old TC string and re-obtain consent.
It is expected that a small number of these errors may occur if ad requests are sent with an expired TC string before the CMP has invalidated and re-obtained the user's consent.
If you are using Google’s consent management solutions, review the troubleshooting steps for apps to resolve 3.3 errors.
|4.1||The TC string was generated using a version of the GVL in which Google was not yet listed.||Re-obtain consent using a current version of the GVL.|
|5.1||The TC string allows out-of-band consent.||Instruct your CMP to remove out-of-band signals from the TC strings.|
|5.2||Globally scoped TC string.||Instruct your CMP to update the TC strings to be service specific.|
Personalised and non-personalised ads will continue to be served using the existing settings without impacting monetisation.
|6.1||TC string version is
||CMP should send TCF v2.0 strings.|
When these issues occur, Google will mitigate the problem itself, when necessary, and proceed with normal TCF handling.
|7.2||The TC string was generated with a GVL version newer than the current version known to Google's ad serving technology.||N/A|
|7.3||Some purposes, features and/or vendors are out of range (unknown).||N/A|
|7.4||The TC string has an older
||CMP should delete the older TC string and reobtain consent using the newest GVL.|
A request has
|7.6||Invalid publisher country code, but consent to Purpose 1 is present.||CMP should fix the TC string implementation errors.|
|7.7||Invalid language code.||Only limited ads will be served. CMP should fix the TC string implementation errors.|
|7.8||TC string version field is neither
||Only limited ads will be served. CMP should fix the TC string implementation errors.|
|7.9||AC string version is not
||CMP should set the AC string version to
When these issues occur, Google will treat the Additional Consent (AC) string as invalid and no additional vendors will be considered beyond the TC string.
|8.1||AC string is not using the version separator (
||CMP should use '
|8.2||AC string contains a vendor list that doesn't follow the expected formatting (list of int64s separated by ' . ')||CMP should fix the AC string implementation errors.|