Server-side tagging for GA4: what the server container does, what a custom domain adds, what it does not fix

What changes and what does not

In an ordinary set-up the browser sends measurement data directly to each vendor. With server-side tagging the browser sends it to a server container you control, which processes each request with clients, tags and triggers and forwards what you choose. A client claims a request, turns it into events, and tags decide what leaves the server.

Nothing in that design repairs a broken web event. The server forwards what the browser sends. If the web event is missing, mis-named or doubled, the server container will faithfully pass the fault on, so confirm the web events in DebugView first.

• Server-side tagging is a route, not a fix for the event itself.
• Google's pages do not say it changes consent obligations; do not treat it as a substitute for consent choices.

The first-party subdomain

Google's custom domain guide explains the difference. A new tagging server starts on a provider domain, which counts as a third-party context and cannot set server-side cookies. Mapping a subdomain of your site, or a same-origin path, gives you the full benefit. A subdomain needs DNS updates; a same-origin path needs a CDN or load balancer to forward requests.

Google strongly recommends the first-party domain before production traffic. That requires someone who controls your DNS, so settle who that is before anything else.

• Identify who manages DNS for the domain.
• Check the network requests in the browser to confirm they go to your subdomain.

Hosting, cost and preview

Google lists three routes for hosting the tagging server: Cloud Run, App Engine and manual set-up. Its overview page makes no statement about cost, so ask your chosen provider what the server will cost at your traffic and who receives the bill. We do not choose or pay a provider on your behalf.

Server preview shows each incoming request, which client claimed it, which tags fired, and the outgoing request and response. Google notes that several analytics events can be bundled in one request, and that bundling stops if the client-side container is also in preview. Use both views, and count the events in GA4 to check that each action arrives once. Google's server-side pages do not cover DebugView, so set debug_mode to true on the web Google tag for the test and remove the parameter afterwards, because Google says setting it to false does not turn debug mode off; if DebugView stays empty, count the events in an exploration for a unique test marker instead.

• Write down the hosting route, who pays and how to switch it off.
• Check each test action produces one event, not one from the browser and one from the server.

What does not fit, and how the paid outcome is accepted

This does not add Meta or Ads server-side conversions, increase measured conversions or improve ad results; none of those claims is supported here. Without DNS access or a willingness to pay hosting charges, do not start.

The outcome Set up server-side tagging starts from £995 as an untested proposal, quoted after the hosting route and DNS owner are known, with payment only after sign-off. Acceptance: test events appear in server preview as claimed by the GA4 client with an outgoing request and response; each is counted once in GA4, in DebugView with debug mode set for the test or in an exploration for a unique test marker; and the browser's collect requests go to your subdomain, not the provider domain. Send the site address and who manages DNS; no billing details or logins.