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:
| Parameter | What it controls |
|---|---|
ad_storage | Storage such as cookies for advertising |
analytics_storage | Storage such as cookies for analytics |
ad_user_data | Sending user data to Google for advertising (new in v2) |
ad_personalization | Personalised 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:
- Basic: Google tags do not load until the visitor interacts with the banner. If they decline, nothing is sent to Google, not even the consent status.
- Advanced: tags load straight away with consent defaulting to denied. While consent is denied, they send measurements without cookies, which Google uses to model conversions. Full measurement data is sent only after the visitor grants consent.
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.
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:
- Your banner still matters. Moving delivery to a server does not remove the need to ask. Our post on whether server-side tracking is GDPR-ready covers that point.
- Google also takes consent on uploads. Google's Ads API documentation lists a consent field on uploaded click conversions, so a server can pass a granted or denied value for user data. That is the server-side counterpart of
ad_user_data. - Google ties hashed data to consent. Per Google's consent-mode documentation, when ad personalization consent is denied, personal data collection for advertising is disabled, including enhanced conversions hashed first-party data.
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:
| Source | How it is read |
|---|---|
| Cookiebot | The marketing category and its accept and decline callbacks |
| OneTrust | The active targeting group |
| IAB TCF v2 | The consent string from the CMP |
| Manual override | window.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
- The visitor explicitly denies marketing consent: SyncBeacon stores the event for your records but does not forward it to any ad platform.
- Consent is missing: marketing identifiers (IP, user agent, click IDs and similar) are removed from the payload before forwarding. Some destinations then skip or fail the event because they have nothing left to match on.
- No banner at all: your own marketing consent setting in the dashboard decides whether identifiers are used.
- Orders from store webhooks: these do not carry the visitor's banner choice, so for them the merchant-level setting decides. Check that setting matches how your store collects consent.
- Google Ads uploads carry consent fields: granted when consent was given, otherwise unspecified.
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
- If you use Cookiebot, OneTrust or a TCF v2 CMP, install the tracker and test: accept, decline, then check what Conversions shows for each.
- If you use another banner with Google Consent Mode, call the manual override from its accept and decline callbacks, then test both paths.
- Keep your Google tags on Consent Mode as before. SyncBeacon does not change that, and it does not replace the Google tag.
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:
| Test | What to do | What you should see |
|---|---|---|
| Accept all | Accept the banner, click an ad link, place an order | The order is forwarded and each destination shows as delivered |
| Reject marketing | Reject marketing cookies, place an order | The event is stored but not forwarded to any ad platform |
| No choice yet | Ignore the banner, place an order | The outcome follows your marketing consent setting |
| Change of mind | Accept, then withdraw consent in the banner settings | Later 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
- SyncBeacon does not send limited or non-identifying data for consent-denied orders. Explicit denial blocks forwarding.
- It does not take part in Google's Consent Mode modeling. That modeling is based on pings from Google tags in the browser.
- The tracker is not cookie-free. It sets a first-party cookie and uses browser storage. It does not use third-party cookies.
- None of this is legal advice or a certification. The banner, the lawful basis and your Google settings remain your decisions.
Related reading
- Server-side tracking
- Is server-side tracking GDPR-ready?
- Google Enhanced Conversions for Shopify and WooCommerce
- SyncBeacon vs Google Tag Manager for GDPR
Sources
- Google for Developers, Consent mode overview
- Google for Developers, Set up consent mode on websites
- Google for Developers, Import offline conversions with the Google Ads API
Get started
Consent-aware server-side tracking
Connect your store, set your consent mode, and see per-platform delivery for every order.
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.