Google Additional Consent Mode v2

Google Additional Consent Mode (AC Mode) works alongside the IAB Europe Transparency & Consent Framework (TCF) v2.2. It allows consent signals to be sent to Google Ad Tech Providers (ATPs) that are not listed in the IAB Global Vendor List (GVL).

Why it matters

Starting January 16, 2024, Google requires all publishers using AdSense, Ad Manager, or AdMob to:

• Use a Google-certified Consent Management Platform (CMP)
• Implement IAB TCF when serving ads to users in the EEA or UK

Google-certified CMPs are evaluated against strict compliance requirements, primarily focusing on full TCF integration.

CookieHub is a Google-certified CMP, ensuring you meet these requirements without additional setup.

When publishers use TCF but also work with Google ad tech partners outside the IAB GVL, Google supports these vendors through the Additional Consent specification. This ensures consent signals are extended to all relevant partners.

How Additional Consent Mode works

When enabled:

• A TC string is generated per TCF v2.2 for IAB GVL vendors
• An Additional Consent (AC) string is created for non-GVL Google ATPs

The AC string includes:

• Version number
• Consented ATP IDs
• Disclosed ATP IDs

Example:

This means:

• Consent granted for ATP IDs: 1, 35, 41, 101
• Vendors 9, 21, 81 were disclosed but not consented

CookieHub implementation

When you enable the IAB TCF 2.2 framework in CookieHub:

• Both TC and AC strings are generated automatically
• Signals are sent to Google and other relevant vendors
• No extra configuration is required

When to use Additional Consent Mode

Enable AC Mode if:

• You use Google ad services with ATPs not in the IAB GVL
• You must comply with Google’s EU User Consent Policy
• You serve ads in the EEA or UK and need full transparency

Summary of features