• Hi, we are writting because Google Adsense sended a notice about TFC 2.0:

    – Error: 2.1a
    – Description: Tag or SDK isn’t receiving a TC string due to CMP status being stub, loading, or error.
    – Suggested action to take: Ask your CMP to make sure that their APIs are properly implemented based on the IAB TCF tech spec.

    Please, could you help to solve this problem after implementing TFC 2.0 from Quantcast?

    Thanks in advance!

Viewing 15 replies - 61 through 75 (of 196 total)
  • If you are using Ad Inserter you can check this page on how to configute blocks so the ad codes are not inserted before the consent is given:
    https://adinserter.pro/faq/gdpr-compliance-cookies-consent#tcf

    Basically you need to whitelist right cookie value (consent).
    Ad Inserter can check for value/property in the cookie (euconsent-v2 cookie is used by Quantcast Choice) and if the value is not present then the ad code is not inserted.

    What value/property in the cookie is present when the consent is given?

    @rbaronqc “Push IAB & Non-IAB consent data to the Data Layer” should be yes or no?

    I have just two google tags, in fact just one…adsense tag and analytics! These two are related to “We’ve detected an issue on your IAB TC string on one or more of your sites or apps” adsense notification?

    @spacetime Can you please guide where should I check the value/property in the cookie?

    Here is the description of the cookie object:
    https://adinserter.pro/faq/gdpr-compliance-cookies-consent#tcf

    Not sure which properties are set when the consent is given.

    @rbaronqc can you tell me the name of the cookie that google needs to read before show ads.

    is the value of that cookie allways the same?

    Plugin Contributor Ryan

    (@rbaronqc)

    @fjps3701 @vsharmilee I believe the cookie you are looking for is “euconsent-v2”. Choice will set that cookie (after consent is set) TCF guidelines

    @rbaronqc I see that quantcast creats 3 similar cookies euroconsent, euroconsent-v2 and googleConsent, this is why i’m asking, are you sure that is euroconsent-v2?

    one thing i’m curious to realize is how many people who have error 2.1a have auto-ads enabled.

    I think the main problem is in the auto-ads tag

    Plugin Contributor Ryan

    (@rbaronqc)

    @fjps3701, but I believe “euroconsent-v2” is the only one set after consent has been set by the user and is the one you need. (I think). Might just have to try it out. Keep in mind that just because euroconsent-v2 is sent that does not mean the user has granted google consent. Just that consent has been selected. So you may see an increase in 1.1 errors (which means a tag is added to the page where google consent was set, but google was not given consent). But I would test it out with “euroconsent-v2” and see if that solves your problem.

    Plugin Contributor Ryan

    (@rbaronqc)

    @sirvss if you enable the push consents to the data layer option it will have the same affect as Step 3 – Push consent signals to the data layer from this guide here: https://help.quantcast.com/hc/en-us/articles/360051794134-TCF-v2-Google-Tag-Manager-GTM-Implementation-Guide which would then allow you to create and use triggers as described/demonstrated in the same help center article under the title Triggers Non-IAB Vendor Tag Blocking and Firing (Such as Hotjar, Facebook, Twitter, LinkedIn, etc)

    @rbaronqc Hi!
    We found 403 issue for example at https://g-portal.hu, but there isn’t any problem with window.location.host, no traffic force to www.
    What could cause the 403 error?
    Thanks.

    Plugin Contributor Ryan

    (@rbaronqc)

    @arthuroadam looks like you missed the “-” when you registered the site here https://www.quantcast.com/protect/sites.

    You can see by the valid url here https://quantcast.mgr.consensu.org/choice/0nuhWDaS_7bxM/gportal.hu/choice.js (with “gportal” not “g-portal”). So your site is looking for https://quantcast.mgr.consensu.org/choice/0nuhWDaS_7bxM/g-portal.hu/choice.js which does not exist. Add the site, and actually because you do not force traffic to either www or non-www you should add both www and non www sites to your quantcast.com dashboard. And you should update your server configuration for force all traffic to 1 version or the other. It does not matter witch you choose, just as long as all traffic is forces to one or the other.

    @rbaronqc Thanks ?? I will check it.

    Plugin Contributor Ryan

    (@rbaronqc)

    @ibiza69 can you tell me more about how you add tags? Do you use a plugin (if so can you post the link) or you add them manually by editing the WordPress theme code? or some other way?

    Thread Starter ibiza69

    (@ibiza69)

    Good morning @rbaronqc, we rechecked all our plugins one by one, and we don’t have any plugin that ads any Google Tags. The only plugin we have is for pages (Tag Pages https://es.www.ads-software.com/plugins/tag-pages/), as in wordpress posts (tags), but only for that (tagging pages). We have checked at plugin description and doesn′t say anything about Google Tags. If you checked our site trabajoyempleo.work, you can see the ads are not showing until they accept, but we did this yesterday and waited till today to see if adsense had take the message 2.1a, but didn’t is still there, so we are so losted… We think we have everything correct, but we have to wait everytime 24hs to check what adsense says, to check if we did it ok or not. Today we just don’t know how to step foward. WE too use Ad Inserter Plugin for our ads. Any idea or maybe help? Thanks in advance for your time, we see you have a lot of people asking similar things and you didn′t rest all weekend ??

    Plugin Contributor Ryan

    (@rbaronqc)

    @ibiza69 I believe the problem lies with the Ad Inserter Plugin or perhaps your configuration of that plugin. I just visited the trabajoyempleo website, I see the CMP popup, as expected, but BEFORE I set/save my consent I can see ads already loading on the page in the background. The Choice CMP is loading as expected and setting the ‘euconsent-v2’ when the user makes their consent selections, but your Google Tags are being added to the page before consent is set by the user (error 2.1a) Ad Inserter Plugin gives guidance here https://adinserter.pro/faq/gdpr-compliance-cookies-consent but I have not had a chance to go through and test out the instructions, but currently you are definitely adding tags to the site before consent is established, I can see the ads added before I give consent.

Viewing 15 replies - 61 through 75 (of 196 total)
  • The topic ‘Google Adsense Problems and Notice’ is closed to new replies.