Certified for
IAB TCF v2.2

The TCF is a global standard developed by IAB Europe to help websites, apps, and ad-tech vendors share consent signals in a structured, interoperable way. It encodes a visitor's consent for specific purposes (1–11) and vendors into a single compact string — the "TC string" — that every TCF-compliant vendor can read.

451 is Consentik's official Consent Management Platform identifier with IAB Europe. It appears inside every TC string we generate, allowing ad vendors and auditors to verify that the consent signal came from an IAB-registered CMP — a baseline requirement for participating in the Open RTB / IAB ecosystem.

GDPR and Google Consent Mode V2 cover what consent the visitor has given. IAB TCF is what makes that consent readable by every other ad vendor — Amazon DSP, Criteo, The Trade Desk, and over 1,200 registered partners. If your site runs IAB-compliant ads or sells inventory through programmatic exchanges, you need TCF.

Every vendor on the IAB Global Vendor List (GVL) — currently over 1,200 — including Google Ad Manager, Amazon Publisher Services, Criteo, The Trade Desk, Magnite, PubMatic, Index Exchange, and Xandr. The vendor list updates automatically inside Consentik when IAB publishes a new GVL revision.

The opposite — without TCF, IAB-compliant vendors treat traffic from your site as non-consented by default, which suppresses bid prices and fill rates. Consentik's TCF banner is optimized for clarity, producing some of the highest opt-in rates in the industry. Most sites see ad revenue increase after enabling TCF, not decrease.

TCF v2.2 introduces enhanced features to strengthen user privacy, including more granular consent options and improved transparency about how vendors use data. Consentik implements the full TCF v2.2 specification — existing configurations work automatically with no merchant action required.