Tracking

Google Tag Gateway

Loading the Google tag through your own domain

In short

Google tag gateway lets you load the Google tag through your own domain and send measurement data to Google through it, instead of directly to Google domains. This makes measurement more resilient to signal loss.

Also known as: Google tag gateway for advertisers

Google tag gateway (full name: Google tag gateway for advertisers, formerly "first-party mode") loads the Google tag through your own domain and forwards measurement data to Google through it. To the browser, this looks like a request to your website, not to a Google domain.

How it works

Instead of googletagmanager.com, your page calls a path on your own domain, for example /metrics/. Your CDN or load balancer forwards these requests to Google. According to Google, this helps reduce signal loss and improve measurement (Google Tag Manager Help).

You can set it up directly in the Google tag with Cloudflare, or follow guides for other CDNs such as Akamai, Fastly or Amazon CloudFront.

What Google says

Google calls tag gateway a building block of data strength. In Google's own analyses, advertisers using it see 14% more measured conversions on average, and over 20% in Demand Gen campaigns. These are vendor figures, and they refer to measured conversions, not additional sales.

In lead generation

Tag gateway only affects what happens in the browser, such as a form submission. Deals that close later in the CRM reach Google through offline conversions or enhanced conversions for leads.

Common mistakes

  • Forgetting consent: tag gateway doesn't change your consent obligations.
  • Leaving old tag scripts in place: with a manual setup, the old script sources must be replaced on every page.
  • Confusing more measurement with more revenue: more measured conversions doesn't mean more customers.

Ready for better tracking?

Try LeadMetrics free for 10 days and see which campaigns actually drive revenue.
Start a 10 day trial

Frequently asked questions

No. Tag gateway only changes which domain the tag is loaded from. Consent obligations stay the same, and Google explicitly recommends using Consent Mode and reviewing your consent settings.

Articles on this topic

Related terms

All terms

First-Party Cookies

First-party cookies are set by the domain you are currently visiting. They store things like logins, shopping carts or tracking IDs for that same website.

Server-Side Tracking

Server-side tracking sends tracking data to ad and analytics platforms from a server instead of the browser – more robust and under your control.

Consent Mode · Consent signals for Google tags

Google Consent Mode passes the consent from your cookie banner to Google tags and Google Ads, so they know which data they may use for measurement and advertising.

Enhanced Conversions · Matching Google Ads conversions with hashed customer data

Enhanced conversions add hashed customer data such as email or phone number to Google Ads conversions, so Google can attribute them to an ad even without a cookie or gclid.

Data Strength · Google's measure for the quality of your first-party data

Data strength is Google's term for how complete and well connected an advertiser's own data is when it reaches Google Ads: tagging, CRM data, customer data and click IDs.

Client-Side Tracking

Client-side tracking captures user actions with JavaScript directly in the browser and sends them from there to analytics and ad platforms.