CookieHub now fully supports IAB TCF v2.3

We are pleased to announce that CookieHub fully supports IAB Transparency and Consent Framework (TCF) version 2.3 as of CookieHub version 2.8.15.

TCF v2.3 introduces improvements aimed at resolving signalling ambiguities related to vendor disclosure and legitimate interest processing. With this release, CookieHub ensures continued alignment with the latest IAB Europe framework ahead of the planned deprecation of TCF v2.2.

The primary change in TCF v2.3 is the introduction of an explicit disclosed vendors signal in the TC string. This allows vendors to reliably determine whether they were disclosed to users in the CMP interface, independently of consent or legitimate interest signals.

This enhancement improves legal clarity in scenarios where vendors declare both legitimate interest purposes and special purposes, removing ambiguity that existed in earlier framework versions.

With CookieHub 2.8.15:

1. TC strings are generated in compliance with TCF v2.3
2. The disclosed vendors signal reflects the vendors configured and disclosed through CookieHub
3. No changes to the consent user interface are required
4. Existing TC strings created under TCF v2.2 remain valid until users update their consent choices

The update is fully backward compatible. Vendors that have not yet adopted TCF v2.3 will continue to operate as before.

To start using TCF v2.3, customers must update their domain configuration to the latest CookieHub version.

This can be done by:

1. Logging in to the CookieHub dashboard
2. Navigating to Domain overview
3. Clicking Update on the relevant domain

Once updated, the domain will begin generating TCF v2.3–compliant TC strings.

Updating to CookieHub 2.8.15 does not introduce any changes to consent banners or user flows. Users will not be prompted to re-consent solely due to this update.

CookieHub remains aligned with IAB Europe specifications and regulatory guidance, with a focus on predictable behavior and minimal disruption for publishers.