IAB TCF v2.2
IAB TCF v2.2 is the advertising industry standard for collecting and sharing consent choices. It lets your site create a TC String (a standardized consent signal) that ad platforms and vendors can read to decide whether they’re allowed to run personalized ads, store cookies, or process data.
How it works
1) Consent is shared as a TC String
- When a visitor makes choices, ConsentMagic generates a TC String.
- That string is saved in a cookie (and used by supported ad tech).
- Participating vendors read the TC String to determine what they can do.
2) Vendors rely on the IAB Global Vendor List (GVL)
- The GVL is the official list of ad vendors that support TCF.
- ConsentMagic pulls the latest GVL so you can show a correct vendor list in the UI and keep everything up to date.
3) Users get a granular consent interface
Instead of simple “Accept / Reject,” TCF provides fine-grained controls, typically for:
- Purposes (why data is used, e.g., personalized ads, measurement)
- Special purposes / features (depending on your setup)
- Vendors (specific ad companies)
What changes on your site
- Ad vendors that support TCF will check consent first (via the TC String) before serving personalized ads or using cookies for advertising purposes.
- You get a TCF-compliant banner/preferences panel designed specifically for ad-tech consent.
- Consent is recorded in a format that large ad platforms understand and expect.
How to enable it in ConsentMagic
- Go to ConsentMagic → Rules and edit the rule where you want TCF (often your EU/GDPR rule).
- Set Consent type to IAB (TCF v2.2).
- Go to ConsentMagic → IAB Settings and configure:
- Vendor visibility (which vendors appear)
- Any available display / compliance options you need
- Save.
Important note (UI customization)
In IAB mode, the consent UI follows strict framework requirements. For compliance reasons, custom text editing is limited/disabled, because the wording and structure must remain consistent with TCF expectations.