Google Tag Gateway

Google Tag Gateway, or GTG, lets you serve Google tags from your own domain instead of serving them directly from Google. This improve measurements by reducing the impact of ad blockers and similar technologies.

How it works

When Google Tag Gateway is active, requests are routed trough a "Tag serving path" on your own website (e.g. yoursite.com/measurements/) instead of loading them from googletagmanager.com, google-analytics.com etc. 

GTG works through your existing Content Delivery Network (CDN), load balancer, or web server. Some CDNs (like Cloudflare) offer a one-click automated setup. Please see Googles set up guide for information on how to setup Google Tag Gateway.

When using a one-click setup, be aware that this often prevents your control over the script loading order. This could cause Google tags to load before the CookieTractor-script resulting in a late consent signal. See our troubleshooting guide about late consent for details.

Implementors should also be aware that the proxy to Google servers will forward the request, including IP address meaning that this process is not equivalent to anonymization - it's a way to improve measurements.

Setup Google Tag Gateway