Ryan

@ibiza69 @goddamnnoise specifically on the 2.1a error code we believe it is likely caused when Google loads before the CMP responds. I am not sure how you are adding Google tags to your site, but if you are not blocking Google tags until after Choice Responds that is likely causing the issue here. If you are using GTM to add your Google tags you can check the option in the WP admin page for the Choice plugin to push consent signals to the data layer. If you use that feature along with GTM you can setup a trigger group to load your Google Tags once the page loads and Choice loads.

@here the team here an Quantcast has put together guidance to show the reasoning and steps to address the various error codes. That information been posted in on the Quantcast Help Center here https://help.quantcast.com/hc/en-us/articles/360052292554 Please take a look at the reasoning and guidance the the error codes. We also have some additional google Choice Google specific documents in the help center here https://help.quantcast.com/hc/en-us/sections/360009359354-Integration-with-Google-on-TCF-v2.

I am working on a sticky post to add to the support here that covers some of the more frequent error code cases.

@cnmmzone did the above solve your issue?

@goddamnnoise I believe the 1.1 errors codes are seeing are just users who did not give Google consent. The description states “Google, as a vendor, is not allowed under consent or legitimate interest.” Which can simply mean the user rejected consent for google. Unless you are seeing the 1.1 error on an unusually large portion of traffic it is very likely just users not giving google consent.

We are actively looking at the 2.1a error.

@here We appreciate everyones patience as we continue to investigate the reported issues, and we will update the support channel here with any progress.

Today is the first day that Google is listening and using to TCF v2 signals, we trying to determine what is expected behavior based on configuration vs issues that need to be resolved.

There are certain configuration options that could cause Google to not work. For anyone seeing issues related to Google can you please check the article here: https://www.quantcast.com/blog/quantcast-supports-google-tcf-v2-integration/ which addresses Google consent requirements.

For instance:

• <div>Active Fingerprinting is Not Allowed</div>
  <div>Google will not work with vendors who register for Special Feature 2 and have an opt-in for it. Special Feature 2 refers to actively scanning device characteristics for identification.</div>

So if you have the “Special Feature 2 refers to actively scanning device characteristics for identification.” feature enabled, in the CMP it does not comply with Google’s privacy requirements.

We added some additional Google consent options to the CMP that you can read about here: https://help.quantcast.com/hc/en-us/articles/360053007813-TCFv2-Google-s-Additional-Consent-Mode-ACM-Implementation-Guide-

@goddamnnoise could you go into your quantacast.com account and click to edit your website. In the general settings you can choose which version of the CMP you would like to use, it defaults to the latest version (v9), can you switch it to v8 and see if you are seeing the same errors on your end?

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

@here still working with the Choice product engineering team to solve this issue.

@sanmag can you see if you are still getting a 403 error found for the resource url you listed above? I was able to view/access that resource. Are you still seeing the issue mentioned above? Also, do you know if you are using Global scope for your CMP settings?

https://www.quantcast.com/blog/quantcast-supports-google-tcf-v2-integration/
“Global Scope and Out of Band Vendors Are Not Allowed Google policies require that publishers use either (a) service-specific scope or (b) group-specific scope. Google does not support Global scope or Out-of-band.”

Hi @sarangsss29 the best way to test would be to use a VPN to visit your website as a user from a GDPR country. There are various free VPN’s that you could download and use to test https://chrome.google.com/webstore/search/vpn?hl=en-US&_category=extensions

Another way to test the user experience for EU traffic would be to test set GDPR to apply to “everyone” and then test the popup functionality. Once you are satisfied you can set the CMP to display to UK + EAA traffic only. But in this case I would still suggest that once you switch over to UK + EAA only you still would want to verify that that popup is working for UK + EAA traffic.

@here Actively working with the product engineering team to solve this issue. I will update the ticket here once I have any new information.

Hi @ibiza69, thank you for reporting this issue, we are looking into it now.

@cnmmzone do you wish to add CCPA functionality to the website or just GDPR? I think there may be a miss match between the CCPA options selected in your quantcast.com account where you added the website and the CCPA select option in the WordPress admin for the plugin.

If you want to use the CCPA functionality can you make sure it is enabled for your website in your quantcast.com account https://www.quantcast.com/protect/sites along with selecting the Automatically add CCPA to footer on the TCF 2.0 Settings Tab in the WordPress admin.

If you do not wish to use CCPA can you make sure it is disabled for your website in your quantcast.com account https://www.quantcast.com/protect/sites and then select “Disable” for the Automatically add footer CCPA message
field on the TCF 2.0 Settings Tab in the WordPress admin.

If that does not solve the issue I can investigate further.

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

For the TCF v2.0 plugin update, all plugin features display features have been moved inside of the quantcast.com dashboard for easier management. Our help center has a list of setup and feature options: https://help.quantcast.com/hc/en-us/sections/360006841354-Setup

Hi @lauren14,
This issue arrises when your site is using https:// and not https://. When I visit https://associations.ouistreham-rivabella.fr/, save my consent, and refresh the page; the CMP performs as expected, remaining minimized (assuming the next page visit is also https). Can you confirm?

I think the best solution in this case is to force all of your traffic to https, so any attempted visit to https://associations.ouistreham-rivabella.fr/ will be automatically redirected to https://associations.ouistreham-rivabella.fr/.

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

@cnxsoft The TCF v2.0 plugin update now offers CCPA support.
You will need to create a quantcast.com account and get a Universal Tag ID to updated to TCF v2.0. I created a short video to show the account creation and update process.

Enable CCPA
1. From the quantcast.com dashboard you can enable and customize for CCPA. See the help center article here. This will enable CCPA and customize the popup/functionality but the footer message still needs to be added to WordPress.

2. Once CCPA has been enabled on quantcast.com (step 1) head over to your WordPress admin dashboard page for Quantcast Choice (url: https://www.YOURWEBSTIE.com/wp-admin/admin.php?page=qc-choice-options&tab=tcfv2_screen) and set the field Automatically add footer CCPA message to Automatically add CCPA to footer. This will automatically add some empty html to the footer of your website (using the ‘wp_footer’ hook):
<div class="container container-choice-footer-msg"><div class="container-inside"><div id="choice-footer-msg" class="choice-footer-msg"></div></div></div> where the CCPA message and Do Not Sell My Data link will be added.