Support » Plugin: Quantcast Choice » Google Error Code 2.1a

  • Plugin Author Ryan

    (@rbaronqc)


    This topic is intended to help anyone address Google 2.1a errors.

    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.

    I created a video here https://vimeo.com/448116970/4d24c9edc9 (apologies for the slow/jerky load in the video here, running over a VPN) which demonstrates expected behavior that shows ad tags that wait for consent to be established on page load before being added to the page. On subsequent page loads (user consent is saved) Choice popup will not show and ads will load using consent set in the previous Choice popup interaction.

    To test, in an incognito window, open your site to a page with ads. When you visit the page you should see Choice (i.e. consent has not been established as this is a first visit in incognito mode). At this point you should not see ads attempting in load in the background. You should not see any ads load/attempt to load. Once you agree and close the Choice popup all of you ads should begin to load without 2.1a issues.

    Solving 2.1a issues can be a rather difficult problem to solve due to the number of different ways tags can be added to websites. We are working to provide more detailed guides & examples to help you solve this error depending upon your setup.

    Quantcast Choice Plugin & Google Tag Manager:
    – 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 consent signals in GTM to create trigger events & trigger groups as shown here: https://help.quantcast.com/hc/en-us/articles/360051794434-TCF-v2-GTM-Implementation-Guide-IAB-Vendor-Tag-Blocking to prevent tags from firing until consent is established.

    • This topic was modified 1 year, 1 month ago by Ryan.
    • This topic was modified 1 year, 1 month ago by Ryan.
Viewing 15 replies - 61 through 75 (of 81 total)
  • Hello, do errors 2.1a and 1.1 have a chance to be fixed in a future Quantcast update? V11 ?

    Or do we have to wait for Adsense to change something in its operation?
    I did put my Quantcast code in the header before all the other javascripts but the errors are still there.

    Thank you.

    Ryan (@rbaronqc) I’m trying your example code on sierodelareina . com , but for some reason the process does not pass the condition of Purpose 1.

                        var hasDeviceStorageAndAccessConsent = tcdata.purpose.consents[1] || false;
                        // Google Requires Consent for Purpose 1
                        if (hasDeviceStorageAndAccessConsent) {	

    Any idea where the problem may be?.

    przyjem

    (@przyjem)

    Can you please post a step by step guide how to solve the Adsense ads not being displayed? I saw the code but I am not sure where to place it. It contains some place holders such as
    <head>
    <title>Your site title</title>
    </head>
    which I am not sure why they are there

    Plugin Author Ryan

    (@rbaronqc)

    @marlaskas I think I see my mistake “tcdata.purpose.consent[1]” should be “tcData.purpose.consent[1]”

    • This reply was modified 1 year ago by Ryan.
    Plugin Author Ryan

    (@rbaronqc)

    @here @nicmic Quantcast Choice itself does not block tags from being added to your page.

    This is over simplified, but, Choice will ask user for consent, save their consent choices, and make those consent choices available via __tcfapi() calls and the euconsent-v2 string. It is up to site owners (or advertising plugins) to use those consent signals in order to make decisions about adding google advertising tags. If you are using a pluign to add Google Advertising tags to your site you need to contact that plugin* and ask them how (with their plugin) you can prevent Google tags from being added to your site without proper consent using a TCF v2.0 compliant CMP.

    *If you are using the Advanced Ads or Ad Inserter plugin please wait for their forthcoming updates to resolve 2.1a and 1.1 errors, as they are actively working on updates and instruction guides.

    If you are using google tag manager to add google advertising tags to your site you can follow the guide. and GTM container import to read and act on consent signals.

    If you created a custom template and added tags directly in the code you would need to do something like the answer I posted here to manually check for consent (this will likely not apply to you).

    NicMic

    (@nicmic)

    Thank you for your response. The quantcast code is added in raw in the wordpress header (no plugin or tag manager). In the mentioned link, you should copy the javascript code before quantcast in the header to correct errors 2.1a and 1.1 ? Thank you. Have a nice day Ryan.
    ps : an integrated code is planned for Quantcast without us having to do anything in a future version?

    • This reply was modified 1 year ago by NicMic.
    marlaskas

    (@marlaskas)

    Ryan (@rbaronqc) Thanks for your response.

    Now if you click on ‘MORE OPTIONS’ button (without touching any option) and then click on ‘AGREE’ button, the ads remain blocked.

    For some reason the process does not pass the condition of Google Advertising Products consent.

                            if(hasGoogleAdvertisingProductsConsent) {							
                              // Insert adsbygoogle.js onto the page.
                              insertAdsByGoogleJs();

    Any idea where the problem may be?.

    • This reply was modified 1 year ago by marlaskas.
    przyjem

    (@przyjem)

    What could be the reason tor QWuantact not lading or loading randomly (sometimes it loads, sometimes it doesn’t) – console says:

    VM263 b1fe56d4aaaa64093b0df6115d8e1468.js:2 GET https://quantcast.mgr.consensu.org/choice/EZ-8ZzyQkTZMX/maddownload.comhttps://3qiupv3lwi8r34f1s23xzss8-wpengine.netdna-ssl.com/choice.js net::ERR_ABORTED 403
    (anonymous) @ VM263 b1fe56d4aaaa64093b0df6115d8e1468.js:2
    (anonymous) @ VM263 b1fe56d4aaaa64093b0df6115d8e1468.js:11

    Prasanta Ghosh

    (@gamersdunia16)

    @rbaronqc Hi there , i have been following this topic for 7 days now. Still did not get a proper solution. along with 2.1a error i also got 1.1 and 5.1 error . also saw google recently changed their solutions for these error on there troubleshooting page.

    so question is ,few of my niches website dont even use any consent how they din’t get any error from adsense for this.

    my site : gamersdunia.com

    I never used QuantCast plugin, should i Install it.

    shaki

    (@shaki)

    Hi all,

    Thanks in advanced for your input!

    We too are seeing some 403 errors in console (blank spaces instead of Adsense ads) and unfortunately we are stuck.

    Our site uses latest version of Quantcast Choice – TCF v2.0 with these settings:

    Universal Tag ID (UTID) — INSERTED
    Enable Choice TCF v2.0 — YES
    Push IAB & Non-IAB consent data to the Data Layer — YES
    Automatically add footer CCPA message — DISABLE

    We haven’t insert any code into header or whatsoever. Just using the plugin.

    What can we do to fix this?

    Plugin Author Ryan

    (@rbaronqc)

    @gamersdunia16 the solution to this problem is difficult as different websites add Google tags in different ways.

    Quantcast Choice only asks for, stores and makes accessible user consent choices (per TCF v2.0). Quantcast does NOT actively block tags from being added to the page. It is up website owners/plugin (that add google tags to your website) to wait for the user to give consent and read those signals to make decisions about tags that can and cannot be added to the page. If you are using either the Ad Inserter or Advanced Ads plugin the authors of those plugins are actively working on fixes to wait for consent and resolve 2.1a and 1.1 errors, and you should check out the specific threads dedicated to those plugins.
    https://wordpress.org/support/topic/choice-ad-inserter-setup-support/
    https://wordpress.org/support/topic/choice-advanced-ads-setup-support/

    If you are using a different plugin to add Google ad tags to you website you will need to contact that plugin and ask them how to configure the plugin to wait for proper TCF v2.0 signals/consent before adding tags to your website.

    If you add Google advertising tags to your website using Google tag manager there are additional instructions here on how to wait for proper consent before adding tags to your website: https://wordpress.org/support/topic/choice-google-tag-manager-gtm-setup-support/

    • This reply was modified 1 year ago by Ryan.
    aldon

    (@aldon)

    I have placed the adsense and Ad manager (DFP) codes directly on my site. How can i fix the problem?

    Although now with Quantcast choice version 11 it does not show the ads if I do not click I accept, in the code of the page i see that the ad has loaded. It just becomes “hide” until i press accept to Quantcast choice menu.

    marlaskas

    (@marlaskas)

    It seems that version 12 of Quantcast automatically blocks Adsense ads before choosing any option.

    Can anyone else confirm it?

    aldon

    (@aldon)

    @marlaskas just hide the adsense ads. The code it’s full loaded on source.

    marlaskas

    (@marlaskas)

    My last TCF 2.1a error log is dated on August 26 in the excel file generated by Adsense. Does the same thing happen to you?.

    • This reply was modified 1 year ago by marlaskas.
    • This reply was modified 1 year ago by marlaskas.
    • This reply was modified 1 year ago by marlaskas.
Viewing 15 replies - 61 through 75 (of 81 total)
  • The topic ‘Google Error Code 2.1a’ is closed to new replies.