Google Additional Consent
Domain access to property (property group) with feature access to vendor list management.
Google Additional Consent is a concept created by Google and the IAB Framework to pass end-user consent to Google Ad Technology Providers despite not adhering to the IAB TCF v2 Framework. In this article, we will cover the necessary information to understand, implement, and test Google Additional Consent on your property.


Information pertaining to Additional Consent can be found at the pages below provided by Google:
Publisher integration with the IAB TCF v2.0 - Google Ad Manager Help
Google’s Additional Consent Mode technical specification - Google Ad Manager Help

Key Concepts

If necessary, please familiarize yourself with the key concepts involved in utilizing Google's Additional Consent:

Google's Ad Technology Partners (ATP)

Google's Ad Technology Partners (ATP) are vendors that Google may share data with and who may or may not belong to the IAB TCF v2. Please refer to the table below to see how end-user consent preferences are delivered based on IAB TCF v2 participation:
Google ATP Vendor Status
Consent Delivery Method
Participating in IAB TCF v2
Not Participating in IAB TCF v2

TCData and TCInAppData

The TCData and TCInAppData objects are used to communicate end-user consent to vendors who participate with the IAB TCF v2. TCData is used for web, and TCInAppData is used for mobile environments.
The Additional Consent string will be added to the TCData and TCInAppData objects to communicate end-user consent for vendors who do not participate with the IAB TCF v2.
The Additional Consent String is the mechanism used to pass end-user consent information for Google ATP vendors who do not participate with the IAB TCF v2. This string will be created and added automatically to the TCData and TCInAppData objects respectively.

Add Google ATP Vendors to Vendor List

Ensure that the IAB vendor, Google Advertising Products is added and configured for the GDPR TCF v2 Vendor List before the addition to any Google ATP vendors. The purposes and legal bases used for this vendor will be used to configure your ATP vendors .
Click here for more detailed instructions to add a vendor to your Vendor List.
Google ATP vendors can be added to a GDPR TCF v2 Vendor List by navigating to GDPR > TCF v2 > Vendor List > Add Vendor > Custom ATP Vendors.
Use the above workflow to add Google ATP Vendors to the GDPR TCF v2 Vendor List.
Click Add Vendors when finished.
Confirm the purposes and legal bases for all Google ATP vendors added to the Vendor List and click Save to confirm changes.

Verify Additional Consent String

To view the Additional Consent string, navigate to a property with a successfully implemented and active messaging campaign, and provide consent through your consent experience.
Access the developer console and execute the following command:
__tcfapi('getTCData', 2, function (tcData, success) {console.log("GETTCDATA: ", tcData);});
The return object will contain addtlConsent followed by the Additional Consent String.
Use Google's Additional Consent Technical Specification to decode the returned string.
Last modified 8mo ago