Google Error Code 2.1a
-
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.
-
@sanmag I have spotted the issue. You force all traffic to non-www, which is totally fine, however when I print out the browser
window.locationin the browser dev console I get the following information:
Location?{href: "https://www.micurodame.it/", ancestorOrigins: DOMStringList, origin: "https://www.micurodame.it", protocol: <strong>"https:", host: "www.micurodame.it"</strong>,?…}. which has a host value of https://www.micurodame.it with the www value. The quantcast choice tag is checking your host value and comparing that with the url you added via the Choice admin panel. The best solution, and the one that should be made is to update your server configuration so the that your host value (window.location.host) matches the url you force traffic to. Until you an make that server update a short term fix, that may work, would be to add 2 more websites to your https://www.quantcast.com/protect/sites account:
– https://www.torrinomedica.it (including the www)
– https://www.micurodame.it (including www)I don’t know for sure if this will work, there could be additional host/url mismatch problems that arise.
As you can see from the url here https://quantcast.mgr.consensu.org/choice/xTTqAJEm-VSq_/micurodame.it/choice.js your config lives under the non www because that is what you added to qc.com and and that is what you force web traffic to, but the value of
window.location.hostin the browser developer console includes the www. Choice reads the value ofwindow.location.hostto determine where to look for the config file.@vsharmilee @lenoop01 the 403 error on the non-iab vendor list is not causing the 2.1a error in any way. It just means you don’t have any custom non iab vendors added. Ill look into checking for that to exist before making the call to prevent the 403 error in this case.
The 2.1a error means you are loading Google tags onto your site before you have user consent. I don’t know how you are adding adsense 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 may need to contact the plugin (that is adding your google tag) 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 and read that data 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.
@vsharmilee yes if follow the GTM setup guide you can then create triggers events/groups (the last section of the guide) and use those to add your tags only after consent is established.
You may also want to try contacting the plugin author for your existing “ad inserter” plugin. They may have already made updates that just require additional configuration and ask if there are additional steps you need to take to wait for consent before the plugin drops tags or if they are currently working on a update to wait for tcf v2.0 consent signals before dropping tags. I have already been speaking with one plugin author today helping them to update to wait for consent before dropping tags, and we are happy to work with more plugins to help them make sure they wait for consent before adding tags.
- The topic ‘Google Error Code 2.1a’ is closed to new replies.
