IAB Transparency and Consent Framework (TCF) 2.2

The IAB Transparency and Consent Framework (TCF) 2.2 is a standard that enables publishers and advertisers to collect, manage, and share user consent signals for compliance with GDPR and the ePrivacy Directive in the EU and UK.

CookieHub is a registered CMP (Consent Management Platform) and supports TCF 2.2 out of the box.

What is TCF 2.2 for?

TCF 2.2 defines how websites:

• Collect and store user consent preferences
• Communicate those preferences to third-party vendors such as ad networks, analytics, and retargeting platforms

It ensures that:

• Vendors can only process data with a valid legal basis (e.g., consent)

  Users are clearly informed about:

  • Why their data is used (purposes)
  • Which vendors are involved
  • What data is collected
  • How long it is retained
• Consent choices are standardized and machine-readable

How it works

When TCF 2.2 is enabled in CookieHub:

• A standardized consent dialog appears, following IAB UI requirements

• The Global Vendor List (GVL) is retrieved, showing all TCF-registered vendors

  Users can accept or reject:

  • Purposes (e.g., personalized ads, content measurement)
  • Special features (e.g., precise geolocation)
  • Vendors that process their data
• A Transparency and Consent (TC) string is generated and stored
• The TC string is shared with vendors through the CMP API

The TC string includes:

• Consent or objection to each purpose
• The selected legal basis (consent or legitimate interest)
• User preferences per vendor

CookieHub implementation

CookieHub manages TCF 2.2 automatically. When you enable the framework:

• The TCF consent dialog is displayed with no extra configuration

  CookieHub:

  • Fetches the GVL
  • Displays purposes and vendors
  • Generates and updates the TC string in real time
  • Makes the TC string available via the IAB API
• If Google is in the vendor list, Google Consent Mode v2 and Additional Consent Mode are activated automatically

No manual setup is required.

When to use TCF 2.2

Use this framework if:

• You serve personalized ads in the EU or UK with platforms that require TCF (Google Ads, AdSense, Meta Ads)
• Your ad partners or header bidding providers need a valid TC string
• You require vendor-level consent management

If you do not work with vendors requiring TCF, use CookieHub Choices for a simpler category-based model.

How to enable TCF 2.2 in CookieHub

1. Go to Dashboard → Domain list
2. Select the domain

3. Click Settings

   Under Regional settings:

   • Set the framework to IAB TCF 2.2
   • Set consent type to Explicit (opt-in)
4. Save your changes

The TCF UI will appear automatically for users in the selected regions, and the TC string will be generated and shared.

Summary of features