Question 1

Does server-side tracking violate GDPR?

Accepted Answer

No — GDPR compliance is about consent and data processing, not the technical method of data collection. Server-side tracking still requires valid user consent for analytics and advertising purposes under GDPR. What changes with server-side is that you have more control over what data is sent to Google (you can strip PII, aggregate data, or apply transformations server-side before forwarding to GA4) — which can actually make compliance easier to manage than client-side. A consent management platform (CMP) that implements Google's Consent Mode v2 is still required; server-side tracking doesn't bypass consent requirements, it just provides more reliable data collection for consented users and fewer accidental PII leaks.

Question 2

How much data does server-side tracking actually recover?

Accepted Answer

Recovery rates vary by audience. In documented implementations across digital marketing agency sites and developer-focused tools (audiences with high ad blocker rates), server-side tracking recovers 25–40% more sessions than client-side GA4 alone. For general e-commerce and consumer service sites, recovery is typically 15–25%. After implementing server-side, run both implementations in parallel for 4 weeks to measure the actual gap for your specific audience — the aggregate figures are a useful benchmark but your audience may differ significantly from the average.

Question 3

Is server-side tracking a replacement for client-side GA4?

Accepted Answer

It's a complement, not a replacement — in most implementations, both client-side and server-side tags run together. The client-side web container still loads (for events where client-side data is needed, like scroll depth and click interactions), but it points to the server-side container rather than directly to GA4. The server-side container then forwards to GA4 and any other marketing platforms. Some advanced implementations run the web container in minimal mode (just capturing events and forwarding them) with all processing done server-side — this is more privacy-preserving but also more complex. For most businesses, the hybrid approach (standard web container + server-side forwarding to GA4) is the right balance of completeness and complexity.

Question 4

What does server-side tracking cost to operate?

Accepted Answer

The primary cost is cloud hosting for the server-side GTM container. On Google Cloud Run, a site with up to 100,000 monthly visits can typically run server-side GTM for £20–50/month. Higher-traffic sites scale linearly: 500,000 visits/month is approximately £60–150/month. These are running costs; the one-time implementation cost (developer time for setup and configuration) typically ranges from 8–20 hours for a standard implementation, or £800–3,000 if done by an agency. The implementation cost is usually recoverable within the first year if the improved data quality changes even one significant campaign or investment decision.

Question 5

How do I know if server-side tracking is right for my site before committing to the cost?

Accepted Answer

Compare your GA4 conversion counts against a source of truth you trust — CRM lead records, ecommerce order data, or email confirmations sent on form submission. If GA4 is undercounting by more than roughly 15–20% against that source, the gap is large enough that server-side tracking is very likely worth investigating further. If the gap is small (under 10%), the cost and complexity of server-side tracking probably isn't justified yet, and the money is better spent elsewhere until the site's traffic or stakes grow.

Question 6

Who should maintain the server-side container once it's set up?

Accepted Answer

A developer or technical marketer comfortable with GTM and basic cloud infrastructure should own it, since the container needs occasional updates (new tags, GTM platform changes, certificate renewals on the hosting side). It's not a "set and forget" system — budget a few hours per quarter for maintenance and monitoring, and make sure whoever owns it has access to both the GTM account and the cloud hosting console, not just one or the other.