Don't have one? Create one ↗
Server-side tagging

Lesson 8 of 8

Testing & Going Live

Server-side has its own debugging surface, and a few habits keep a migration from quietly losing data.

How to test

  • Use the server container's Preview, it shows each incoming request, which client claimed it, the event data object, and which tags fired.
  • Confirm the destination actually received the event (GA4 DebugView, Meta Events Manager "Test events").
  • Check the response sets the expected first-party cookie.
  • Watch for events that arrive but are claimed by no client, the usual sign of a misconfigured client or URL.

Rolling out safely

  • Run server-side alongside the existing client-side setup first; compare totals before cutting over.
  • Expect a modest increase in recorded conversions (recovered from blockers/ITP), not a drop. A drop means something is misrouted.
  • Mind cost: Cloud Run scales with traffic, so load-test high-traffic events.

Key takeaway

Debug in the server container's Preview, confirm receipt at each destination, and roll out in parallel with client-side so you can compare before cutting over. Recovered data should nudge numbers up, not down.