Chapter navigation
TCF version deltas
consentRole & classification
Transparency & Consent Framework (TCF) version evolution: v1 (deprecated) → v2.0 → v2.1 → v2.2 → v2.3 deltas; v2.4 has no released version and must not be cited as one. The mapping between the TcfPolicyVersion field and Global Vendor List (GVL) versions.
- GPP section
- §2 (TCF EU)
- Status
- Final v2.2 + 2.3
Version timeline
| Version | Released / mandatory | Key changes |
|---|---|---|
| v1deprecated | — | The first TCF; the encoding format and API were fully reworked in v2.0, now encountered only in legacy integrations. |
| v2.0 | 2019-08-21 | Reworked the framework: introduced Publisher Restrictions, strengthened user control over purposes and vendors, added Special Features opt-in. |
| v2.1 | 2022-02 / 2022-06 | GVL format maintenance: Feb 2022 moved the Planet49 ruling vendor fields (deviceStorageDisclosureUrl etc.) from a separate tech spec into this core spec; Jun 2022 updated the filename in the GVL JSON example's deviceStorageDisclosureUrl. No policy version change (TcfPolicyVersion remained 3). |
| v2.2 | 2023-05-16 · mandatory 2023-09-30 | Addressing the Belgian DPA's concerns: removed Legitimate Interest as a legal basis for ad/content personalisation (Purposes 3–6), leaving consent only; TcfPolicyVersion raised to 4; user-friendly descriptions replace legal text; the Consent Management Platform (CMP) discloses vendor counts on the first layer; easier consent withdrawal. |
| v2.3 | 2025-04 | The DisclosedVendors segment becomes mandatory, resolving disclosure ambiguity for Legitimate Interest under Special Purposes (Google's enforcement deadline 2026-02-28). |
| v2.4no released version | — | No released version; do not hard-code a release date or contents when citing. |
Version deltas
The TcfPolicyVersion field in the Core segment marks the TCF policy version of the GVL: 4 since v2.2; strings with a policy version below 4 are invalid since 2023-09-30.