What is Google Additional Consent?
Google’s Additional Consent is a technical specification designed to enable publishers to collect and signal additional consent for ad tech providers that are not part of the IAB Europe’s Transparency & Consent Framework (TCF) v2.2, but are listed on Google’s Ad Tech Providers (ATPs) list. This specification is crucial for publishers that want to work with ad tech providers not using the TCF. It is important to note that Google’s Additional Consent does not replace the standard IAB TCF v2.2 consent collection process, but supplements it, enabling an extra layer of consent collection for Google ATPs.
The Google Additional Consent V2 supports an Additional Consent (AC) String and to allow interoperability for CMPs that support TCF and Advertiser Consent Mode. For more information, please refer to this guide.
How to implement Google Additional Consent V2?
Google Additional Consent V2 is supported by the Apps SDK starting from version 2.11.0.
To successfully incorporate Google Additional Consent V2 into your mobile application, add the vendor called Google Ad Technology Providers to your CMP configuration:
In Usercentric’s Admin Interface, go to your configuration.
Under Service Settings, select the Google Vendors tab.
Use the toggle to enable the Google Ad Technology Providers (ATPs).
Select your providers in the list.
Your app is now using the Google Additional Consent Mode V2. To access the Additional Consent Mode Data generated by the SDK, use the getAdditionalConsentModeData endpoint.