TCF 2.4: Complete Web CMP Disclosures
TCF 2.4 for web CMPs
IAB Europe published TCF Specifications 2.4 and the corresponding Global Vendor List update on 23 July 2026. Web CMPs must implement the new disclosures by 23 October 2026.
TCF is a voluntary industry standard for communicating choices in the digital advertising chain; participation supports accountability but does not by itself establish legal compliance.
Required disclosures
Purposes and features: CMPs display GVL standard text, illustrations, and the current Special Feature 2 disclosure.
Legal bases and vendor counts: Consent and legitimate-interest objections remain separate, with vendor counts for each purpose and basis.
Operational disclosures: Vendor details include TCF and non-TCF storage, Special Purposes, operational domains, and mobile SDK package identifiers.
What changed operationally
Version 2.4 adds current standard text and illustrations for Features, updates the name and explanation of Special Feature 2, and strengthens the information available before a person decides. Disclosed-vendor requirements introduced with TCF 2.3 remain part of the implementation. App and CTV CMPs have a later 23 February 2027 deadline.
Publishers should test more than the banner: vendor lists, legal-basis controls, TC String generation, the TCF API, withdrawal, and downstream tag behavior must all reflect the same published configuration.
Integration with 1Consent
1Consent applies the TCF 2.4 model throughout authoring, frozen publication snapshots, CMP presentation, TC String persistence, the TCF API, and Google Consent Mode signalling. Customers still need to choose vendors and purposes accurately and validate their legal basis and data flows.
Building transparent consent infrastructure for the modern web.