Is server-side tracking GDPR-ready? It depends on what you mean by the question. Server-side tracking is a delivery method. It can be run in a way that respects visitor choices, or in a way that ignores them. The method alone does not decide.
Merchants usually ask about server-side tracking GDPR for one of two reasons: they hope it removes the need for a cookie banner, or they fear it makes things worse. Neither is quite right. This post sets out what changes, what stays the same, and what SyncBeacon does about each, using the wording we can back up.
GDPR-ready is not GDPR compliant
We say "GDPR-ready" deliberately. It means the product has the controls a merchant needs to operate in line with the GDPR: consent gates, a data processing agreement, retention limits, export and deletion. It does not mean a certificate, a regulator's approval or a guarantee about your own use of it.
Under the GDPR you, as the merchant, are the controller. You choose the lawful basis, you run the banner, you sign the contracts, and you answer for what is sent to ad platforms. A tool processes data on your instructions. If a vendor tells you their product is simply "compliant", ask what they are assuming about you.
What moving to the server changes
| Question | Browser pixel | Server-side |
|---|---|---|
| Who sends data to the ad platform? | The visitor's browser, directly | A server you control or a relay you hire |
| Can you inspect what leaves? | Hard, it depends on scripts you load | Yes, the payload is yours to define and log |
| Can you strip fields? | Limited | Yes, before anything is forwarded |
| Do you still need consent? | Yes | Yes |
| Does the ad platform still receive personal data? | Yes | Yes, if you send identifiers |
The gain is control. The data path goes through a place where you can enforce rules, rather than through scripts that run on the visitor's device. The risk is that the same control is used to send data that the visitor declined. Control is not compliance.
Consent is still the central question
Storing or reading information on a visitor's device, and sending their data to an advertiser, both raise consent questions under EU law. The ePrivacy Directive covers access to a user's device, and the GDPR covers the processing of the personal data that results. Server-side delivery does not remove either.
What matters in practice is that the visitor's choice reaches the system that sends the event, and that the system honours it. This is how SyncBeacon behaves:
- The browser tracker detects marketing consent from Cookiebot, OneTrust, IAB TCF v2 consent strings, and a manual window.SyncBeaconConsent override. Other banners are not detected automatically. See Consent Mode v2 and server-side tracking for the details.
- If a visitor explicitly denies marketing consent, the event is stored for the merchant's records but not forwarded to ad platforms.
- If consent is missing, marketing identifiers (IP address, user agent, click IDs and similar) are removed from the forwarding payload.
- Without any banner, the merchant's own marketing consent setting decides whether identifiers are used.
- Forwarding stops entirely for merchants who have not accepted the data processing agreement or who have an Article 18 processing restriction.
One thing we do not do: send "limited, non-identifying" data for consent-denied orders. An explicit denial blocks forwarding.
EU-hosted, and what that does not mean
SyncBeacon's infrastructure is EU-hosted. It runs with Hetzner Online GmbH in Germany, which is listed as a sub-processor in our privacy notice. The company behind SyncBeacon is a German GbR.
That statement is narrower than it sounds, and we keep it narrow on purpose. The relay runs on EU infrastructure. Events that you choose to forward then go to Meta, Google and the other ad platforms, which process data under their own terms and may do so outside the EU. Those transfers rely on each platform's own transfer mechanisms. We do not say that data never leaves the EU, and we do not claim there is no US transfer, because forwarding to ad platforms is the point of the product.
How personal data is handled
- Hashing: email and phone are SHA-256 hashed before events are stored or sent. Hashing is pseudonymisation, not anonymisation. A platform that holds the same email can compute the same hash, so treat hashed data as personal data.
- What is stored: store webhooks arrive with customer data, and SyncBeacon hashes it on receipt and drops the customer block before storing the event. Browser event payloads can still hold an IP address and user agent until the retention period ends, so we do not claim that no personal data is stored.
- Retention: event data is kept for the conversion-history period of your plan and then purged automatically.
- Control: merchants can export or delete personal data from the dashboard.
- Cookies: the tracker is not cookie-free. It sets a first-party cookie and uses browser storage. It does not use third-party cookies.
Who is responsible for what
| Responsibility | You (the merchant) | SyncBeacon |
|---|---|---|
| Lawful basis and banner | Choose it, run the banner, keep records | Reads supported banner signals and honours them |
| Contract with the tool | Accept the data processing agreement | Stops forwarding if it is not accepted |
| Contract with ad platforms | Accept each platform's data terms | Cannot do this for you |
| What is sent | Decide which destinations are connected | Hashes identifiers and removes marketing identifiers without consent |
| Access and deletion requests | Handle requests from your customers | Provides export and delete controls in the dashboard |
Questions to ask any server-side vendor
- Where does the relay run, and which sub-processors are involved?
- What happens to an event when the visitor declines marketing consent?
- Which banners does it detect, and which need manual work?
- What personal data is stored, and for how long?
- How do you export or delete one person's data?
- Does the vendor describe itself as compliant? If so, what is it assuming about you?
What you still need to do
- Run a consent banner that matches your lawful basis, and check that it actually blocks non-essential scripts before consent.
- Update your privacy notice so it names the ad platforms you send data to and why.
- Accept the data terms of each ad platform you use, and sign the data processing agreement with your tracking provider.
- Send only what you need. Do not forward identifiers you cannot justify.
- Test the deny path. Decline the banner on a test order and confirm nothing is forwarded.
- Get legal advice for your market. Interpretations differ between member states and data protection authorities.
Common server-side tracking GDPR questions
Does server-side tracking get around ad blockers and consent?
It gets around ad blockers, because no script runs in the browser for that event. It does not get around consent. Treating it as a way to avoid asking is the mistake that causes trouble.
Do I need a banner if I only send hashed data?
Hashed data is still personal data, and the lawful basis for sending it is your call. Many EU merchants rely on consent. Ask your counsel, and see our comparison with Google Tag Manager for how the two approaches differ.
Related reading
- Server-side tracking
- GDPR conversion tracking with SyncBeacon
- Consent Mode v2
- Meta Conversions API without a developer
Sources
Get started
Server-side tracking with consent built in
EU-hosted, GDPR-ready server-side tracking for Shopify, WooCommerce and Shopware.
Not legal advice. GDPR obligations depend on your jurisdiction, business model and consent setup. Talk to your data protection officer or legal counsel before relying on any tracking configuration.