What is this feature
Google released additional requirements for publishers and advertisers to work with their products. Here are more details: Google’s Additional Consent Mode (ACM) requirements
Why do you need it
If you work with Google and would like to continue using Google products after they move to TCF v2.0, you'll need to meet Google’s ACM requirements. Luckily, Quantcast Choice automatically builds this feature in as part of the platform to protect your business for you.
This release will allow you to support consent for Google’s additional vendors, and use Google Ads products, e.g. Google Tag Manager, Ad Exchange, Ad Manager, AdSense, AdMob, etc
How to turn this on
This feature became effective when Google fully transitioned its operations onto TCF v2.0 as of August 16, 2020. You can follow these steps to navigate turning this feature on in the Portal:
-
Go to Privacy, then select Properties
- For existing sites: click the pencil icon to edit the site you want to update.
For new sites: click Protect a Site.
- If you use your own Purposes, you need to check Your consent configuration to make sure you are collecting consent for the following purposes:
* Store and/or access information on a device
* Select basic ads
* Create a personalized ads profile
* Select personalized ads
* Measure ad performance
* Apply market research to generate audience insights
* Develop and improve products
Note: If you don’t use your own Purposes, you don’t need to do this.
- Select the checkbox option for Enable Google Vendors to turn it on.
How this feature will impact your user experience
When you turn on the feature your CMP will reprompt because this will update the CMP list by adding more vendors. (Note: every time you add vendors, the CMP will reprompt.)
What do I need to know as a developer
To be compliant with Google's specification, the TCF APIs that return a TCDdata object (getTCData and addEventListener) have been updated to now also return the addtlConsent string as part of the TCData object.
Learn more about Google’s key privacy requirements on TCF v2 here: Prepare for Google’s Additional Requirements on TCF v2.0 on TCF v2.0