← All posts

Blog

Consent Mode v2GDPRServer-Side Tracking

Consent Mode v2 Server-Side Tracking: What It Covers and What It Does Not

22 November 20267 min readSyncBeacon Team

Consent Mode v2 server-side tracking is a confusing pairing, because the two things live in different places. Consent Mode is a signal system for Google's browser tags. Server-side tracking moves event delivery off the browser. If you run both, you need to know which consent decision travels where.

This post explains Consent Mode v2 using Google's own documentation, shows where it stops when events are sent from a server, and says plainly how SyncBeacon handles consent today. That includes one limit you should know about before you rely on it: the SyncBeacon tracker does not read Google Consent Mode signals.


What Consent Mode v2 actually is

Google Consent Mode lets a website tell Google's tags what the visitor agreed to, so the tags can adjust what they store and send. According to Google, you still have to obtain the consent yourself (usually through a banner or a consent management platform), pass the choice to Google, and make sure your tags respect it. Consent Mode does not save the visitor's choice. Your banner does.

Version 2 was introduced in November 2023 and added two parameters to the existing pair. There are now four that matter for advertising:

ParameterWhat it controls
ad_storageStorage such as cookies for advertising
analytics_storageStorage such as cookies for analytics
ad_user_dataSending user data to Google for advertising (new in v2)
ad_personalizationPersonalised advertising (new in v2)

A page sets defaults before any measurement tag runs, then updates them when the visitor decides:

gtag('consent', 'default', {
  'ad_storage': 'denied',
  'ad_user_data': 'denied',
  'ad_personalization': 'denied',
  'analytics_storage': 'denied'
});

// later, when the visitor accepts:
gtag('consent', 'update', {
  'ad_storage': 'granted',
  'ad_user_data': 'granted',
  'ad_personalization': 'granted',
  'analytics_storage': 'granted'
});

Basic and advanced mode

Google describes two ways to run it:

Google says advanced mode supports a more detailed advertiser-specific model, while basic mode relies on a general one. Modeling also has a data threshold, so it does not fill every gap.

Key takeaway: Consent Mode is a way for a browser tag to tell Google what the visitor allowed. It is not a consent banner, and it does not by itself govern events that a server sends.

Server-side tracking consent: where the decision lives

In a server-side setup, a purchase is sent from a server after the order exists. There is no Google tag running in the visitor's browser for that event, so there is no live gtag consent state to read. The consent decision has to reach the server some other way, and the sender has to honour it.

Three things follow from that:


What SyncBeacon does instead

SyncBeacon does not use Google Consent Mode as its consent input. Its browser tracker (sb.js) detects marketing consent from these sources:

SourceHow it is read
CookiebotThe marketing category and its accept and decline callbacks
OneTrustThe active targeting group
IAB TCF v2The consent string from the CMP
Manual overridewindow.SyncBeaconConsent with a marketing true or false value

Google Consent Mode, Complianz, Borlabs, Usercentrics and CookieYes are not detected automatically. If your banner is one of those, you can still pass its marketing decision through the manual override from the banner's own callback. That is a small piece of JavaScript you or your developer adds, not a built-in integration.

What happens to the event

Forwarding also stops for merchants who have not accepted the data processing agreement or who have an Article 18 processing restriction on file. These consent checks run in the delivery pipeline before an event reaches any ad platform connector.

A practical setup

The Consent Mode v2 page has the product view, and GDPR and SyncBeacon lists what the consent pipeline does.


How to test the consent path

Do not trust a consent setup you have not tried. Use a private browser window and a test order for each case:

TestWhat to doWhat you should see
Accept allAccept the banner, click an ad link, place an orderThe order is forwarded and each destination shows as delivered
Reject marketingReject marketing cookies, place an orderThe event is stored but not forwarded to any ad platform
No choice yetIgnore the banner, place an orderThe outcome follows your marketing consent setting
Change of mindAccept, then withdraw consent in the banner settingsLater events are not forwarded

Check Google's side separately. Google Tag Assistant can show what your Google tags believe the consent state is, which is a different question from what SyncBeacon believes.

Common questions

Do I need Consent Mode v2 if I send conversions from a server?

If you also run Google tags in the browser, yes: Google ties its own tag behaviour and modeling to those signals. The server upload is a separate path with its own consent field. They are two places to keep consistent, not one.

Does SyncBeacon work with Google Consent Mode v2?

It works alongside it, but it does not read it. If you use Cookiebot, OneTrust or a TCF v2 CMP, the tracker picks up the visitor's marketing choice directly. If your banner only speaks Consent Mode, you pass the decision through the manual override. We would rather tell you that than imply a built-in integration.

Can I use Consent Mode v2 to avoid asking for consent?

No. Consent Mode only carries a decision. Obtaining it is your job. Google's documentation says you are responsible for obtaining consent on your site and for any data you upload to Google.

Honest limits


Sources

Get started

Consent-aware server-side tracking

Connect your store, set your consent mode, and see per-platform delivery for every order.

Get started

Not legal advice. Consent requirements depend on your jurisdiction, your banner and your lawful basis. Ask your data protection officer or legal counsel before relying on any setup.