# IAB TCF V2.3 Release details

## What’s Changing (and What You Need to Know)

The IAB Europe Transparency & Consent Framework (TCF) is evolving to version 2.3, bringing a set of refinements designed to improve transparency, consistency, and user experience.

This page provides a clear, user-friendly overview of what’s changing—and most importantly, what it means for you.

***

### Good News: No Action Required

**You don’t need to do anything.**

Our CMP fully handles the transition to TCF v2.3 on your behalf. All necessary updates will be automatically applied, ensuring that your implementation remains compliant without any manual intervention.

***

### What’s New in TCF v2.3?

TCF v2.3 is not a complete overhaul—it’s an incremental update focused on clarifications, standardization, and better alignment with regulatory expectations.

Here are the key changes:

#### 1. Improved Legal Basis Transparency

The framework introduces clearer distinctions around legal bases (such as consent and legitimate interest), helping ensure that users are better informed about how their data is processed.

**What this means:**\
Users will benefit from more explicit and consistent messaging, improving trust and transparency.

***

#### 2. Enhanced Vendor Disclosures

Vendors participating in the TCF are now required to provide more detailed and standardized information about their data processing activities.

**What this means:**\
Greater consistency across vendor information, making it easier for users to understand who is processing their data and why.

***

#### 3. Standardization of User Interface Elements

TCF v2.3 introduces stricter guidelines around how consent notices should be displayed, particularly regarding clarity and accessibility.

**What this means:**\
A more harmonized user experience across websites and apps using the framework.

***

#### 4. Technical Specification Updates

There are minor technical updates to the framework specifications to improve interoperability and ensure smoother communication between CMPs, vendors, and publishers.

**What this means:**\
Behind-the-scenes improvements with no impact on your setup.

***

### Summary

* TCF v2.3 introduces **incremental improvements**, not major changes
* Focus areas include **transparency, standardization, and clarity**
* **No action is required from you**
* Our CMP ensures **full compliance automatically**

***

{% hint style="info" %}
If you wish to go further, you can verify your TCF compliancy, IAB Europe has released a new CMP Validator Chrome Extension available [here](https://chrome.google.com/webstore/detail/cmp-validator/ffhhjklgcfabkpholngojpkijlafjooc) that includes all requirements of TCF v2.2 & 2.3.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://doc.commandersact.com/features/consent-management/knowledge-base/iab-tcf-v2.3-release-details.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.