> TCF 2.2 standardises consent transmission to advertising vendors. Differences with Consent Mode and implementation guide. > > Canonical: https://www.flowconsent.com/en/blog/tcf-2-2-transparency-consent-framework-guide [Regulation](https://www.flowconsent.com/en/blog?category=regulation) # TCF 2.2: understanding the Transparency and Consent Framework By FlowConsent · Published 15 March 2026 · Updated 9 October 2026 · 3 min read In short TCF 2.2 is an IAB Europe standard for transmitting consent to advertising vendors. Differences with Consent Mode, purposes and implementation. ## **TL;DR** The TCF 2.2 (Transparency and Consent Framework) is a technical standard from IAB Europe that enables structured transmission of visitor consent choices to advertising vendors (ad tech vendors). It does not replace the GDPR or Google Consent Mode: it complements them by standardising consent communication across the programmatic advertising chain. If your site displays programmatic advertising or uses adtech technologies, your CMP must support TCF 2.2. ## What is TCF 2.2? The TCF 2.2 (Transparency and Consent Framework version 2.2) is a technical framework developed by IAB Europe. It defines a standardised protocol to transmit user consent choices to advertising vendors (SSPs, DSPs, ad exchanges, data management platforms) participating in the programmatic chain. When a visitor interacts with a TCF-compatible [consent banner](https://www.flowconsent.com/en/blog/gdpr-cookie-banner-examples-best-practices), the CMP generates a TC String: an encoded character string containing the visitor consent choices for each purpose and for each vendor registered in the IAB Global Vendor List (GVL). ## What is the difference between TCF 2.2 and Consent Mode v2? TCF 2.2 and [Google Consent Mode v2](https://www.flowconsent.com/en/blog/google-consent-mode-v2-implementation-guide) are two complementary mechanisms, not competitors. Consent Mode v2 is proprietary to Google and transmits signals exclusively to Google tags. TCF 2.2 is an open industry standard transmitting choices to all vendors in the IAB GVL (over 1,000 vendors) across 11 purposes. If your site only uses Google Analytics and Google Ads, Consent Mode v2 is sufficient. If your site displays programmatic advertising via SSPs or ad exchanges, TCF 2.2 is needed in addition. ## Who needs to implement TCF 2.2? Publishers who monetise through programmatic advertising and work with GVL-registered vendors. Adtech vendors (SSPs, DSPs, DMPs) processing consent data in the EEA must also be registered and respect TCF signals. If your site does not display programmatic advertising, TCF 2.2 is not necessary. A standard [consent banner](https://www.flowconsent.com/en/blog/cookie-banner-gdpr-compliance-guide) with Consent Mode v2 covers your needs. ## TCF 2.2 purposes TCF 2.2 defines 11 purposes and 2 special purposes. These cover device storage (purpose 1), limited ad selection (purpose 2, new), ad profiling (purposes 3-4), content personalisation (purposes 5-6), performance measurement (purposes 7-8), audience understanding (purpose 9), service improvement (purpose 10), and limited content selection (purpose 11, new). ## How does TCF 2.2 work in practice? The TCF-compatible CMP displays the consent banner with purposes and vendors. The visitor makes their choices. The CMP generates the encoded TC String and stores it. Advertising scripts read the TC String via the CMP API (\_\_tcfapi method) and adapt their behaviour based on consents obtained. To be valid, a CMP must be registered with IAB Europe and obtain a CMP ID. The main CMPs on the market support TCF; support is coming soon to FlowConsent. ## What changed between TCF 2.1 and TCF 2.2? TCF 2.2, published in May 2023, removes legitimate interest for purposes 3-6 (profiling), requires explicit consent for those purposes, adds two new purposes (2 and 11), and requires vendors to provide processing description URLs for greater transparency. ## Common mistakes with TCF 2.2 **Confusing TCF with Consent Mode.** These are two different mechanisms. TCF concerns the programmatic chain, Consent Mode concerns Google tags. **Enabling TCF on a site without programmatic advertising.** TCF adds complexity to the banner. If your site does not need it, it makes the banner unnecessarily complex. **Using a CMP not registered with the IAB.** Only registered CMPs can generate valid TC Strings. Adtech vendors reject signals from uncertified CMPs. **Not updating the Global Vendor List regularly.** The GVL is updated frequently. An outdated version may cause incorrect consent transmission. ## Checklist: implementing TCF 2.2 1. Verify that your site uses programmatic advertising requiring TCF. 2. Choose a [CMP registered](https://www.flowconsent.com/en/blog/how-to-choose-consent-management-platform) with IAB Europe. 3. Configure TCF purposes in the consent banner. 4. Identify GVL vendors used on your site. 5. Configure Consent Mode v2 in parallel for Google tags. 6. Test TC String generation with a decoding tool. 7. Verify that adtech scripts correctly read the TC String via \_\_tcfapi. 8. Run a [cookie audit](https://www.flowconsent.com/en/scan) to confirm pre-consent blocking. ## Conclusion TCF 2.2 is a necessary standard for sites participating in programmatic advertising in the EEA. It completes the compliance chain by standardising consent transmission to adtech vendors. If your site does not display programmatic advertising, TCF is not necessary. Start with a [scan of your site](https://www.flowconsent.com/en/scan) to identify the scripts present and determine whether TCF is relevant for your configuration. [Back to the blog](https://www.flowconsent.com/en/blog) Share this article · [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.flowconsent.com%2Fen%2Fblog%2Ftcf-2-2-transparency-consent-framework-guide) · [X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fwww.flowconsent.com%2Fen%2Fblog%2Ftcf-2-2-transparency-consent-framework-guide) Questions ## Common questions on this topic. Can't find your question? Write to us, we answer fast. [Write to us](https://www.flowconsent.com/en/demo) ### What is the difference between TCF 2.2 and Google Consent Mode v2? TCF 2.2 is an open standard from IAB Europe that transmits consent to all advertising vendors registered in the Global Vendor List (over 1,000 vendors). Consent Mode v2 is a proprietary Google mechanism that transmits consent exclusively to Google tags. Both are complementary. ### Does my site need to implement TCF 2.2? TCF 2.2 is necessary if your site displays programmatic advertising via SSPs, ad exchanges or third-party ad networks registered in the IAB GVL. If you only use Google Analytics and Google Ads without programmatic advertising, Consent Mode v2 is sufficient. ### What is a TC String? The TC String is an encoded character string generated by the TCF-compatible CMP. It contains the visitor consent choices for each purpose and each vendor. Advertising scripts read this string via the \_\_tcfapi API to adapt their behaviour. ### Does TCF 2.2 replace the GDPR? No. TCF 2.2 is a technical framework that standardises consent transmission in the programmatic advertising chain. It does not replace the GDPR, which is the legal framework. TCF is a tool for GDPR compliance in the context of online advertising. ### What changed between TCF 2.1 and TCF 2.2? TCF 2.2 removes legitimate interest for advertising profiling purposes (purposes 3 to 6) and requires explicit consent. Two new purposes were added (purposes 2 and 11) to better distinguish contextual advertising from targeted advertising. ### Does my CMP need to be registered with the IAB to use TCF? Yes. Only CMPs registered with IAB Europe and holding a CMP ID can generate valid TC Strings. Adtech vendors reject signals from uncertified CMPs. The list of registered CMPs is public on the IAB Europe website. Read next ## Keep reading. [All articles](https://www.flowconsent.com/en/blog) [Marketing tools · 29 May 2026](https://www.flowconsent.com/en/blog/google-consent-mode-v2-implementation-guide) ### [Google Consent Mode v2: the complete guide to understanding and implementing it](https://www.flowconsent.com/en/blog/google-consent-mode-v2-implementation-guide) [The reference guide to Google Consent Mode v2: why it is mandatory, its four parameters, basic vs advanced, a step-by-step setup with GTM and on the main platforms, and the errors to fix.](https://www.flowconsent.com/en/blog/google-consent-mode-v2-implementation-guide) [Read the article ](https://www.flowconsent.com/en/blog/google-consent-mode-v2-implementation-guide)· [Best practices · 9 October 2026](https://www.flowconsent.com/en/blog/what-is-consent-management-platform-cmp) ### [What is a consent management platform (CMP)? Definition and how it works](https://www.flowconsent.com/en/blog/what-is-consent-management-platform-cmp) [A consent management platform (CMP) asks visitors for permission before cookies run, enforces their choice and keeps proof of it. Here is what a CMP does, why the law requires one, and how it works.](https://www.flowconsent.com/en/blog/what-is-consent-management-platform-cmp) [Read the article ](https://www.flowconsent.com/en/blog/what-is-consent-management-platform-cmp)· [Comparisons · 3 March 2026](https://www.flowconsent.com/en/blog/how-to-choose-consent-management-platform) ### [How to choose a consent management platform (CMP) in 2026](https://www.flowconsent.com/en/blog/how-to-choose-consent-management-platform) [A practical method to choose a CMP: the ten criteria that matter, the main types of tools on the market, a five-step evaluation and a checklist for any vendor.](https://www.flowconsent.com/en/blog/how-to-choose-consent-management-platform) [Read the article](https://www.flowconsent.com/en/blog/how-to-choose-consent-management-platform) ## Make your site compliant today. Free up to 25,000 sessions a month. No credit card, no commitment. [Create my banner](https://app.flowconsent.com/auth/sign-up?utm_source=flowconsent.com\&utm_medium=referral\&utm_campaign=general) · [Scan my site](https://www.flowconsent.com/en/scan)