IAB TCF v2.4 Support
Last updated: November 3, 2026
CYBEXO Web CMP and Mobile CMP support IAB Transparency and Consent Framework (TCF) 2.4. Use the applicable integration guide to install the current release and verify the configuration, disclosures and consent behavior in your own website or app.
Supported installation paths
Section titled “Supported installation paths”| Surface | Implementation and guide |
|---|---|
| Direct Web | The managed Web CMP runtime; see Web setup and Web TCF disclosures and lifecycle. |
| Google Tag Manager | Loads the shared Web CMP runtime; see the GTM template guide. |
| WordPress | Loads the shared Web CMP runtime; see WordPress integration. The plugin version is separate from the runtime version. |
| Shopify | Connects the shared Web CMP runtime to the storefront; see Shopify integration. |
| Drupal | Loads the shared Web CMP runtime; see Drupal integration. |
| Webflow and Wix | Use the shared Web CMP installation described in Webflow and Wix. |
| Android | Native TCF 2.4 choices in Android SDK 2.0.1; see Android setup and its API reference. |
| iOS | Native TCF 2.4 choices in iOS SDK 2.0.3; see iOS setup and its API reference. |
Framework support does not by itself verify a customer’s installation, connected tags or recipient configuration. Google certification and third-party platform review are separate from implementation support.
TCF 2.4 disclosures
Section titled “TCF 2.4 disclosures”The privacy controls use official vendor-list information for purposes, vendors and their declared processing. The TCF 2.4 disclosure changes include the explanation of Features as processing methods, the illustrations supplied for Features, and the current name and wording for Special Feature 2.
Check that the relevant information is reachable in the first and second layers, including purpose and vendor details. Use the official text available for the selected language. Do not invent missing vendor-list wording or illustrations. See the IAB Europe policies and IAB technical specifications for normative requirements.
Web verification
Section titled “Web verification”Install the CMP before dependent tags and TCF consumers. Confirm that there is one intended loader and no conflicting CMP installation. Check ping and use addEventListener to observe the current consent state and later changes:
let listenerId;window.__tcfapi('addEventListener', 2, (data, success) => { if (!success || !data) return; listenerId = data.listenerId; console.log({ cmpStatus: data.cmpStatus, eventStatus: data.eventStatus, gdprApplies: data.gdprApplies, tcString: data.tcString });});The API argument remains 2; TCF 2.4 is not a request to change that argument to 2.4. The framework revision, API version, TC String version, policy version and SDK or plugin version identify different things.
A function or loading stub alone does not prove successful initialization. Verify the actual ready state, choice changes, saved decisions and error recovery. Remove a temporary listener when finished:
if (listenerId !== undefined) { window.__tcfapi('removeEventListener', 2, removed => { console.log('Listener removed:', removed); }, listenerId);}See TCF API validation for lifecycle checks. Keep TC strings and detailed diagnostic output in your controlled audit records rather than public logs.
Native Android and iOS verification
Section titled “Native Android and iOS verification”Native apps use their SDK’s consent snapshot and stored IAB TCF values. A native app is not expected to expose a website’s window.__tcfapi. Use the relevant SDK guide for the actual public methods and supported app-owned WebView bridge.
For a TCF-enabled app configuration, verify the actual TC string, purpose consent and legitimate-interest choices, vendor choices and special-feature choices against the published configuration. Check that saved choices survive a normal relaunch and that reopening preferences shows the saved state. Decode actual strings when validating the encoded choices; do not infer grants from the mere presence of a string or vendor disclosure.
Verify the separate Analytics choice and the effective Google consent values as well. Exercise Analytics-only withdrawal and Google vendor refusal, then confirm that the app’s optional events and connected recipients respect those choices. A local SDK API result is not proof that a remote recipient received an event.
TCF-enabled and TCF-disabled configurations
Section titled “TCF-enabled and TCF-disabled configurations”TCF and Google Consent Mode are separate controls. Android and iOS can use a published Google consent choices configuration without a TC string. This mode still requires testing all four Google consent choices, saving and discarding changes, relaunch, rejection and withdrawal.
Show the configuration and its effective state when reviewing TCF-disabled behavior; a regional banner that happens not to appear does not demonstrate this mode. For a worldwide TCF review, configure worldwide coverage so the reviewer can reach the TCF controls regardless of location. Test ordinary visitor-region routing separately and identify the configuration used.
For both modes, verify the installed integration and dependent tags or SDKs. Preserve a matching receiver event where remote delivery is part of the test, and verify blocked requests at the point where optional event collection is controlled. See Google Consent Mode validation and the pre-launch checklist.