---
title: "IAB TCF explained: consent signals for advertising | Quantlix"
description: "The IAB Europe TCF standardizes how sites ask for and share privacy choices with ad tech vendors. Learn how it works, what v2.3 changed and how to build it in."
canonical: "https://quantlix.com/en/standards/iab-tcf/"
last-updated: 2026-11-16
---

Source: https://quantlix.com/en/standards/iab-tcf/
Language: en
Description: The IAB Europe TCF standardizes how sites ask for and share privacy choices with ad tech vendors. Learn how it works, what v2.3 changed and how to build it in.

**IAB TCF** [Privacy and consent](https://quantlix.com/en/standards/#privacy)

# IAB TCF: the Transparency and Consent Framework for advertising

IAB TCF is the IAB Europe framework that lets publishers, consent platforms and ad tech vendors record and share a user's privacy choices in one standard format across the advertising supply chain.

[Discuss your project](https://quantlix.com/en/contact/) [Read the key points](https://quantlix.com/en/standards/iab-tcf/#standard-overview)

## At a glance

**Full name**

IAB Europe Transparency and Consent Framework (TCF)

**Published by**

IAB Europe as managing organization; technical specifications stewarded by IAB Tech Lab

**Type**

Voluntary industry framework (policies and technical specifications)

**Current version**

TCF v2.3, released in 2025; required for all TC Strings created on or after 1 March 2026

**Applies to**

Publishers, advertisers, ad tech vendors and consent management platforms serving users in Europe

**Last reviewed**

November 16, 2026 (2026-11-16)

## In plain terms

### Key points

- The TCF gives the whole ad supply chain one standard way to disclose purposes and pass on a user's choices.
- A registered consent management platform records choices in a TC String that vendors read before processing data.
- TCF v2.3 made the disclosed vendors segment mandatory for TC Strings created from 1 March 2026.
- Only consent and legitimate interests are supported, and personalization purposes need consent.
- Using the TCF supports GDPR and ePrivacy compliance but does not replace each company's own obligations.

### What is IAB TCF?

The Transparency and Consent Framework (TCF) is **a shared industry standard for telling people which companies want to use their data for advertising and content, and for passing their choices along the supply chain**. IAB Europe released the first version in April 2018 and manages its policies, while IAB Tech Lab stewards the technical specifications.

It exists because a single web page can involve many ad tech companies. Instead of each one asking separately, the publisher’s consent management platform (CMP) asks once, in a standard format, and every participating vendor reads the same answer. The framework is voluntary and supports compliance with GDPR and the ePrivacy Directive rather than replacing them.

### What the TCF covers

- **Policies.** Binding rules for publishers, vendors and CMPs on how to disclose purposes, present choices and handle signals. IAB Europe vets registrations and can suspend participants for serious violations.
- **Purposes and features.** Eleven standardized purposes, such as storing information on a device or measuring advertising performance, plus special purposes and features, each with fixed wording shown to users.
- **Global Vendor List (GVL).** A public registry of participating vendors with the purposes they pursue, the legal basis they claim, their retention periods and how they access devices.
- **TC String.** A compact encoded value that records the user’s choices for each purpose and vendor and travels with ad requests.
- **CMP API.** A standard JavaScript interface, ` __tcfapi `, through which scripts on the page read the current choices.
- **Legal bases.** Only consent and legitimate interests are supported. Device storage (purpose 1) and the purposes that build or use profiles for personalized ads or content (purposes 3 to 6) need consent.

### Versions and key dates

TCF v2.0 arrived in August 2019, v2.1 followed in 2020 and v2.2 on 16 May 2023, when legitimate interests stopped being available for personalization purposes. The current version, **TCF v2.3**, was released in 2025 to settle how legitimate interests are signaled. It makes the disclosed vendors segment of the TC String mandatory, so vendors can tell whether the CMP actually showed them to the user.

The transition period ended on 28 February 2026. A TC String created from 1 March 2026 without that segment is invalid, while older strings remain valid until users renew or change their choices. Existing users did not need to be asked again purely for the upgrade.

### How it fits with GDPR and US privacy signals

The framework helps companies meet [GDPR](https://quantlix.com/en/standards/gdpr/) and ePrivacy rules; it is not a certification. In March 2024 the Court of Justice of the European Union held that a TC String can be personal data when it can be linked to an identifier such as an IP address, and that IAB Europe can be a joint controller for it. Each publisher and vendor still answers for its own lawful basis, notices and records.

For the United States, IAB Tech Lab’s Global Privacy Protocol (GPP) is a transport layer that carries state privacy signals, such as opt-outs under the [CCPA](https://quantlix.com/en/standards/ccpa/), and supports existing formats like the TCF alongside them.

### How it shows up in software projects

- **CMP setup.** A registered CMP is configured with the right vendors, publisher restrictions and wording, and loads before any tag that stores data or requests ads.
- **Tag gating.** Analytics, advertising and personalization scripts wait for the ` __tcfapi ` signal and run only for the purposes and vendors the user allowed.
- **Server-side checks.** Ad servers and data pipelines decode the TC String and apply it to each request, including the disclosed vendors segment.
- **Consent evidence.** The string, CMP identifier and vendor list version are stored with events, so a past choice can be shown when someone asks.
- **Ongoing upkeep.** Vendor lists and policies change, so CMP settings, vendor declarations and tests are reviewed on a schedule.

### How we work with IAB TCF

We integrate consent management into websites, apps and data platforms: configuring CMPs, gating tags, reading TC Strings on the server and connecting the signals to analytics and [digital marketing](https://quantlix.com/en/services/digital-marketing/) tools. Our [web application development](https://quantlix.com/en/services/web-application-development/) teams test that each choice changes what actually loads, in every browser you support.

Registration with IAB Europe and adherence to its Policies belong to the publisher, CMP or vendor, and legal compliance belongs to each controller. We build and test the technical side and document how signals flow. Learn more about our work in [marketing and advertising](https://quantlix.com/en/industries/marketing-and-advertising/).

## Where it applies

Industries where this standard often shapes the work.

- ### [Marketing & Advertising](https://quantlix.com/en/industries/marketing-and-advertising/)

  Campaign operations, audience insights and marketing analytics

## Related standards

[All standards](https://quantlix.com/en/standards/)

- GDPR

  ### [EU personal data protection law](https://quantlix.com/en/standards/gdpr/)

  GDPR is the European Union regulation that sets how organizations collect, use, share and protect personal data about people in the EU, giving individuals clear rights and every controller and processor clear duties.
- CCPA

  ### [California consumer privacy rights](https://quantlix.com/en/standards/ccpa/)

  CCPA is the California law, expanded by the CPRA, that gives residents rights to know, delete, correct and opt out of the sale or sharing of their personal information, and sets duties for the businesses that collect it.

## Services that support this work

The services we usually bring to projects that involve this standard.

[View all services](https://quantlix.com/en/services/)

### [Web application development](https://quantlix.com/en/services/web-application-development/)

Quantlix designs and builds web applications with responsive interfaces, business logic and system integrations, balancing accessibility, performance and maintainability.

### [Digital marketing](https://quantlix.com/en/services/digital-marketing/)

Quantlix develops search strategy, paid campaigns and content marketing with measurement tied to qualified enquiries, audience needs and business priorities.

### [Data analytics](https://quantlix.com/en/services/data-analytics/)

Quantlix builds analytics pipelines and business intelligence tools that turn operational data into defined metrics, useful reports and decision support.

## Questions, answered

What teams usually ask us about this standard.

**Is the IAB TCF mandatory?**

No law requires it. It is a voluntary industry framework, but many ad tech partners rely on TCF signals from European traffic, so in practice it is often a commercial requirement. To take part, a publisher uses a CMP registered with IAB Europe.

**What is the latest version of the TCF?**

TCF v2.3, released by IAB Europe in 2025. The transition period ended on 28 February 2026, and every TC String created on or after 1 March 2026 must include the disclosed vendors segment.

**Did users have to give consent again for TCF v2.3?**

Not just because of the upgrade. IAB Europe said strings created before the deadline stay valid until users renew or change their choices, and CMPs should not re-surface the consent interface solely for the framework update.

**Does using the TCF make us GDPR compliant?**

No. The TCF is an accountability tool that standardizes disclosures and signals. Each publisher and vendor remains responsible for its lawful basis, notices, records and security under GDPR and national ePrivacy rules.

**What is a TC String?**

A compact encoded value created by the consent management platform. It records which purposes and vendors the user allowed or objected to, which vendors were disclosed, and the vendor list and policy versions used, so every participant reads the same choice.

## Official sources

Read the official text before relying on any detail. What applies to you depends on your role, your location and the version in force.

- [IAB Europe: Transparency and Consent Framework](https://iabeurope.eu/transparency-consent-framework/)
- [IAB Europe: TCF Policies](https://iabeurope.eu/iab-europe-transparency-consent-framework-policies/)
- [IAB Europe: transition to TCF v2.3](https://iabeurope.eu/all-you-need-to-know-about-the-transition-to-tcf-v2-3/)
- [IAB Tech Lab: TCF technical specifications](https://github.com/InteractiveAdvertisingBureau/GDPR-Transparency-and-Consent-Framework)

These guides explain each standard in plain terms. They are not legal advice, and they do not state that any product or organization conforms to a standard.

## Planning software around this standard?

Tell us which systems are involved and what you need to show. We will help you build the requirements in from the start.

[Discuss your project](https://quantlix.com/en/contact/)
