Consent Mode v2 and server-side tracking: who needs what

Server-side tracking doesn’t remove the need for consent. Sending an event from a server instead of the browser changes where the request comes from, not whether the shopper agreed to it. What changes is the work: the shopper’s choice from the cookie banner has to travel with every event to the server, and the server has to apply it, for each platform separately.

This article covers how that works with Google Consent Mode v2. It describes what we built and why; it isn’t legal advice.

Your cookie banner (the consent management platform, CMP) sets four signals:

Signal What the shopper agrees to
ad_storage Advertising cookies on the device
ad_user_data Sending their data to Google for advertising
ad_personalization Personalised advertising, remarketing included
analytics_storage Analytics cookies on the device

Google defined them, but they describe the shopper’s choice well enough that we use the same four signals for Meta and TikTok too.

What each platform needs before an event goes out

Each platform needs a different combination. These are the rules TallyHost applies by default:

Platform Needs Without ad_personalization
Meta ad_storage and ad_user_data The event goes out for attribution only (opt_out)
TikTok ad_storage, ad_user_data and ad_personalization Not sent: TikTok has no equivalent of Meta’s opt_out
GA4 analytics_storage Sent with personalisation denied; hashed email and phone only with ad_user_data
Google Ads ad_storage and ad_user_data Sent with personalisation denied

Look at Meta and TikTok side by side. A shopper who accepts ad cookies but rejects personalisation still counts as a conversion in Meta, flagged so Meta uses it only to attribute the conversion to the campaign. TikTok gets nothing, because its API has no equivalent of that flag for shoppers in Europe.

GA4 is the other way round: it doesn’t need ad consent at all to count the purchase, only analytics consent. If you also use IAB TCF, the rules add consent per vendor; IAB TCF or Google Consent Mode covers what that means for each platform.

The browser half: wait for the banner

On the page, the tracking script must not set or read ad cookies before the shopper decides. The TallyHost script waits for the banner’s decision (up to 2 seconds), then sends the queued events with it. Without ad_storage it doesn’t read or write _fbp, _fbc, _ttp or the click IDs (ttclid, gclid, gbraid, wbraid) and doesn’t load any pixels; _ga is read only with analytics_storage.

A purchase sent from your shop’s server when the order is paid (see paid orders that never reach the thank-you page) leaves when the shopper may be long gone. The server can’t ask the banner.

So the decision has to be saved earlier. The TallyHost script keeps the shopper’s current decision in one first-party cookie, the only one it sets regardless of consent, because it is needed to respect the choice. At checkout, the WooCommerce plugin reads that cookie and saves the consent in the order. When the order is paid, the purchase goes out with exactly that consent. A missing or broken cookie counts as no consent.

No banner, no events

If your site has no CMP sending Consent Mode v2 or TCF, all four signals are false and nothing reaches the platforms. The panel warns about it during setup. Without any consent, the IP address, user agent and browser identifiers are also removed before the event is stored; the event stays only to be counted and shown in the debugger.

The gap that consent leaves is the shopper’s choice. Server-side tracking closes other gaps (a thank-you page that never loads, a blocked request), but not that one; our article on why GA4 shows fewer orders than WooCommerce separates the two.

How to check your setup

  1. Accept everything in your banner, place a test order and check that each platform received the purchase. This holds for a banner with Consent Mode v2 and without TCF; once TCF decides, even next to Consent Mode, TikTok gets nothing and Meta needs Google’s Additional Consent from your CMP.
  2. Reject everything, place another one and check that nothing arrived.
  3. Accept everything except personalised advertising. Meta should get the purchase for attribution only, TikTok nothing.

In TallyHost, the debugger shows each event with the consent it carried and, for every platform, whether it went out or was skipped for lack of consent. The consent section of the features page shows what the panel reports.

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

Read next