Ryan

@webdados @ibiza69 @abragad @nicks89 @mattiave There is an updated version of the plugin (v2.0.6) that incorporates the latest Quantcast Choice Tag updates.

@designium @tristanleboss The Quantcast Choice Plugin has been updated and the latest (v2.0.6) version uses the updated Quantcast Choice tag.

@cvrle77 thank you. The product engineering team has been notified and is looking into the issue.

If a user has not given Consent for IAB Vendor 755 or has not given consent for Purpose 1 (Store and/or access information on a device) It is recommenced that no Google tags be added to the site until both of these consents have been granted. Doing so with out waiting for consent will result in 2.1a or 1.1 errors.

If you add a Google Advertising Tag to your website they will automatically check for consent by making a __tcfapi() call, but if it makes this call without Purpose 1 – Store and/or access information on a device consent being set, it has already violated consent (as the user has not given permission to access/read data from their device). As the name of purpose 1 implies it is the ability to read/access info from a device so you need to wait until this is true before adding Google Advertising Tags. The same is true for 1.1 errors. If a user has given Purpose 1 consent but not Google Advertising Products consent (vendor id 755) and a Google Advertising Tag is added to the page it will result in 1.1 errors and you the tag was added to the page even though the user did not give consent for Google Advertising Tags to be added to the page.

As long as both of the above consents have been given (Purpose 1 & IAB Vendor 755) then you are free to add Google Advertise Tags to the site, but NOT before this. From here (assuming both consents have been granted by the user), Google (now that they have consent to read the signals) will read consent signals directly from the TCF v2 consent string and make decisions about the types of ads to server such as personalized vs non-personalized ads. If the site adds a Google Advertise Tag to the page without Purpose 1 consent Google will still read/attempt to read the consent string and if they don’t find purpose 1 consent granted there there you will get a 2.1a error and if they don’t find consent for IAB Vendor 755 you will get a 1.1 error.

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

@ibiza69 On August 15th Google (Advertising Products) joined the IAB and got an IAB vendor ID (755), I believe Google Analytics & Google Optimize are NOT considered part of Google Advertising Products and you would have to create a NON-IAB vendor for these specific use cases. But for Google Advertising Tags like Adsense, the Google consent needed is for the IAB Vendor ID 755. This is where/what Google is checking for when looking at Google Vendor Consent. 1.1 errors result when a Google Advertising Tag has been added to the page where IAB Vendor ID 755 (google) Does NOT have consent.

@sirvss that depends upon when Google Advertising Tags are added to the page/attempt to read the consent signals. This is simplified, but Quantcast Choice will ask for, store, and make accessible user consent choices. It is up to the site owner (ad plugin) wait for, read and respect those consent choices. For example, if a user visits the website and a Google Advertising Tags are added in the background before the user selects their consent, that will result in a 2.1a error. When you add a Google Advertising Tag to your site, that tag/script will attempt to read the TCF v2 consent signals, if those signals are not yet set by the user and Google attempts to read them it will result in a 2.1a error. We put out some additional information here https://www.quantcast.com/blog/google-error-code-2-1a-protecting-your-ad-revenue/ to help with 2.1a errors

@sirvss I was previously seeing this error on the site:

Uncaught TypeError: n is not a function
    at e.apiCall (VM373 cmp2.js:2)
    at new e (VM373 cmp2.js:2)
    at Module.<anonymous> (VM373 cmp2.js:2)
    at n (VM373 cmp2.js:2)
    at Object.<anonymous> (VM373 cmp2.js:2)
    at n (VM373 cmp2.js:2)
    at VM373 cmp2.js:2
    at VM373 cmp2.js:2

But now, after your removal of the 2nd tag that js error is no longer present.

@sirvss, If you are using the QC Choice plugin (and added your UTID) the plugin will automatically add the Quantcast Universal Tag to the <head> of your website.

The plugin essentially does 3 things:
– Adds the Quantcast Universal Tag to the <head> of the site
– (optional) Automatically pushes consent signals to the data layer (when the option is enabled on the plugin admin page). This option is for users who need consent signals accessible for 3rd party tools like Google Tag Manager. This option can be enabled/disabled on the plugin admin page.
– (optional) Automatically adds CCPA Do not sell my data message and link to an empty container added to the footer of the website. This option can be enabled/disabled on the plugin admin page. In order for this feature to work you also have to have CCPA enabled on your tag from the quantcast.com portal.

@vsharmilee that is awesome news!

Closing the issue due to inactivity by the original author.

If you are having a similar issue please check the support forums for an existing answer before opening up a new support request.

Closing the issue due to inactivity by the original author.

If you are having a similar issue please check the support forums for an existing answer before opening up a new support request.

Closing the issue due to inactivity by the original author.

If you are having a similar issue please check the support forums for an existing answer before opening up a new support request.

Closing the issue due to inactivity by the original author.

If you are having a similar issue please check the support forums for an existing answer before opening up a new support request.

@satheeshrajv how are your google advertising tags being added to your site?

@cvrle77 @arthuroadam
You likely only to choose the “I don’t declare a legal basis for my property”

You only need declare a legal basis if you need consent for yourselves (Most users do not need this and can stick with the I don’t declare a legal basis for my property option. There is also an option for additional google consent, you may also might or might not need the Google additional vendors enabled as adSense is supported through the TCF. It might be that there are vendors that Google uses you need, so in that case enabling Google addtl vendors would be good to add. For the average user the default consent settings should work.

There is additional information here about consent in the Choice setup guide and the IAB has additional information on consents here which might be useful

Some common stacks if you do need to customize would be:
NUMBER 26
Name: Personalised ads and content, ad and content measurement, and audience insights
Description: Ads and content can be personalised based on a profile. More data can be added to better personalise ads and content. Ad and content performance can be measured. Insights about the audiences who saw the ads and content can be derived.
Purposes included
● Purpose 2: Select basic ads
● Purpose 3: Create a personalised ads profile
● Purpose 4: Select personalised ads
● Purpose 5: Create a personalised content profile
● Purpose 6: Select personalised content
● Purpose 7: Measure ad performance
● Purpose 8: Measure content performance
● Purpose 9: Apply market research to generate audience insights

or

NUMBER 42
Name: Personalised ads and content, ad and content measurement, audience insights and product development
Description: Ads and content can be personalised based on a profile. More data can be added to better personalise ads and content. Ad and content performance can be measured. Insights about audiences who saw the ads and content can be derived. Data can be used to build or improve user experience, systems and software.
Purposes included
● Purpose 2: Select basic ads
● Purpose 3: Create a personalised ads profile
● Purpose 4: Select personalised ads
● Purpose 5: Create a personalised content profile
● Purpose 6: Select personalised content
● Purpose 7: Measure ad performance
● Purpose 8: Measure content performance
● Purpose 9: Apply market research to generate audience insights
● Purpose 10: Develop and improve products

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