IAB TCF or Google Consent Mode: which one your shop needs
For an online shop advertising on Meta, TikTok and Google, the short answer is: send Google Consent Mode v2, and turn on IAB TCF only if you need it. As soon as TCF decides, even next to Consent Mode, TikTok can’t get consent at all, and Meta depends on a Google extension of TCF that not every banner supports. A banner sending only TCF also gives GA4 no analytics consent. This sits inside the bigger picture of server-side tracking for online shops.
This article describes how TallyHost reads both signals and why; it isn’t legal advice.
Two different things
Google Consent Mode v2 is four signals your cookie banner sets for Google’s tags: ad_storage, ad_user_data, ad_personalization and analytics_storage. They describe what the shopper agreed to, not who gets the data. Consent Mode v2 and server-side tracking covers how each platform uses them.
IAB TCF (the Transparency and Consent Framework of IAB Europe) is a standard string your banner stores. It records consent for numbered purposes, such as storing information on a device or personalised advertising, and separately for each vendor on the Global Vendor List. Under TCF, consent to a purpose isn’t enough: the shopper must also have agreed to that vendor.
How TCF maps onto Consent Mode
Google publishes how it reads a TCF string as Consent Mode signals. TallyHost uses the same mapping, and only consents count, not legitimate interest:
| Consent Mode signal | From TCF |
|---|---|
ad_storage |
Consent to purpose 1 |
ad_user_data |
Consent to purposes 1 and 7 |
ad_personalization |
Consent to purposes 3 and 4 |
analytics_storage |
No mapping: always taken from Consent Mode |
When your banner offers TCF, the ad signals come from TCF, even if it sends Consent Mode too. That’s how Google’s own tags work with TCF, and TallyHost does the same.
The last row is the first trap. Google doesn’t derive analytics consent from TCF, and Google Analytics isn’t a vendor on the list. A banner that sends only TCF leaves analytics_storage false, so GA4 gets nothing.
Who is on the Global Vendor List
The second trap is the vendor list itself. In version 185 of the list (12 November 2026):
- Google is there as Google Advertising Products, vendor 755.
- TikTok appears only as “TikTok Ad Network” (vendor 986), the ad network for app publishers. That’s not the TikTok Pixel or the Events API that advertisers use.
- Meta isn’t on the list at all.
What each platform gets when TCF decides
| Platform | Needs | Without it |
|---|---|---|
| Meta | Consent to purposes 1 and 7, plus Meta (provider 89) among the consents in Google’s Additional Consent | Not sent. Without purposes 3 and 4 it goes out for attribution only |
| TikTok | No standard signal exists | Never sent while TCF decides |
| GA4 | analytics_storage from Consent Mode; vendor 755 isn’t required |
Without analytics consent: not sent. Without 755: sent without hashed email or phone, ad signals denied |
| Google Ads | Consent to purposes 1 and 7, plus vendor 755 | Not sent. Without purposes 3 and 4 it goes out with personalisation denied |
Additional Consent is Google’s extension of TCF for ad technology providers that aren’t on the IAB list. Meta is provider 89 there. Using it for Meta is our deliberate approximation: it’s Google’s mechanism, not a signal Meta defines for the Pixel or the Conversions API, but no other standard one exists. Meta counts as consented only when provider 89 is among the consents (not just among the disclosed providers) in Additional Consent version 1 or 2. A banner without Additional Consent leaves Meta blocked under TCF.
TikTok has no signal TallyHost could use, so while TCF decides, the debugger shows its events as skipped with no_vendor_consent. If TikTok matters to you, use a banner with Consent Mode v2 and without TCF.
When TCF applies at all
The TCF data a banner provides includes gdprApplies. When it’s false, TallyHost ignores TCF and goes by Consent Mode; a banner that doesn’t send Consent Mode then leaves every consent denied.
To make TCF decide from the first event, turn on the IAB TCF option of the install code (the data-cmp="tcf" attribute; in the WooCommerce plugin it’s a setting). The script then waits for the banner’s TCF decision (up to 2 seconds) before sending. Without it, an early Consent Mode update could decide the first events without the vendor rules.
One more thing to check: purpose 7
ad_user_data needs consent to purpose 7 as well as purpose 1, never legitimate interest, because in Consent Mode v2 it is a consent. Some banners may store “Accept all” without explicit consent to purpose 7. Then Meta and Google Ads get no_consent even from shoppers who accepted everything, and GA4 gets no hashed email or phone. Check what your banner stores before you rely on it.
How to check your banner
- Accept everything and place a test order. With Consent Mode v2 and no TCF, each platform should get the purchase. With TCF, expect TikTok to be missing, and Meta too if your banner has no Additional Consent.
- Look at the debugger: an event skipped with
no_vendor_consentpoints to the vendor list,no_consentto the purposes or to Consent Mode. - Reject everything and check that nothing reached the ad platforms.
The panel’s consent page shows which signal your banner sends and, for each destination, the share of events over the last 7 days without consent. The consent section of the features page has more. Primary sources: Google’s guide to implementing TCF strings and the IAB Europe Global Vendor List.
Send your shop's orders from the server
TallyHost reports paid orders with consent checked, to Meta, TikTok, GA4 and Google Ads. Free up to 100,000 events a month.
Start free