How to check server-side tagging from the browser

Updated September 2026 · 3 min read

With server-side tagging, your browser sends data to the configured tagging server endpoint. Verifying this connection from the browser is the first step to ensure your server container receives the events.

How to check the routing in DevTools

1. Open DevTools (F12), go to the Network tab and type collect in the filter.
2. Navigate your site to trigger a Google Analytics™ 4 event.
3. Check that the request URL matches your configured tagging server URL; this may use a custom domain (e.g., metrics.yourdomain.com) or a provider-assigned hostname.
4. Check the path. The request usually maintains the /g/collect path, indicating it is a GA4 payload.

What you can see in the browser

When the browser sends an event to your server container, standard GA4 requests generally use the same encoding as direct browser requests:

• Parameters: You can see the event data included in that request, such as en (event name), tid (measurement ID), and custom parameters (ep. and epn.).
• Consent state: When present, inspect gcs and gcd. Their presence does not prove that all consent types are configured or that server tags respect them; verify the effective state and server tag behavior.
• Batches: GA4 often groups several events in a single POST request body.

What is not visible from the browser

The browser only shows what goes into the server. According to Google’s documentation, you cannot see from DevTools:

• Which tags fire inside the server container.
• What data the server modifies, redacts, or adds before forwarding it.
• The final requests sent from your server to endpoints like Google Analytics, Google Ads, or the Conversions API.

To debug those server-side processes, you can use Preview mode of your server container in Google Tag Manager, as well as the server’s logs and other server tools.