Ryan

@webzunft lets connect on wordpress.slack. I messaged you there.

@sanmag Yes, we support multiple languages, I believe we all of the default privacy messaging translated to 17 different languages. I thought the default behavior is to autodetect the visitors browser language, but maybe you have to select that. Can you create a custom theme here https://www.quantcast.com/protect/themes and under in the Customize UI section make sure the CMP UI LANGUAGE field is set to “Autodetect language”. One your new theme is created head over to https://www.quantcast.com/protect/sites, select the edit “pencil icon” for your site and apply your new theme.

Hi @webzunft, thanks for letting me know about the admin link issue, I will try to push out a fix for that that week.

Yes, for the domains that you add here https://www.quantcast.com/protect/sites you would NOT include the subfolder, it would either be ‘example.com’ or ‘www.example.com’ depending upon how you have your server configured. Choice looks at your window.location.host (more on window.location) value, so whatever your window.location value is, your registered site on Choice should match.

@ibiza69 if you are getting 2.1a errors it is likely your site is adding google tags to to the website before getting consent from a user. The solution will really depend on how you are adding google tags to your website. If you are adding google adsense to your website via google analytics which is added to your website with a wordrpess plugin you are likely adding analytics without waiting for consent. There are all kinds of different ways and different plugins you could be adding tags with. It is hard for me to know and answer because I do not know your website setup and how you are adding tags. Can you tell me how you are currently adding your tags and how you are blocking tags until consent is established? In my comments I suggest the easiest way to do this is with Google Tag Manager. Have you considered trying that method, or is it not possible to add with google tag manager? I also put out addition information specifically about 2.1a here https://www.ads-software.com/support/topic/google-error-code-2-1a/ which is also in some of the comments above.

@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.location in 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.host in the browser developer console includes the www. Choice reads the value of window.location.host to determine where to look for the config file.

• This reply was modified 4 years, 3 months ago by Ryan.
• This reply was modified 4 years, 3 months ago by Ryan.
• This reply was modified 4 years, 3 months ago by Ryan.

@redsoccerinfo the first part of this guide shows an example of importing a container (not the same container). There is also a video of the process embedded there. You can also find lots of info out there on importing containers by just searching. https://support.google.com/tagmanager/answer/6106997?hl=en

@redsoccerinfo I cant say for sure (this is in no way legal consent advice) what consents you need to set. But I would leave the Google Vendors on (You are right that is a new featured added to help make sure Quantcast Choice and site owners collect all of the consent necessary for Google ad vendors). And unless you have a specific reason to select custom consents I would leave it as the default value (but you may need to discuss with your legal department as to what consents you need).

@redsoccerinfo You can create your GTM account by going here https://tagmanager.google.com/. There are lots of different ways to add Google Tag Manager to your website, but in this case I would just finding WordPress plugin to do so. Once GTM is added to your site I would suggest following Google’s guide for adding GA via GTM https://support.google.com/tagmanager/answer/6107124?hl=en. You would then need to replace the page view trigger (from the video) to use a custom Trigger group that waits for page view and google consent. See the QC – Trigger_SAMPLE – All Pages trigger example here https://help.quantcast.com/hc/en-us/articles/360051794434-TCF-v2-GTM-Implementation-Guide-IAB-Vendor-Tag-Blocking (the last one). You will need to replace the regular “all pages” trigger as seen in the google with this new custom trigger group. You can download and import this ready made GTM container with the needed variables and example triggers (one of the examples is google triggers). See this comment for more details.

@redsoccerinfo based on the answers above I’m pretty sure the issue lies with Googlytics – Simple Google Analytics adding the GA tag without waiting for consent to be established. (I’m not saying they are doing anything wrong, its just that when Google started listening for consent things changed and now site owners need to be more conscious about how tags are added to website, and prevent them from being added until consent can be established). You may have to consider a different solution like adding Google Analytics (and in turn Adsense) to your website using Google Tag Manager and waiting for consent signals before adding the GA tag to the page. Otherwise maybe Googlytics will update with a way to wait for consent signals before dropping the GA tag on the page.

Sounds great, thanks for getting back to us. If your still seeing issues we love to know so we can improve the product.

@evrendede “Ask your CMP to make sure that their APIs are properly implemented based on the IAB TCF tech spec.” is listed in the help document here for 2.1a. (Also 2.1b, but I have not seen any reports of 2.1b, so ill assume you mean 2.1a) We believe the issue stems from Google tags being added to the website before consent has been established. See the sticky post here for more information.

As mentioned above the solution for 2.1a can be difficult to solve because different sites add tags in different ways using plugins, GTM, directly in code, etc so the solution described in the document as:
Per the ePrivacy Directive and EU Google Policy, a consumer must establish a valid legal base through Quantcast Choice before Google tags can be set.
To Address
1. The site owner must prevent all tags from firing until a response is obtained from Quantcast Choice.
2. Then, the site owner should only fire the tags for which the consumer provided permission.

is very broad could vary for users depending upon their setup.

Quantcast has cataloged the error codes, reasons they arise with Choice and ways to address them here: https://help.quantcast.com/hc/en-us/articles/360052292554-Google-IAB-TCF-v2-Error-Codes-Guidance

@redsoccerinfo I created a sticky topic here https://www.ads-software.com/support/topic/google-error-code-2-1a/ to try to get the different error codes in a single channel. I posted some initial information and one possible way to test if this error is being caused by Google Advertise Tags loading before consent is captured. However, the solution can become difficult there are different ways in which people add tags to their site. We have the most documentation around using GTM to block/allow tags in the help center there are lots of different ways in which tags can be added it it can be difficult to prevent tags from firing until after the CMP returns consent as the one of primary objectives of almost every tag is to fire as early as possible. Can you give me any more information about how google tags get added to your site? Using GTM? Directly in code? Using a plugin?

@goddamnnoise if your using GTM I made a GTM container with the 4 necessary variables and 8 example triggers that you can download here and import into your GTM. The container has a Non IAB example and IAB (Google Advertising Products) example with the following trigger types:
– A trigger, by vendor name, which fires a tag as soon as the consent window closes, and the user has granted the tag consent to fire.
– A trigger, by vendor id, which fires a tag as soon as the consent window closes, and the user has granted the tag consent to fire.
– A trigger which blocks a tag from firing if consent has not been granted to the tag.
– A trigger group which fires the tag after consent has been granted to the tag and some other trigger has fired as well (e.g. a DOM Ready trigger). This is useful for deferring tags that fire during page load to wait for consent to be granted before allowing them to fire.

You can read more about the different trigger types in the guide here

Here is an example video of importing a similar container https://vimeo.com/444324744/e4c3d8f2b3 (it is recommended that you create a New Workspace).

In the help center guide here starting at Triggers Non-IAB Vendor Tag Blocking and Firing (Such as Hotjar, Facebook, Twitter, LinkedIn, etc) you can see the steps for creating a Non-IAB vendor tag that may be helpful as well as the only difference for these purposes is the GTM variable/string (iab vs non iab) that is used by the different triggers.

Hopefully this Google tag manager container import and above trigger info/guides can help you get your tags/triggers set in GTM.

@arthuroadam can you start a separate topic