Consent

Consent Mode v2 and server-side tracking: what SyncBeacon reads and does

Consent Mode v2 is Google's consent signalling. SyncBeacon works differently: it reads your banner's own consent state and blocks forwarding when a visitor says no. This page spells out the difference, without claiming more than the code does.

Works with

Shopify · WooCommerce · Shopware

Connects to

OpenAI Ads · Meta Ads · Google Ads · Microsoft Ads · Pinterest · Snapchat · X ads · TikTok (upcoming) · GA4 (coming soon)

Built for modern ecommerce

Simple to set up · EU-hosted · GDPR-ready · Secure event processing

Conversion events we support

PageView · ViewContent · Search · AddToCart · InitiateCheckout · AddPaymentInfo · Purchase

Also supported

OrderCancelled · Lead · CompleteRegistration

Last updated:

What Consent Mode v2 is, in short

Google Consent Mode is a way for your cookie banner to tell Google tags what a visitor has agreed to. Version 2 added two signals, ad_user_data and ad_personalization, next to the existing ad_storage and analytics_storage. Google tags then adjust how they behave. Check Google's own documentation for current requirements in your market, since they change.

Consent Mode v2 lives in the browser and speaks to Google tags. It is not a universal switch for every ad platform, and it doesn't say anything about what a server does with an order. That gap is what this page is about.

What SyncBeacon detects, and what it doesn't

SyncBeacon's tracker script (sb.js) looks for a marketing-consent signal from these sources:

Consent sources the SyncBeacon tracker reads
SourceRead by SyncBeaconHow
CookiebotYesReads the marketing consent state and reacts to accept and decline
OneTrustYesReads the marketing category from the banner's active groups
IAB TCF v2YesReads the consent string through the standard TCF interface
Manual overrideYeswindow.SyncBeaconConsent with a marketing true or false value
Google Consent Mode signalsNoNot read today

We name Cookiebot, OneTrust and IAB TCF because those are the ones we have built and can stand behind. We don't list other banners as supported, because the script doesn't detect them by name.

What it means that Google Consent Mode isn't read

SyncBeacon does not read Google Consent Mode state. In practice, this splits into three situations:

  • Your banner is Cookiebot, OneTrust or a TCF banner. SyncBeacon reads the banner's own consent state directly. It doesn't matter that the same banner may also be driving Consent Mode for your Google tags, because SyncBeacon looks at the banner, not at the Google signals.
  • Your banner only exposes Google Consent Mode. SyncBeacon can't see it. You can pass the decision across yourself by setting window.SyncBeaconConsent with a boolean marketing value, for example from your banner's accept and decline callbacks.
  • There is no banner signal at all. Your own consent setting in SyncBeacon decides whether identifiers are used.

This is about server-side tracking consent for the data SyncBeacon relays. It is not a statement that your Google tags are or aren't configured correctly. That remains a banner and tag setup question.

What happens when consent is denied

Consent state and what SyncBeacon does with the event
Consent stateWhat SyncBeacon does
Visitor explicitly denies marketing consentThe event is stored for your records and not forwarded to any ad platform
No banner signal, marketing consent missingMarketing identifiers (IP, user agent, click IDs, fbp and fbc and similar) are removed. Several connectors then skip or fail the event
Visitor grants marketing consentThe event is forwarded with hashed email and phone and the click IDs that were captured
DPA not accepted, or processing restrictedForwarding stops for that merchant

A denial doesn't send a trimmed, anonymous version of the conversion; it blocks forwarding. The cost is real: you lose those conversions in the ad platform. The benefit is that the rule is simple and you can explain it to a data protection officer. Email and phone are SHA-256 hashed before events are stored or sent.

For Google Ads specifically, uploads also carry consent fields (set to granted or unspecified), and hashed identifiers are only attached when consent is granted. See Google Ads Enhanced Conversions.

Passing your banner's decision to SyncBeacon manually

If your banner isn't one of the three we detect, the manual override is the supported route. It is a plain browser global that your banner's accept and decline handlers can set:

// when the visitor accepts marketing
window.SyncBeaconConsent = { marketing: true };

// when the visitor declines marketing
window.SyncBeaconConsent = { marketing: false };

The value has to be a real boolean. Anything else is ignored and treated as no signal. Test it on your own store: decline in the banner, place a test order, and check on the Conversions page that the event was not delivered to your destinations. Then accept and confirm that delivery happens. We can't test every banner configuration for you, so treat this check as part of your setup.

What this page does not claim

SyncBeacon is GDPR-ready and the relay runs on EU infrastructure hosted by Hetzner Online GmbH in Germany. That is not the same as being compliant, and it isn't a claim that Consent Mode v2 is implemented or certified. The ad platforms you forward to process data under their own terms, including outside the EU, and consent wording, banner setup and legal basis stay your decision. This is not legal advice.

More on the data side: GDPR conversion tracking, the server-side tracking guide, and the destination pages for Meta, Pinterest, Snapchat, X and OpenAI Ads. Related reading: Consent Mode v2 and server-side tracking and is server-side tracking GDPR-ready. Plans are on the pricing page.

Supported today

Stores: Shopify · WooCommerce · Shopware

Ad platforms: OpenAI Ads · Meta Ads · Google Ads · Microsoft Ads · Pinterest · Snapchat · X ads

FAQ

Frequently asked questions

Does SyncBeacon support Consent Mode v2?

SyncBeacon doesn't read Google Consent Mode signals. It reads Cookiebot, OneTrust and IAB TCF v2 consent state directly, plus a manual override, and blocks forwarding when a visitor denies marketing consent.

Which consent banners does SyncBeacon detect?

Cookiebot, OneTrust and IAB TCF v2 consent strings, plus a manual window.SyncBeaconConsent override. Other banners aren't detected by name; you can use the override with them.

What does server-side tracking consent mean in practice?

Consent still applies when a server sends the event. SyncBeacon stores the event but doesn't forward it if the visitor denied marketing consent, and removes marketing identifiers when consent is missing.

Does a consent-denied order still send limited data?

No. An explicit denial blocks forwarding to ad platforms. The event is kept for your own records.

My banner only supports Google Consent Mode. What do I do?

Set window.SyncBeaconConsent to an object with a boolean marketing value from your banner's accept and decline handlers, so SyncBeacon gets the same decision.

Ready to connect your store and ad platforms?

Get started in minutes. No developer required for Shopify, WooCommerce, or Shopware setup.