• 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 - 46 through 60 (of 196 total)
  • @rbaronqc Thank you. I still need assistance i try to add all procedures for GTM but i mixed everything up, please if there is someone to help me with it.

    Hi there! From the last four days I think, I faced the following notify in my adsense account, an I thhink it’s quantcast related:

    “We’ve detected an issue on your IAB TC string on one or more of your sites or apps. These errors may affect your ability to serve ads to European users. A detailed report is available for you on the EU user consent page.”

    What shoul I do in order to get rid of this annoying notify? I tried everything, updated plugins, new tcf 2.0 tag, nothing.

    I use Quantcast Quantifier for the tag, I changed today from Insert Headers and Footers.

    My quantcast popup appear but I stil face notify in adsense account.

    My website which google notified me about, it’s> https://www.criticmedia.ro/

    Thanks!

    Plugin Contributor Ryan

    (@rbaronqc)

    @sirvss

    The 2.1a error means you are loading Google tags onto your site before you have established user consent. I don’t know how you are adding the tags to your website, but it is very likely the the method you are using is NOT waiting for consent before adding the tags to the website. If you’re using a WordPress plugin to add Google tags to your site it is very likely this plugin is not waiting for consent before adding the Google tag (error 2.1a). You will likely need to contact the plugin author (plugin that is adding your google tags) and ask them how to wait for consent before adding the Google tags with their plugin. I think some plugins may have to adjust when and how they drop google tags, checking/waiting for consent first.

    The Choice plugin cannot stop other plugins from adding tags to a site (no plugin can), instead it collects and saves consent data and makes it accessible so that others can read it and make decisions based consents provided by users. In this case plugins that add Google Tags to your site have to wait for consent before adding tags. If plugins add tags before consent is established you will get a 2.1a error. Quantcast Choice cannot stop them from adding tags, hence the errors. We can only provide the consent signals/choices, that data still needs to be acted upon in this case. It is likely those plugins need to adjust and make sure they wait for consent to be established before adding tags to your site. I’m guessing that many plugins that add Google tags to sites are actively working on a solution to follow TCF v2 guidelines and wait for consent before adding tags. Until they update, im not sure there is much you can do unless you want to consider adding your tags with a different method like google tag manager.

    @rbaronqc thanks for your reply!

    As I said, right now I use for tag, Quantcast Quantifier. There is a workaround or a specific way for adding tag with Google Tag Manager in order to make this to work? I didn’t work before with GTM plugin! You have a tutorial or a step by step procedure?

    Thanks!

    Plugin Contributor Ryan

    (@rbaronqc)

    @sirvss what are you using the Quantcast Quantifier plugin for? That plugin has not been updated in 9 years (and was not created by Quantcast). I would suggest removing. Im assuming the sole purpose of the plugin is to add Quantcast Measure to your website? If so, you should be covered with the new Quantcast Choice plugin as that adds the new Quantcast Universal Tag which includes Choice and Measure.

    @rbaronqc Thank you for your reply!

    I remove the Quantcast Quantifier plugin and I install the new one as you said, Quantcast Choice…I inpud the Universal Tag ID (UTID or pCode), and now I didn’t have the popup acceptance window anymore.

    If I did that, I dont have to add the entire univrsal tag after </body> in header or footer? It supose to wirk just like that, with the Tag Id?

    Bacause mine didn’t!

    Thanks!

    Plugin Contributor Ryan

    (@rbaronqc)

    @vsharmilee I see the issue. You force traffic to non www (that is totally fine) but in the browser developer console when I do window.location.host the value returns with www. From the perspective of choice https://www.example.com is different than example.com, just like help.example.com is different. So in the dashboard you registered your site like ‘example.com’ and your website is requesting data for your site like ‘www.example.com’. See my answer here for the solution https://www.ads-software.com/support/topic/google-error-code-2-1a/#post-13263023

    Plugin Contributor Ryan

    (@rbaronqc)

    @vsharmilee also, it looks like maybe you are adding your UTID with the “p-” on the front of it? Can you make sure to follow this guide https://help.quantcast.com/hc/en-us/articles/360051794614-TCF-v2-GTM-Implementation-Guide-Finding-your-UTID to get the correct UTID value to enter in your WP admin.

    Yeah noted it, removed and the QC popup is showing now after adding https://www.Thank you!
    Can I set Consent scope to ‘Only users in the EEA or UK’? Will this solve the 2.1a error?

    Reg 1.1 we see google listed under IAB vendor page.However we are seeing the 1.1 error recurring.Kindly advise.

    Plugin Contributor Ryan

    (@rbaronqc)

    @vsharmilee, yes if you use this plugin (https://www.ads-software.com/plugins/quantcast-choice/) you will add both quantcast choice and quantcast measure to you website. You do not need to manually add the tag in any way, as long as the plugin installed/activated/configured and everything is configured correctly in your https://www.quantcast.com/protect/sites dashboard choice and measure should be added. You may still have to do some additional work make sure google tags are not added to your site before consent is established (that is the 2.1a error). This solution will vary depending upon your setup. If you are using a plugin to add google tags to you site please contact them and ask them how to configure their plugin to wait for TCF v2.0 signals before adding tags to your site.

    @vsharmilee I am now seeing the popup show on your site, nice work! However without making any consent choices (i.e. the popup is still open and I have not clicked on anything) I can see ads added in the background, which means whatever method you are using to add the tags to your site, it is not waiting for consent before dropping the tag on the page. You can see in this video here what should be happening https://vimeo.com/448116970/4d24c9edc9 where no ads are loaded until after the user makes their consent Choices on the first visit (no consent set prior)

    Plugin Contributor Ryan

    (@rbaronqc)

    1.1 Just means that a user said no to consent. I believe a user said no, but your site still dropped a google cookie and google is flagging it as an error because a tag that ads a cookie was dropped on the page when a user dined google consent (I believe this is the case)

    @rbaronqc Yes, my bad, the ”p” in the front of my ID was the problem, now it’s fine, the window popup it’s back but the adsense notify “We’ve detected an issue on your IAB TC string on one or more of your sites or apps.” it’s still there!

    And for the first part, in my wordpress settings, as well in my quantcast dashboard, I have https://www.criticmedia.ro link form added. It’s not suposed to be like that, or…?

    Thanks!

    Plugin Contributor Ryan

    (@rbaronqc)

    @vsharmilee your 2.1a problem will not be solved until your website stops dropping Google tags before consent is established. I’m not sure how you are adding Google tags to your site, but I would start by contacting the plugin author (of the plugin your using to add google tags) and ask them how to prevent their plugin (I’m assuming your using a plugin to add your google tags here) from adding tags to the site before consent is established for TCF v2.0 complaince.

    Plugin Contributor Ryan

    (@rbaronqc)

    @vsharmilee having the www is fine, but in some cases you are using the url like https://www.example.com and in some cases you use it like example.com (these are technically 2 separate url) We just have to make sure that whatever value window.location.host gives us is the same url that is registered here: https://www.quantcast.com/protect/sites. I believe you are all good from this perspective now. The last remaining issue (the hardest one) is making sure, however you are adding your tags, that they are not added until after consent is established.

    @spacetime Still ads are getting loaded before user consent so can you please address the issue?

    @rbaronqc Reg www mismatch I will check and fix it.But reg the loading of ads before user consent please let me know if configuring GTM would fix the issue.Will the ads still be there in ad iserter plugin even if I install GTM? Kindly help!

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