Server-side tracking sends your measurement data first to a server you control, and only then to GA4, Google Ads or Meta [1]. That way you decide what each platform receives, and cookies keep working for longer. You still need your cookie banner, and besides hosting you mainly pay for the setup.
Behind an address on your own domain runs a server container, usually from Google Tag Manager. It receives the events from your website, leaves out or adds fields, and forwards them to the platforms you choose [1]. The web container on your site is still needed: it captures clicks, forms and purchases.
Whether you set it up yourself or bring in a Google Analytics agency: only start once your measurement plan and your consent are in order. An event that counts twice today will count twice via your server too.
What does server-side tracking deliver?
Mainly control and better signals, not a fixed percentage of extra conversions.
- Control over what you pass on. For each destination, you decide which fields leave. An email address that accidentally ends up in a URL gets filtered out, and a platform that doesn't need the IP address doesn't get it.
- Cookies that last longer. Safari deletes cookies set via JavaScript after seven days without interaction. A cookie set by your own server escapes that, unless the request goes through a CNAME or a third-party IP address [2].
- Server-to-server connections. Via Meta's Conversions API and Google Ads' conversion integrations, platforms learn from real results, such as the margin or a lead that became a customer. Meta deduplicates pixel and server events if the name and event ID match, within 48 hours [3].
- Less code in the browser, but only if you actually remove scripts. The web container and the Google tag remain.
What exactly you gain at Meta is explained in Meta Pixel or Conversions API? Why you need both.
What it doesn't do: replace your consent, or fix a poor measurement plan. The percentages circulating online rarely come with a measurement method. What you recover depends on your share of Safari visitors, ad blockers and your consent rate, so measure it against your own orders or leads.
Two arguments are best ignored. Bypassing ad blockers: anyone who refuses in your banner may not be tracked via your own server either. And the disappearance of third-party cookies in Chrome: in April 2025, Google decided to keep its current approach in Chrome [4].
Do you still need your cookie banner?
Yes: server-side tracking changes the route of your data, not the rules. In Belgium, the cookie rule is in Article 10/2 of the Framework Act of 30 July 2018. The Belgian Data Protection Authority (DPA) has no exemption for cookies that count visitors, not even for first-party cookies [5], [6].
The rule also applies to pixels, device fingerprinting and local storage [5]. The European regulators also apply it to tracking links and certain tracking based on the IP address [7]. Code that sends information from the device still runs in the browser, so no analytics or advertising tracking without consent.
With Consent Mode, your visitor's choice travels along to your server container, and the Google tags there follow it [8]. Third-party tags, such as Meta's Conversions API, you have to make wait for that choice yourself. How to set the signals correctly is explained in Consent Mode v2 in practice: basic or advanced?.
If you forward hashed email addresses, bear in mind that hashing is pseudonymisation: it remains personal data [9]. What server-side does make possible is forwarding less and hosting in Europe, for example in the Google Cloud region europe-west1 in St. Ghislain [10].
What does server-side tracking cost?
Count on three items: hosting, setup and maintenance. The setup is usually the largest.
| Hosting | What it is | Cost | Suits |
|---|---|---|---|
| Google tag gateway via Cloudflare | Loading Google tags and measuring via your own domain, without a server container [11] | Free [12] | Sites behind Cloudflare with mainly Google tags |
| Google Cloud Run | Your own server container in your own cloud project | About $45 per server per month, at least 2 servers recommended [13] | Those who want full control and their own invoice |
| Specialised host | The same server container, managed by a third party | Subscription based on the number of requests | SMEs without their own cloud management |
Google expects 2 to 10 servers together to handle 35 to 350 requests per second [13]; 35 per second is well over three million per day. The gateway only works for Google tags: for Meta or LinkedIn you need a server container. If you choose a specialised host, ask where the servers are located and whether you get a data processing agreement.
The setup covers your measurement plan, both containers, consent, testing and comparing. The maintenance is small but not zero: updating templates, adding new events and monitoring that the server keeps running.
Which setup suits you?
| Your situation | What we would do |
|---|---|
| Little traffic and no advertising budget | Not yet. First a clean Google Tag Manager container and good key events. |
| You mainly advertise on Google and your site runs behind Cloudflare | The Google tag gateway: free and little work. |
| You advertise on Google and Meta | A server container with GA4, Google Ads and the Conversions API, with deduplication between pixel and server. |
| Webshop with a lot of Safari traffic and customers who compare for a long time | A server container on the same origin, so that cookies of visitors with consent don't expire after seven days. |
| B2B leads that only become customers weeks later | Server-side plus offline conversions from your CRM, so that the platforms learn from customers instead of forms. |
How to go about it
- First measure where you stand. Compare a month of GA4 with your orders or leads. If you doubt your current setup, start with a free tracking audit.
- Get your key events and your consent right. Which actions really count is explained in GA4 key events and conversions: the difference explained.
- Choose hosting in a European region, with a data processing agreement, and put the cloud project and the containers in your company's name.
- Connect an address on your own domain, preferably same origin, such as
www.yoursite.be/metrics. Google recommends this; Cloud Run's default domain runs in a third-party context and can only set JavaScript cookies [14]. - Send GA4 and then the other destinations via the server. Don't also send the same event directly to GA4, and give the pixel and the Conversions API the same event ID [3].
- Test and compare. Check both containers in preview mode and, after two to four weeks, compare your figures with your baseline.
Frequently asked questions
Is server-side tracking GDPR-compliant?
Not by itself. It changes the route of your measurement data, not the rules: in Belgium, analytics and advertising tracking still require prior consent, including for pixels. You can, however, leave out fields per vendor, such as the IP address, and run your server in a European region.
Do I still need a cookie banner if I measure server-side?
Yes. The Belgian DPA has no exemption for cookies that count visitors, not even for first-party cookies. With Consent Mode you pass the choice from your banner on to your server container. Third-party tags there, such as Meta's Conversions API, you have to make wait for that choice yourself.
What does server-side tracking cost per month?
That depends on the hosting. Google estimates a server container on Cloud Run at about $45 per server per month and recommends at least two servers. Specialised hosts charge by number of requests, and the Google tag gateway via Cloudflare is free. Setup and maintenance come on top.
Does server-side tracking bypass ad blockers?
Partly: a measurement address on your own domain is blocked less often than the well-known domains of Google or Meta. But anyone who refuses in your cookie banner may not be tracked via your own server either. Bypassing ad blockers is therefore not a good reason to start.
What is the difference between server-side tagging and the Google tag gateway?
With server-side tagging you run your own server container that processes data and sends it to multiple platforms, including Meta or LinkedIn. The Google tag gateway only loads the Google tags via your own domain, without a server of your own. Lighter and cheaper, but limited to Google.
Sources
- An introduction to server-side tagging — Google for Developers, 30 Jul 2026, accessed 27 Sep 2026
- Tracking Prevention in WebKit — WebKit, accessed 27 Sep 2026
- Handling Duplicate Pixel and Conversions API Events — Meta for Developers, accessed 27 Sep 2026
- Next steps for Privacy Sandbox and tracking protections in Chrome — Google Privacy Sandbox (Anthony Chavez), 22 Apr 2025, accessed 27 Sep 2026
- Cookie-checklist — Gegevensbeschermingsautoriteit (Belgian Data Protection Authority), 17 Oct 2023, accessed 27 Sep 2026
- Heeft u toestemming nodig voor cookies voor publieksmeting (statistische of analytische cookies)? — Gegevensbeschermingsautoriteit (Belgian Data Protection Authority), accessed 27 Sep 2026
- Guidelines 2/2023 on Technical Scope of Art. 5(3) of ePrivacy Directive, version 2.0 — European Data Protection Board, 2024-10, accessed 27 Sep 2026
- Implement consent mode with server-side Tag Manager — Google for Developers, 30 Jul 2026, accessed 27 Sep 2026
- Guidelines 01/2025 on Pseudonymisation — European Data Protection Board, 16 Jan 2025, accessed 27 Sep 2026
- Regions and zones — Google Cloud Documentation, accessed 27 Sep 2026
- Set up Google tag gateway for advertisers in Google Tag Manager with Cloudflare — Tag Manager Help, accessed 27 Sep 2026
- Google tag gateway for advertisers — Cloudflare Docs, 17 Apr 2026, accessed 27 Sep 2026
- Set up server-side tagging with Cloud Run — Google for Developers, 12 May 2026, accessed 27 Sep 2026
- Map a custom domain to your tagging server — Google for Developers, 27 Jun 2025, accessed 27 Sep 2026