Ryan

@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://www.ads-software.com/support/topic/choice-ad-inserter-setup-support/
– https://www.ads-software.com/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://www.ads-software.com/support/topic/choice-google-tag-manager-gtm-setup-support/

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

@toengel thanks for reporting this issue. I don’t believe it is causing any functionality/performance issues but we are working to resolve.

@fredvi I looked at the url you sent. A couple of things. The part of the code from https://stackoverflow.com/questions/63440572/how-to-display-or-block-personalized-adsense-ads-based-on-consent-for-iab-tcf-v2 where google tags should be added to the page is all commented out on your website, so my code (which waits for consent is not adding Google tags). Your Google ad tags are being added else where on page. Can you move the adding of your google tags into the insertAdsByGoogleJs() function?

*Also, there was a small bug in the code posted previously (since fixed) where I used “tcdata.vendor.consents” and “tcdata.purpose.consents” where it should be “tcData.vendor.consents” and “tcData.purpose.consents”. (I missed the capital D in data).

In this code snippet here (from stack overflow, with the incorrect variable names updated):

if ( ! tcData.gdprApplies ) {
   // GDPR DOES NOT APPLY
   // Insert adsbygoogle.js onto the page.
   insertAdsByGoogleJs();
 }
 else {
   // GDPR DOES APPLY
   // Purpose 1 refers to the storage and/or access of information on a device.
   var hasDeviceStorageAndAccessConsent = tcData.purpose.consents[1] || false;
   // Google Requires Consent for Purpose 1
   if (hasDeviceStorageAndAccessConsent) {
     // GLOBAL VENDOR LIST - https://iabeurope.eu/vendor-list-tcf-v2-0/
     // CHECK FOR GOOGLE ADVERTISING PRODUCTS CONSENT. (IAB Vendor ID 755)
     var hasGoogleAdvertisingProductsConsent = tcData.vendor.consents[755] || false;
     // Check if the user gave Google Advertising Products consent (iab vendor 755)
     if(hasGoogleAdvertisingProductsConsent) {
       // Insert adsbygoogle.js onto the page.
       insertAdsByGoogleJs();
     }
   }
 }

You are adding Google ad tags to your website without checking for consent. I

@cvrle77 there are 2 separate things I’m looking into here. I don’t think that either one of them would be causing google errors (but I will be investigating).

The first one, vendors not getting turned back on after initially rejecting and then accepting consent from the main page. This would cause ads not to show (when you expect them to) as the purpose consents are getting enabled, but google vendor consent is not getting re-enabled, so plugin properly reading the consent string would read no google consent and not display ads (I have reported this to the product team).

The second issue 403 not found https://quantcast.mgr.consensu.org/choice/-xPe9kx2k7RVZ/brzikolaci.com/.well-known/noniab-vendorlist.json?timestamp=1598172183097. I am looking into this issue, but I don’t think this would be causing any of the issues discussed above but I will investigate and work on resolving the issue. Quantcast Choice allows for you to get consent for non-IAB vendors as well as IAB vendors. That file (not found) would contain non IAB vendor data if you had added any here https://www.quantcast.com/protect/vendors under the “non-IAB vendors” tab.

@cvrle77 Thank for pointing out the issue with rejecting and then accepting consent. I have raised the issue with the product team.

@cvrle77 a couple of things.

1. On first visit, after agreeing, I did not see ads, however on all page views after that I do see ads appearing.

2. It sounds like you might only want to show the CMP for users in the European Economic Area (EAA) and UK, you can do this by going to https://quantcast.com/protect/sites, clicking the pencil icon for your domain, and setting the CMP to show only for EAA and UK visitors.

If you do the above, Quantcast will set the tcData.gdprApplies to false for all those visiting outside the EAA & UK, and it is my understanding that if you install the latest development version of the Ad Inserter plugin and set Ad Inserter configuration up as mentioned here https://www.ads-software.com/support/topic/choice-ad-inserter-setup-support/#post-13294432 Ad Inserter will now read the `tcData.gdprApplies’ value and show ads as normal when GDPR does not apply.

@ibiza69 @vsharmilee Ad Inserter is currently working on an update to resolve these issues, see here: https://www.ads-software.com/support/topic/choice-ad-inserter-setup-support/#post-13294432

Awesome

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

@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).

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

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

@sneesel you are correct that when I click agree no ads appear, but I am seeing ads on all subsequent page views (so that is good). I believe there is either an Ad Inserter config setting that will load on the first close or that @spacetime is working on an update for that as we speak.

@43rumors Good point about annoying users that did give consent already. A Privacy button that allows users to change their consent choices should always be on the page. By default Choice will add that Privacy button for you in the lower right hand corner (only shows up if GDPR applies). You can also disable that via the display settings in your quantcast.com account and add your own privacy button to the page and use this js to show the UI __tcfapi(‘displayConsentUi’,2, function() {});

@spacetime maybe this can help https://stackoverflow.com/questions/63440572/how-to-display-or-block-personalized-adsense-ads-based-on-consent-for-iab-tcf-v2 It’s similar to the updates that I see in your plugin trunk.

@spacetime you should still be able to make __tcfaip calls such as:

__tcfapi('getTCData', 2, (tcData, success) => {
  if(success) {
    console.log(tcData);
  } else {
    // do something else
  }
});

Running the above in the dev console (visiting from US) prints out this data:

{
cmpId: 10
cmpStatus: "loaded"
cmpVersion: 10
eventStatus: "tcloaded"
gdprApplies: false
listenerId: undefined
tcfPolicyVersion: undefined
__proto__: t.Response
}

I believe you should be able to use the tcData.gdprApplies value in this case to determine if you can show ads.

@spacetime please feel free to reach out to me on the WordPress slack channel.

@vsharmilee I think that got rid of the TCFv1 CMP. I am no longer seeing it, now let’s activate the Quantcast Choice TCFv2 plugin/cmp.