Loading
Home / IAB TCF

IAB TCF Compliance

The IAB Transparency & Consent Framework (TCF) was developed by IAB Europe to standardize how user preferences and data processing information are managed across the digital advertising ecosystem. Easily implement TCF v2.4 with Okito and configure your consent management in line with the latest standards.

Get Started TCF v2.4
Powering we provide the latest solutions for website privacy compliance
garcia.png
suaryapi.png
blackstate.png
gulbenergen.png
reportage.png
tecnhifue.png
sulax.png (1)
barbertrade.png
naksanyapi.png
byonhotels.png
atlastek.png
nexonya.png
uiduk.png
endemik.png
sms.png
envatarim.png
scotty.png
baru.png
pehlivan.png
mintek.png
ader.png

Create Your Okito Account

Add your website, choose the plan that fits your needs, and begin configuring TCF v2.4 from the Okito dashboard.

Create Your Okito Account

Copy Your Banner Code

Configure your banner design, data processing purposes, and vendors. Then copy the code generated specifically for your website.

Copy Your Banner Code

Add the Code to Your Website

Place the code in your website’s <head> section or deploy it through Google Tag Manager. Publish your banner and start managing user preferences according to the TCF standard.

Add the Code to Your Website

Configure Your TCF v2.4 Consent Experience

A TCF interface should present the right information in a clear and easy-to-follow order. Okito helps you configure this experience in line with the latest technical and interface requirements of TCF v2.4.

  • Enable TCF v2.4 settings through a guided setup.

  • Configure data processing purposes, features, and disclosures related to Special Feature 2.

  • Customize the layout, colors, and CSS to match your brand while preserving the required TCF information.

Give Users Clear and Flexible Choices

Visitors should be able to understand which purposes and vendors may process their data before making a choice. They should also be able to update their preferences or withdraw consent after their initial selection.

  • Present accept, reject, and granular preference options in a clear and balanced way.

  • Keep the preference center or banner recall button easily accessible.

  • Display the appropriate consent experience based on the user’s location.

  • Clearly explain the scope of preferences in supported multi-device environments.

Manage Vendors and Communicate Consent Signals

User choices should not remain limited to the banner; they must be communicated to the relevant vendors through a standardized mechanism. Okito helps present vendor information clearly and transmit consent signals consistently across the digital advertising ecosystem.

  • Manage vendors from the IAB Global Vendor List and eligible Google Ad Tech Providers.

  • Display each vendor’s data processing purposes and relevant disclosures.

  • Let users make granular choices by vendor and purpose.

  • Transmit preferences through the standardized TC String and configure Google Additional Consent support where required.

What is IAB Europe?

IAB Europe is the European-level industry association for the digital marketing and advertising ecosystem. Through its network of national IABs and media, technology, and marketing companies, it represents more than 5,500 organizations and develops shared standards and technical frameworks.

The Transparency & Consent Framework (TCF), managed by IAB Europe, creates a common language for communicating user preferences among publishers, CMPs, and ad tech providers. Consent, objection, and vendor disclosure signals collected through a CMP or cookie banner are encoded in a standardized TC String.

IAB TCF does not replace the GDPR or the ePrivacy Directive. Every organization using the framework remains responsible for ensuring that its own data processing activities comply with applicable law.

What Is IAB TCF v2.4?

IAB TCF v2.4 is the current technical standard that defines how consent, objections, data processing purposes, and vendor disclosure signals are communicated through the TC String across the digital advertising ecosystem.

The first version of TCF launched on April 25, 2018. TCF v2.3, released on June 19, 2025, made the Disclosed Vendors segment mandatory to include vendor disclosure information in the TC String. TCF v2.4 specifications and the revised Global Vendor List followed on July 23, 2026.

The main changes introduced with TCF v2.4 include:

  • In supported implementations, user preferences can be managed across different access points to the same service, such as its website and mobile app.

  • The cookie banner must clearly state whether a choice has service-specific, group-specific, or multi-device scope.

  • Features must be presented with standardized explanations and illustrations, while Features that users cannot disable must not appear alongside misleading controls.

  • Special Feature 2 has been renamed “Identify devices based on information actively requested” and requires a separate user opt-in.

CMPs participating in IAB TCF must implement the new disclosures in web environments by October 23, 2026, and in mobile app and CTV environments by February 23, 2027.

Why Does IAB TCF v2.4 Matter for Publishers and CMPs?

Clear User Choices in the Cookie Banner

TCF v2.4 helps users make informed decisions by allowing them to review data processing purposes and relevant vendors through the cookie banner.

Users can give consent, set detailed preferences, object to processing based on legitimate interest, or withdraw consent they previously provided.

The banner clearly indicates whether a choice applies only to the current service or across supported devices and environments belonging to the same service. Users can also access the preference center to update their choices at any time.

CMP and TC String Management with TCF v2.4

A CMP that supports TCF v2.4 processes the disclosures in the updated Global Vendor List and encodes user preferences in a TC String that follows the latest technical specification.

The interface clearly distinguishes between Purposes and Special Features that users can control and Features that are displayed for information only.

The accuracy of the signals contained in the TC String depends on whether the CMP configuration matches the website’s actual cookies, vendors, and data processing activities.

Consistent Consent Signals for Advertising Platforms

Ad tech providers receive user choice, purpose, and vendor signals through the TC String. Under TCF, consent is required to create profiles for personalised advertising and select ads based on those profiles.

Without the required consent, these activities cannot be signalled as permitted, and platforms may serve limited or non-personalised ads according to their own rules.

An up-to-date TCF v2.4 setup helps reduce issues caused by missing or misinterpreted consent signals, but it does not guarantee advertising revenue or legal compliance.
Scan report https://example.com

Generated on

0

Cookies (in total)

0 total
Categories
Do you want to scan your entire website?

Our free scan is limited to the URL you entered. To discover all the cookies set by your website, you need to sign up.

Sign up and scan
14-day free trial Cancel anytime
Create a free trial account and complete your scanning
  • Database of 100,000+ cookies
  • Detect unique cookies and trackers
  • Auto-generate your first scan report
  • Schedule monthly scanning
  • Deploy a custom cookie banner
  • Access more compliance features!
FAQ

Frequently Asked Questions

IAB TCF v2.3 is the updated Transparency and Consent Framework developed by IAB Europe for standardized consent and vendor transparency signaling in digital advertising. It helps publishers, CMPs and technology vendors collect, store and communicate user consent choices through a structured TC String.

When a user visits a website or app, a CMP presents consent choices and records the user’s preferences. These choices are encoded into a TC String and shared with participating vendors. In IAB TCF v2.3, newly generated TC Strings also include the disclosedVendors segment for clearer vendor disclosure.

IAB TCF v2.3 is not a law by itself, but it is the required technical standard for participants in the IAB TCF ecosystem after the transition deadline. For publishers using major advertising platforms in regulated markets, supporting the latest TCF requirements is important for valid consent signaling.

IAB TCF v2.3 does not replace GDPR, ePrivacy or local privacy laws. It helps organizations structure consent collection, vendor disclosure, consent records and user preference management in a more standardized way.

The IAB Global Vendor List is the official registry of vendors participating in the IAB TCF framework. CMPs use the GVL to display vendor information and encode user consent preferences correctly within the TC String.

Google’s Additional Consent specification is used alongside IAB TCF for certain Google Ad Tech Providers that are not registered on the IAB Global Vendor List. It is not the same as Google Consent Mode v2.

GDPR is a legal regulation for personal data processing, while IAB TCF v2.3 is an industry framework for digital advertising consent signaling. GDPR defines legal obligations; IAB TCF v2.3 helps communicate consent, vendor and purpose information in a standardized technical format.

The main change is the mandatory disclosedVendors segment in newly generated TC Strings. This helps vendors understand whether they were actually disclosed to the user in the consent interface.

Organizations should use a CMP that supports the latest IAB TCF requirements, configure vendors and purposes correctly, generate valid TC Strings, and allow users to update or withdraw consent preferences at any time.