Consent Mode V2 vs TCF 2.3
Website owners keep hearing two things: "You need Consent Mode V2" and "You need TCF 2.3." Both relate to consent but solve completely different problems. Understanding the difference — and why you need both — is critical for maximising compliance and ad revenue.
The Core Difference
Consent Mode V2 tells Google tags how to behave based on the user's consent status. It is a communication protocol between your CMP and Google's advertising and analytics products.
IAB TCF 2.3 tells the entire programmatic advertising ecosystem — SSPs, DSPs, ad exchanges, data management platforms — what the user has consented to. It is the industry standard for the open ad marketplace.
How Consent Mode Works
- Before consent: Google tags fire in restricted mode — no cookies, no identifiers, but basic pings are sent
- After consent: Full tracking activates — cookies, conversion tracking, remarketing
- After rejection: Tags remain restricted, but Google uses AI to model conversions from the anonymous pings
How TCF 2.3 Works
- 11 standardised purposes for data processing (advertising, analytics, personalisation, measurement, etc.)
- Global Vendor List (GVL) with 1,000+ registered ad tech companies
- TC String: A coded string generated by your CMP that encodes the user's consent choices and travels with every ad request
Without a valid TC String, SSPs and DSPs will not bid on your inventory. Your programmatic CPMs drop to zero.
Why You Need Both
Consent Mode only? Google Ads works fine, but your programmatic advertising revenue suffers because ad exchanges cannot read consent status.
TCF only? Programmatic works, but Google loses conversion modelling data, Smart Bidding degrades, and remarketing audiences shrink.
Both together? Full coverage. Google products get Consent Mode signals. The programmatic ecosystem gets TC Strings. Nothing falls through the cracks.
How They Work Together
- 1. Visitor sees the consent banner
- 2. Makes their choice (accept, reject, or customise)
- 3. FlexyConsent simultaneously updates Consent Mode parameters AND generates a TC String
- 4. Google tags adjust behaviour; ad exchanges read the TC String
The Myth: "TCF Replaces Consent Mode"
This is incorrect. They are complementary, not competing. TCF is the industry standard for the open web ad ecosystem. Consent Mode is Google's proprietary framework for its own products. You cannot use one to replace the other.
FlexyConsent: One CMP, Both Frameworks
- Google Certified CMP — native Consent Mode V2 with all four parameters
- IAB Europe Registered — full TCF 2.3 with valid TC String generation
- Microsoft UET support — consent signals for Microsoft Advertising included
- One banner, one choice — two protocols handled simultaneously
FlexyConsent manages both from a single integration. Start free today.
Start Free Trial