AnalyticsIs your GA4 Server-Side set up correctly?
Enter your website URL and TagStack scans the live page to verify your GA4 Server-Side implementation — duplicates, missing events, and consent problems — in seconds. Free, no login or code access needed.
GA4 Server-Side detected in 34,363 GTM containers in our index — and a large share have at least one setup issue.
What the GA4 Server-Side check looks for
- 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.
About 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.
Learn more about GA4 Server-SideCheck other tools
GA4 Server-Side setup FAQ
It can be — you control what leaves the browser and can strip identifiers before forwarding to Google — but only if consent is honoured server-side too. TagStack shows whether your server-side setup still respects the visitor’s consent choice.