![\"TCF](\"https:\/\/stg-coolmedia-stage.kinsta.cloud\/wp-content\/uploads\/2020\/10\/TCF-Error-Report.png\")
<\/p>\n
\u201cIAB TCF v2.0 errors detected. Download the TCF error report and go to \u2018Learn more\u2019 for guidance on how to fix\u201d<\/em><\/p>\n Error 1.1 occurs when Google, as a vendor, is not allowed under consent or legitimate interest. This issue can result in dropped and unfilled ad requests which can have a negative impact on your ad revenue. As such, they do not receive a grace period.<\/p>\n Error 1.1 occurs when Google cannot detect signals of consent or legitimate interest. This can either be caused by users intentionally rejecting Google as a vendor or a result of an outdated Consent Management Platform (CMP) configuration, which does not present users with the option to accept Google as a vendor.<\/p>\n In order to solve error 1.1, there are three steps you\u2019ll need to address:<\/p>\n Error 2.1a occurs when the tag or Software Development Kit (SDK) is not receiving a TC string due to CMP status being stub, loading or error. For 60 days from August 15, 2020, publishers will be able to fix any misconfiguration issues without impacting their monetization. If the issue is not solved between October 14, 2020 and November 13, 2020, non-personalised ads will be served regardless of existing personalised and non-personalised ad settings. After November 13, 2020 ad requests will not be filled.<\/p>\n The most common cause of error 2.1a is ad requests being made before the user provides or rejects consent. This error occurs when working with Google as a vendor because most TCF vendors check themselves whether the TC string is available before requesting an ad so that they can determine if they have a legal basis to process personal data.<\/p>\n However, Google does not check for the TC string first and instead expects the publisher to make sure the TC string is available via the CMP before requesting ads. Therefore, if an ad is requested before a TC string is made available, this results in error 2.1a.<\/p>\n Error 2.1a can be solved by adding conditional logic to ensure that the TC string is made available before an ad is called.<\/p>\n The following snippet leverages the TCF v2.0 API and GPT API to only execute the GAM auction once consent has been ascertained from the CMP. Please use it for illustrative purposes as a base to suit your particular needs:<\/p>\n The deadline for the IAB\u2019s Transparency and Consent Framework (TCF) v2.0 was on August 15, 2020 which means that Google now fully supports the<\/p>\n","protected":false},"author":1,"featured_media":9243,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[10,6,4,2],"tags":[8],"class_list":["post-6239","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-analysis","category-okonews","category-news","category-tips","tag-privacy"],"acf":[],"yoast_head":"\nHow to troubleshoot TCF v2.0 Google implementation error 1.1<\/h3>\n
What is error 1.1?<\/h4>\n
What causes error 1.1?<\/h4>\n
How to solve error 1.1<\/h4>\n
\n
How to troubleshoot TCF v2.0 Google implementation error 2.1a<\/h3>\n
What is error 2.1a?<\/h4>\n
What causes error 2.1a?<\/h4>\n
How to solve error 2.1a<\/h4>\n
\/\/TCF API listener code - add after TCF 2.0 compatible CMP initialization code has executed
\nwindow.__tcfapi('addEventListener', 2, function(tcData, listenerSuccess) {
\nif (listenerSuccess) {
\n\/\/ check the eventstatus
\nif (tcData.eventStatus === 'useractioncomplete' ||
\ntcData.eventStatus === 'tcloaded') {<\/code><\/p>\nif(!tcData.gdprApplies){
\n\/\/GDPR does not apply to this user so start GAM auction
\ngoogletag.cmd.push(function () {
\ngoogletag.pubads().refresh();
\n});
\nreturn;
\n}<\/code><\/p>\n\/\/ Deal with parsing tcData for IAB Vendor consents
\n\/\/Deal with personalized\/non-personalized Google ads based on this document: https:\/\/support.google.com\/admanager\/answer\/9805023?hl=en
\nif ((tcData.vendor.consents[755] || tcData.vendor.legitimateInterests[755])
\n&& (tcData.purpose.consents[1] && tcData.purpose.consents[3] && tcData.purpose.consents[4]
\n&& tcData.purpose.legitimateInterests[2] && tcData.purpose.legitimateInterests[7] && tcData.purpose.legitimateInterests[9] && tcData.purpose.legitimateInterests[10])) {<\/code><\/p>\n\/\/consent signals sufficient for personalized ads
\n\/\/set personalized ads and then run the GAM auction
\ngoogletag.cmd.push(function () {
\ngoogletag.pubads().setRequestNonPersonalizedAds(0);
\ngoogletag.pubads().refresh();
\n});
\n} else if((tcData.vendor.consents[755] || tcData.vendor.legitimateInterests[755])
\n&& (tcData.purpose.consents[1]
\n&& tcData.purpose.legitimateInterests[2] && tcData.purpose.legitimateInterests[7] && tcData.purpose.legitimateInterests[9] && tcData.purpose.legitimateInterests[10])) {<\/code><\/p>\n\/\/consent signals NOT sufficient for personalized ads
\n\/\/set non-personalized ads and then run the GAM auction
\ngoogletag.cmd.push(function () {
\ngoogletag.pubads().setRequestNonPersonalizedAds(1);
\ngoogletag.pubads().refresh();
\n});
\n}
\n}
\n}
\n});<\/code><\/p>\n","protected":false},"excerpt":{"rendered":"