Is Google Tag Gateway actually running on your site?
Enter your domain. We load it in a real browser and watch where your Google tags are served from — your own domain or Google's — and tell you whether that's Tag Gateway, a server-side container, or neither.
Free · no login · we load your site in a real browser and record what fires before consent.
Most checkers read the page. Ours watches it.
- Tag Gateway and server-side GTM both serve tags from your own domain, so a first-party host alone can't tell them apart. We resolve the host: a tagging server CNAMEs to Stape, Addingwell, TAGGRS or Cloud Run — Tag Gateway is a reverse proxy on your own CDN and does not.
- We record whether googletagmanager.com is still contacted. Under Tag Gateway it is — that health check is expected, and its absence usually means something else is going on.
- They are not alternatives, and Google's own documentation recommends running both. We show you which you have so you can tell whether you're missing half the setup.
- We report what we observed, not vendor uplift claims. The conversion-recovery figures in circulation trace back to Google's own marketing and have no independent audit behind them.
- Same scan also reports what fires before consent — because moving tags to your own domain does nothing about consent, and first-party delivery of a tag that shouldn't have fired yet is still a leak.
Tag Gateway is a reverse proxy: your CDN serves Google's tag from your domain, and the request is forwarded to Google. There's no container you control and no transformation of the payload. Server-side GTM is a tagging server you run — your own container, where you can reshape, enrich or withhold data before anything reaches a vendor. Tag Gateway is free and takes minutes; sGTM is infrastructure you pay for and maintain. They solve different problems, which is why Google recommends both.
Not reliably. First-party delivery avoids blocklists that match on Google's hostnames, but blockers that match on request paths or script contents still catch it — Ghostery still blocks Google Analytics through Tag Gateway. Treat it as a signal-quality improvement, not an ad-blocker bypass.
No, and it's worth being blunt about this. Tag Gateway changes where a tag is served from, not whether it was allowed to fire. If your tags currently run before consent, they'll keep running before consent — from your own domain. Consent enforcement is a separate job, which is why this scan reports both.
Google's own — GA4, Google Ads, Google Tag Manager and Campaign Manager 360. Third-party pixels like Meta, TikTok or LinkedIn are out of scope for Tag Gateway entirely. If you need those served first-party, that's a server-side GTM job.
Found something you don't like?
We fix exactly this — consent enforcement, Consent Mode v2, and server-side tracking. Book a call or start with a scan.