Skip to content
Tracking SOP

Google Tag Gateway

A simpler, complementary piece — distinct from full server-side GTM — routing the existing client-side container’s own script loading through your domain via Cloudflare.

Setup

  1. 1.GTM → Admin → Google Tag Gateway.
  2. 2.Choose a Measurement Path — Google’s default is a random 4-character path (deliberately obscure, harder for ad blockers to pattern-match) — accept the default unless there’s a specific reason to customize.
  3. 3.Sign into Cloudflare, authorize (this integration does not create new visible DNS records/Workers/Page Rules — it uses an internal Cloudflare-Google integration layer, confirmed via Cloudflare’s own technical blog describing this exact mechanism).
  4. 4.Select the specific domain(s) to enable — deliberately scope this to production/client-facing domains only, not internal tools like a CRM subdomain with no tracking value.
  5. 5.Save, complete setup.
  6. 6.Status will show "Pending" immediately — expected; flips to "Active"/"First-party" once real traffic passes through the new path. Don’t chase an instant status change.
  7. 7.Verify via Tag Assistant: Summary → Output → Hits Sent tab — confirm hits route through the site’s own domain rather than directly to googletagmanager.com.