Server-side tagging for GA4: is it worth it?

How it works

1. The browser sends one stream of events to your tagging server, for example at metrics.yoursite.com, instead of to each vendor.
2. The server container receives the request with a client (the GA4 client is built in), turns it into event data, and runs server-side tags.
3. Each tag forwards only what you allow to its vendor: GA4, Google Ads, Meta's Conversions API and so on. You can strip IP addresses, drop parameters or block a vendor entirely.

What it improves

• Control over data sharing. Vendors receive what your server sends, not whatever their script can read in the browser.
• Cookie lifetime. Safari caps cookies written by JavaScript at seven days. Cookies set by your own server in an HTTP response, from a subdomain that resolves to your own infrastructure, can last longer, so returning visitors are recognised more often.
• Page weight. Several vendor scripts can be replaced by one lightweight stream, which helps Core Web Vitals on tag-heavy sites.
• Ad blockers. A first-party endpoint is blocked less often than google-analytics.com. Treat this as a side effect, not a goal: a visitor who blocks tracking has expressed a preference.

What it does not change

Consent. Moving a tag to a server does not make tracking lawful without consent where consent is required. The consent signals still have to travel with each event and the server tags still have to honour them. Regulators look at what data reaches whom, not where the code runs.

Costs and effort

• Hosting. Google's automatic provisioning deploys to Cloud Run on Google Cloud, billed by usage; Google's documentation recommends multiple instances for production so the server does not drop events. Managed hosts for server GTM also exist and charge by request volume.
• Set-up. A custom subdomain with DNS records, the server container, the web container changed to send to it, and each vendor tag rebuilt server-side.
• Upkeep. Someone has to watch error rates, update the container and keep vendor tags current.

Who should do it

Worth it: sites with significant ad spend where better conversion data moves bidding, sites with many vendor tags, and sites with strict data-sharing requirements. Not yet worth it: a small business site with GA4 and one ads tag. Fix the basics first: clean event tracking, consent and lead quality data matter more than cookie lifetime.

Where to host

Cloud Run is Google's default. Any host that can run the server container image works. If you would rather run it on a managed virtual server you already pay for, check that the plan can run Docker containers and that you can add a TLS certificate for the subdomain.