Server-Side & Governance: Recap And Review

5 questions. Answer all of them, then submit; you need 4 of 5 to pass.

1. 1. What changes when you set server_container_url on your Google tag?

   The browser sends its GA4 hits to your tagging server's URL instead of directly to GoogleGTM stops loading in the browser entirelyThe tag downloads its configuration from your server but still sends hits to GoogleIt enables offline mode for the container
2. 2. In a raw /g/collect request, what do en, tid and cid identify?

   The endpoint, the timestamp and the checksumThe event name, the measurement ID and the client IDThe encoding, the tag ID and the container IDThe environment, the trigger ID and the consent ID
3. 3. Inside a server container, what does a client (like the GA4 client) do with an incoming hit?

   It renders the hit in a dashboard for manual reviewIt blocks the hit unless a consent header is presentIt claims the request and parses it into an event data object that the server's tags then consumeIt forwards the raw bytes to every configured vendor unchanged
4. 4. You send a Meta browser pixel and a server-side Conversions API hit for the same purchase. How does Meta avoid counting it twice?

   Meta compares purchase values and drops equal onesCAPI hits always override pixel hits within an hourThe pixel is automatically disabled once CAPI is liveBoth hits carry the same event_id, so Meta deduplicates them into one conversion
5. 5. Two teammates need to build separate changes in the same GTM container without overwriting each other, and mistakes must be reversible. Which features cover this?

   Two separate containers merged by export/import each weekFolders for isolation and Preview mode for rollbackWorkspaces for parallel drafts, and versions so every publish can be rolled backEnvironments, which prevent two users editing at once