Google tag gateway for advertisers

Google tag gateway for advertisers allows website owners using Cloudflare as a CDN to get the most out of ad measurement tools with just a few clicks. It allows you to deploy Google scripts using your own domain, enhancing data privacy and improving signal measurement recovery. Unlike standard setups where tags are requested from a Google domain, Google tag gateway for advertisers loads the tag from your domain and sends measurement events to your domain, where they are forwarded to Google.

Learn more about why we built it and how it works in our blog post .

Google tag gateway for advertisers is free to use. Requests routed through the gateway do not count toward usage or billing for other Cloudflare products such as CDN, WAF, or Bot Management.

Site owners can enable this feature in one of two ways: through the Google tag console, or through the Cloudflare dashboard .

The fastest way to set up Google tag gateway for advertisers is in Google Tag Manager. Follow the steps in Google's Help Center .

1. In the Cloudflare dashboard, go to the Google Tag Gateway page.

   Go to Google Tag Gateway ↗

2. Select your domain.

3. Enable the toggle for Turn on and configure Google tag gateway.

4. Add your Google tag ID and the path on your website reserved for the Google tag. The Google tag ID can be found in the Google Tag Experience dashboard. The measurement path is an unused path on your site that will load Google Tag Manager and all subsequent measurement requests.

5. Once you click Save, Google tag gateway for advertisers will be enabled on your zone. If you already have a GTM script on your website, this First Party Tag will override the existing script.

Now that you have authenticated into your Cloudflare account and configured GTM in first-party mode, your Google Tags will be loaded using https://your-domain/measurement-path/...and subsequent measurement requests will be served by Cloudflare.

Google tag gateway for advertisers is configured at the zone level. When you enable it for a zone (for example, example.com), it applies to all hostnames and subdomains within that zone, including custom hostnames. Currently, it is not possible to enable or disable the feature for individual subdomains independently. Configuration Rules cannot be used to control or disable the tag injection on specific subdomains.

If you need different tag behavior for specific subdomains (for example, only firing certain tags on shop.example.com), you can use Google Tag Manager triggers to control when tags fire. For example, you can create a trigger condition like Page Hostname equals shop.example.com to restrict a tag to a specific subdomain.

This approach lets you maintain a single zone-wide Google tag gateway configuration while still customizing tag behavior per subdomain.

• Google Developer Docs: Set up Google tag gateway for advertisers
• Google Help Center: Set up Google tag gateway for advertisers in the Google tag with Cloudflare
• Google Help Center: Set up Google tag gateway for advertisers in Google Tag Manager with Cloudflare