Google Additional Consent Mode v2

Google Additional Consent Mode v2 is a technical specification designed to work alongside the IAB Europe’s Transparency & Consent Framework (TCF) v2.2. It enables publishers and Consent Management Platforms (CMPs) to send transparency and consent signals to Google Ad Tech Providers (ATPs) that are not registered on the IAB Europe Global Vendor List (GVL).

Purpose

The primary goal of Additional Consent Mode v2 is to:

Extend consent signaling to include Google ATPs not listed in the IAB GVL.
Ensure compliance with Google’s EU User Consent Policy by providing transparency and obtaining consent for these additional vendors.

How It Works

When implemented:

Transparency & Consent (TC) String: Generated per TCF v2.2 specifications, covering vendors listed in the IAB GVL.
Additional Consent (AC) String: A supplementary string that lists consented and disclosed Google ATPs not present in the IAB GVL.

These strings are then:

Stored by the CMP.
Passed through the digital advertising chain to inform vendors of the user’s consent choices.

AC String Format

The AC string comprises:

Version Number: Indicates the specification version (e.g., 2).
Consented ATP IDs: Dot-separated list of user-consented Google ATP IDs.
Disclosed ATP IDs: Prefixed with dv., a dot-separated list of disclosed (but not consented) Google ATP IDs.

Example: 2~1.35.41.101~dv.9.21.81

This string signifies:

User has consented to ATPs with IDs 1, 35, 41, and 101.
ATPs with IDs 9, 21, and 81 have been disclosed to the user.

Implementation in CookieHub

CookieHub, as a registered CMP supporting TCF v2.2, automatically:

Generates the AC string when the IAB TCF 2.2 framework is enabled.
Includes consented and disclosed Google ATPs based on user interactions.
Ensures that both TC and AC strings are available to vendors for compliance purposes.

No additional configuration is required beyond enabling the IAB TCF 2.2 framework in your CookieHub settings.

Implement Additional Consent Mode v2 if:

You’re using Google advertising services that include ATPs not listed in the IAB GVL.
You aim to provide transparency and obtain consent for all vendors involved in ad delivery and measurement.
You’re operating in regions where compliance with the EU User Consent Policy is mandatory.

Summary

Feature	Supported in CookieHub
TCF v2.2 Compliance	✅ Yes
Automatic AC String Generation	✅ Yes
Integration with Google ATPs	✅ Yes
No Additional Configuration Required	✅ Yes