AnalyticsWhat is GA4 Server-Side?
GA4 Server-Side sends analytics events through a server-side Google Tag Manager container instead of directly from the browser. The container runs on your own infrastructure, so requests to Google originate server-to-server rather than from the visitor’s device.
Why GA4 Server-Side matters
Server-side tagging is adopted by more mature teams that want first-party cookies, better resilience against ad blockers, and tighter control over what data leaves the browser. It is comparatively rare, which makes it a strong signal of tracking sophistication when you find it on a competitor.
Sites using GA4 Server-Side
A sample of domains in the TagStack index where GA4 Server-Side was detected.
What's usually deployed alongside GA4 Server-Side
Share of indexed containers running GA4 Server-Side that also run each tool. Based on a sample of the index, so treat these as approximate.
Is your GA4 Server-Side set up correctly?
- The server container endpoint is on a first-party subdomain (not the default googletagmanager.com).
- Client-side and server-side GA4 are not both sending the same events — a frequent double-counting bug.
- Consent state is forwarded to the server container, not dropped at the browser boundary.
- The transport URL is healthy and not returning errors that silently lose events.
See GA4 Server-Side on any website
Enter a URL to reveal its full tracking stack — every tag, pixel and consent tool — in seconds. No login or code access required.
Common GA4 Server-Side alternatives
GA4 Server-Side FAQ
TagStack has detected GA4 Server-Side in 34,363 Google Tag Manager containers across its index of 3,278,587 scanned domains. That reflects sites deploying GA4 Server-Side through GTM, so sites that install it directly in their source code are not counted.