Just as everyone got comfortable with the term first-party mode, Google renamed it to Google tag gateway – and plenty of guides still describe the old idea inaccurately. It is a genuinely useful, lighter alternative to a full tagging server. Here is what it actually is now.

What it is

First-party mode, now called Google tag gateway, routes your Google tag requests through your own domain instead of Google's. Rather than the browser loading tags from googletagmanager.com, requests pass through a subfolder on your site, such as yoursite.com/metrics/, served by your CDN, load balancer, or proxy. As of 2026 it is in public beta and available to everyone.

How it differs from server-side GTM

The key distinction is that it needs no tagging server. Google tag gateway simply reroutes the serving of Google's tags through your infrastructure, using a CDN or load balancer you already have. Server-side GTM, by contrast, is a full data pipeline that receives, processes, and forwards data, with all the control and cost that implies. The gateway is lighter and cheaper; the server is more powerful.

What it does and does not do

The trade-off is capability for simplicity:

  • It does make Google tags load from your domain, improving first-party durability and resisting some blocking.
  • It does work for both client-side and server-side Google tags.
  • It does not let you strip PII, block tags conditionally, or run custom pipeline logic the way sGTM can.
  • It works only for Google services like GA4 and Google Ads, not Meta, TikTok, or other vendors.

Who it fits

Google tag gateway suits teams that use mainly GA4 and Google Ads and want better first-party resilience without standing up and maintaining a server. If you also send data to non-Google platforms, or you need real data control, server-side GTM is the right tool – and the two can be combined, with the gateway serving Google's tag library while a server handles routing and processing.

Why the rename happened

The rebrand to Google tag gateway is not just cosmetic; it reflects Google positioning the feature as a mainstream, advertiser-facing way to improve measurement resilience, now open to everyone rather than a niche beta. The old first-party mode name described the mechanism, serving tags as first-party; the gateway name describes the job, a controlled entry point for Google tags on your domain. Guides written before the change often conflate it with server-side tagging, which is exactly the confusion to avoid.

What setup looks like

You do not build a server; you configure your existing edge. In practice that means telling your CDN, load balancer, or proxy to forward a chosen path on your domain to Google's endpoints, then enabling the gateway in your Google tag settings. The heavy lifting is on the infrastructure side you already run, which is precisely why it is lighter to adopt than a tagging server, provided you have that infrastructure and permission to change its routing.

First-party mode did not disappear; it became Google tag gateway, a lighter way to serve Google tags from your own domain through a CDN, no server required. It buys first-party durability cheaply but stops short of the control a tagging server gives, and it covers only Google's own services. Know the new name and its real limits, and you can choose the gateway, the server, or both on purpose rather than by outdated advice.

Want a stronger data analyst role or a raise? Grab the FREE Product Analyst Playbook and get the exact roadmap to your next offer.