Consent management for publishers
Google requires publishers using AdSense, Ad Manager or AdMob to use a Google-certified CMP integrated with the TCF when serving personalized ads to users in the EEA, the UK and Switzerland. CookieHub is a Gold Google Certified CMP, certified by IAB Europe as CMP 354, and was updated to TCF v2.4 ahead of the IAB's 23 October 2026 deadline.
Trusted and used by 30.000+ websites and companies worldwide.
What an ad-funded site needs from its CMP
Google's CMP requirement, met
CookieHub is a Gold Google Certified CMP. Google assesses certified CMPs mainly on TCF compliance, and requires one for personalized ads served through AdSense, Ad Manager and AdMob in the EEA, the UK and Switzerland. CookieHub also supports Google's Additional Consent specification, for ad technology providers that are not registered with the TCF.
IAB TCF 2.4, kept current
CookieHub implements IAB TCF 2.4 and Policies v5.0.b. Domains with automatic updates moved to v2.4 with nothing to configure, almost a month before the IAB's 23 October 2026 web deadline.
Consent signals you can defend
The TC string reflects the purposes and vendors your dialog disclosed and the choices your visitors made. Purposes you do not present are never signalled as consented, and the disclosed-vendors segment records which vendors were shown.
How publishers stay compliant as the TCF evolves
IAB Europe revises the framework regularly, and each version comes with a date by which CMPs must implement it. A publisher maintaining its own TCF integration has to track every release. With a managed CMP, the changes arrive in the widget.
Updates ship to the widget:
TCF v2.4 reached every automatically updating CookieHub domain ahead of the deadline, with no migration.
Your choices carry over:
Existing dialogs keep the same purposes and controls in the same order when new disclosures are added.
Stored consent is never rewritten:
Changing your purpose set does not alter consent already collected. Newly added purposes read as denied until the visitor is asked again.
Checked against the live vendor list:
Every change in the 2.4 release was verified by decoding real consent strings against the live Global Vendor List.
You decide what the dialog asks for
Choose which purposes, special features and stacks your dialog presents, individually or as IAB stacks, and manage your vendor list and legitimate-interest settings in the Dashboard's TCF settings.
Personalized ads and Consent Mode
Present purposes 3 and 4, or Stack 10, and the ad_personalization Consent Mode signal becomes grantable once visitors consent. How CookieHub derives each Consent Mode signal under the TCF is documented for widget version 2.9.1 and later.
Built for many sites and many markets
Every site in one dashboard
Manage all your properties from one account, with cross-domain consent and forwarding on the Business plan.
The right framework in each region
Geolocation shows each visitor the consent framework for their location: the TCF in Europe, and frameworks such as the IAB Global Privacy Platform (GPP) elsewhere.
Consent reports
Reports on consent responses and sessions, with advanced consent reports on the Enterprise plan.
Check your site's TCF setup
Our free compliance checker shows how your site interacts with vendors and consent signals under the IAB Transparency and Consent Framework, with a report on every active service, its declared purposes and its legal bases.
Which plan includes IAB TCF?
IAB TCF 2.4 is included in the Business plan, built for publishers and ad-driven sites with up to 1,000,000 sessions a month, and in Enterprise. Enterprise starts at 1,000,000 sessions a month and adds configuration via API, advanced consent reports, enterprise SSO and implementation services.
FAQ for publishers
If you serve personalized ads through AdSense, Ad Manager or AdMob to users in the EEA, the UK or Switzerland, yes. Google requires a Google-certified CMP integrated with the TCF for those ads. CookieHub is a Gold Google Certified CMP.
No. The TCF is an industry standard, not a law, and the GDPR does not require websites to use it. Advertising platforms do: Google requires it for the ads above, and header bidding providers and other advertising partners may require a valid TC string.
Yes. CookieHub supports Google's Additional Consent specification, which carries consent for ad technology providers on Google's list that are not registered with the TCF.
Use a CMP that ships them. CookieHub moved every automatically updating domain to TCF v2.4 before the IAB's 23 October 2026 web deadline. If automatic updates are disabled on your domain, update to the 2.4 release before then: CookieHub no longer supports TCF 2.3.
Yes. CookieHub derives the Consent Mode signals from your visitors' TCF choices, and the mapping for each signal is documented for widget version 2.9.1 and later.
Yes. Geolocation shows each visitor the framework for their region, and CookieHub supports the IAB Global Privacy Platform (GPP) for privacy signals beyond the TCF.
IAB TCF is included in the Business plan and in Enterprise. Sites with more than 1,000,000 sessions a month, or that need API configuration, SSO or implementation help, belong on Enterprise.
