TL;DR
The gateway changes where the Google tag is served from. Instead of the browser fetching it from a Google domain and posting events to a Google domain, both hops go to a path on your own domain, and your infrastructure forwards them on [1]. Google's own announcement attaches an 11% figure to it, and the footnote says that number measures Google tag script loads, not conversions [2]. Google documents setup on your existing CDN, load balancer, or web server [4], with two named in-UI integrations today: Cloudflare [1] and a Google Cloud Global External Application Load Balancer [3]. A Shopify-hosted storefront can use none of them: Shopify serves the storefront HTML itself. Cloudflare documents proxying a Shopify storefront through your own zone, on any plan, via a proxied CNAME [6]. What no page documents is the gateway running over that arrangement. So the practical answer for a Shopify merchant in August 2026 is to watch the partner list and get delivery resilience from the server side instead.
Key Takeaways
- Google tag gateway for advertisers is a delivery change, not a data change. Same tag, same events, different hostname on the wire [1].
- Google documents setup on your existing CDN, load balancer, or web server [4], with two named in-UI integrations today: Cloudflare [1] and a Google Cloud Global External Application Load Balancer [3]. The Cloudflare one is one-click, zone-level, applies to all hostnames on the zone, and free [5]; the Google Cloud one requires routing all of the domain's traffic through the load balancer [3].
- The 11% figure Google publishes is an uplift in signals, measured as Google tag script loads over April 9 to 16, 2025 on a seven-day trailing median [2]. It is not an 11% conversion lift and should never be repeated as one.
- Shopify serves the storefront HTML itself, and no vendor documents the gateway over a proxied Shopify zone [6].
- Google's own Shopify tag documentation routes merchants through the Google & YouTube app, with no gateway step anywhere in it [7].
- The gateway is not server-side tagging. It moves the request path, while a server container or a tracking app changes who sends the event.
- Cloudflare is the launch partner; Google's announcement lists Fastly, Google Cloud CDN and more as planned [2]. Fastly documents its own Ad Tag Gateway integration [8], which is Fastly's documentation rather than a Google-published setup path.
What does the gateway actually change?
A normal Google tag setup makes two cross-origin trips. The browser loads gtag.js from a Google-owned host, then the tag posts measurement hits to another Google-owned host. Both trips are visible to anything that filters by hostname.
The gateway rewrites the first hop and the second. The tag is served from a path on your own domain, and the measurement events are sent to your domain, where your infrastructure forwards them to Google [1]. From the browser's point of view, everything is same-origin. From Google's point of view, the same events arrive with the same parameters.
That is the whole mechanism, and the modesty of it matters when you are budgeting time. Nothing about the payload changes. Google does flag that enabling it affects tag firing behavior and tells consent-mode users to review their consent settings and turn off automated script setup [1]. You are not gaining a new event, a new identifier, or a new match key. You are removing a category of interruption between the tag and the browser.
The name is worth pinning down because half the material online uses an older one. Google's current documentation calls it Google tag gateway for advertisers, and it sits in the tag platform docs as a shipped configuration [1][4]. Articles that still describe it as a beta, or as "first-party mode", are describing the same product under a name Google no longer uses, though some vendor docs still do.
One clarification that saves an argument later: this is a different product from a server-side tagging container, and different again from a vendor CAPI gateway. Our server-side Google Tag Manager explainer covers the container model, and the Meta CAPI Gateway comparison covers Meta's self-hosted middleware, which is a separate piece of software from a different vendor with a different deployment story. The three get blended together constantly. The gateway described here changes the route; the other two change the sender.
The paths Google documents today
Google documents setup on your existing CDN, load balancer, or web server [4], with two named in-UI integrations today: Cloudflare [1] and a Google Cloud Global External Application Load Balancer [3].
| Path | What it requires | Scope |
|---|---|---|
| Cloudflare | The domain on a Cloudflare zone. Enabled with one click, from Google's tag settings or the Cloudflare dashboard [5] | Zone-level. Applies to all hostnames on the zone, and overrides an existing Google Tag Manager script [5] |
| Google Cloud | A Global External Application Load Balancer, not the classic Application Load Balancer [3] | All traffic for the domain must route through the load balancer [3] |
Both are infrastructure work at the edge of your domain, which is the detail that decides everything below. Neither is a tag setting, a plugin, or a snippet you paste into a theme. The Cloudflare route is free and takes a minute if you already run the domain through Cloudflare [5]. The Google Cloud route is a load balancer you operate.
Google's announcement names Cloudflare as the launch partner and lists Fastly, Google Cloud CDN and more as planned [2]. Fastly documents its own Ad Tag Gateway integration [8], which is Fastly's documentation rather than a Google-published setup path.
About that 11% figure
Google's announcement page carries an 11% number, and it comes with a footnote most write-ups drop [2]. The footnote says the measurement is an uplift in signals, that signals here means Google tag script loads, that the window was April 9 to 16, 2025, and that the statistic is a seven-day trailing median [2].
Script loads. Not conversions, not revenue, not attributed sales. The gateway makes the tag more likely to load and its hits more likely to arrive, and 11% is Google's measurement of that first thing across whatever set of sites it observed.
Whether more script loads become more reported conversions on your account depends on what was blocking them and on what those blocked sessions would have done. A visitor who blocks the Google tag and then buys is a real recovered conversion. A visitor whose tag load failed on a bounce page is a recovered script load and nothing more. Google has published no conversion-level figure for the gateway, and anyone quoting "11% more conversions" has invented the second half of that sentence.
Can a standard Shopify store deploy it?
Here is where a straightforward feature meets a platform that is built the other way around, and the answer as of today is no, for reasons that stack.
Start with the Cloudflare path. It needs your domain proxied through Cloudflare so the edge can serve the tag and receive the events. On a Shopify-hosted store, the storefront HTML is served by Shopify's own infrastructure, not by an origin of yours. Cloudflare documents proxying a Shopify storefront through your own zone, on any plan, via a proxied CNAME [6]. What no page documents is the gateway running over that arrangement.
The proxied arrangement also carries a carve-out. Cloudflare's provider guide for Shopify states plainly that Workers and Snippets are disabled on the /checkout URI path [6]. Checkout is where the purchase happens, and any edge feature that stops at the checkout boundary stops exactly where the conversion lives. Cloudflare does not document which mechanism serves the gateway, so whether that carve-out reaches it is unstated [5][6]. What is documented is that Workers and Snippets stop at /checkout.
Nobody documents the combination. No Google page and no Shopify page describes a supported tag gateway setup for a Shopify-hosted storefront. Google's own guide for putting the Google tag on Shopify routes merchants through the Google & YouTube app and never mentions the gateway [7]. That absence is not proof that a determined merchant cannot make something work at the edge; it is proof that if it breaks, there is no documented configuration to point at, on either vendor's side.
The Google Cloud path is structurally out. It requires all traffic for the domain to pass through a load balancer you run [3]. On a Shopify-hosted store, the traffic terminates at Shopify. There is no origin to place behind a load balancer, so the path does not apply rather than merely being difficult.
If you run a headless storefront on your own infrastructure, most of this reasoning does not bind you, and the Cloudflare or Google Cloud paths are ordinary edge work. This article is about the standard Shopify-hosted case, which is the one most merchants asking the question are actually in.
What would have to change
Two things, and they are independent.
The first is the partner list. Google says more CDN partners are planned [2], and a partner whose product sits in front of a Shopify storefront in a way Shopify supports would change the calculation immediately.
The second is documentation from either vendor. Shopify has shipped checkout on the merchant's own domain, and edge configurations around Shopify domains keep evolving. What is missing right now is a page from Google or Shopify saying "here is the supported way", and that page is what turns this from a maybe into a task.
You have probably had the experience of finding a vendor tutorial for a combination neither vendor supports, following it, and discovering six weeks later which half broke. That is the shape of the risk here.
What Shopify merchants can do for delivery resilience now
The gateway is one answer to a specific problem: browser requests to advertising and analytics hosts get blocked, filtered, or dropped. On Shopify, the available answer to that same problem is to stop depending on the browser for the events that matter.
Server-side delivery moves the purchase off the browser entirely. The order webhook fires from Shopify's servers when the order is created, and the conversion is sent from a server to the platform's API. No script load, no cookie hop, no extension in the way. Our ad blocker and conversion tracking piece walks through what each blocking layer actually stops, and the server-side tracking overview covers how the pieces fit for GA4, Meta, TikTok and Google Ads.
WeltPixel Conversion Tracking works this way by design. The purchase is server-only, sent from Shopify's orders/create webhook, so it does not depend on the buyer's browser surviving checkout. When the browser-side capture of an ad click ID is blocked, the app recovers the click ID from the order's landing URL and fills that gap, without touching a value the browser did capture. Plans are a free plan that covers GA4 tracking for up to 100 storefront orders a month, and $39/mo for Plus, which covers the other eight integrations.
Nothing there is a substitute for the gateway on the pages the gateway would cover, and it is worth being straight about that: browse events on a store with heavy blocking will still be thinner than the same store's order count implies. The purchase, which is the number your bidding runs on, is the part that is already off the browser.
FAQ
Is Google tag gateway for advertisers available on Shopify?
Not on a standard Shopify-hosted storefront, as of August 24, 2026. Google documents setup on your existing CDN, load balancer, or web server [4], with two named in-UI integrations today: Cloudflare [1] and a Google Cloud Global External Application Load Balancer [3]. The documented paths all need infrastructure in front of your domain that can route a reserved path to Google [3][4], and Shopify serves the storefront HTML itself. No Google or Shopify page documents a supported setup for this combination.
Is the gateway the same as server-side tagging?
No. The gateway changes where the Google tag and its hits are served from on the network [1]. Server-side tagging changes which machine builds and sends the event. You can run one without the other, and they solve overlapping but different problems.
Does the 11% figure mean 11% more conversions?
No. Google's footnote defines it as an uplift in signals, measured as Google tag script loads, over April 9 to 16, 2025, on a seven-day trailing median [2]. Google publishes no conversion-level figure for the gateway.
Is it still in beta?
No. Google documents it as a shipped configuration under the name Google tag gateway for advertisers [1][4]. Material calling it a beta, or calling it first-party mode, predates the current documentation.
Can I set it up through Cloudflare on my Shopify domain anyway?
Cloudflare documents proxying a Shopify storefront through your own zone, on any plan, via a proxied CNAME [6]. What no page documents is the gateway running over that arrangement. The same guide disables Workers and Snippets on the /checkout path [6], and Cloudflare does not document which mechanism serves the gateway, so whether that carve-out reaches it is unstated [5][6]. What is documented is that Workers and Snippets stop at /checkout, which is where your purchase event lives. Nobody documents this combination as supported, so treat any tutorial claiming otherwise as untested.
If you want conversions delivered from the server rather than the browser while the gateway story on Shopify is still unwritten, install WeltPixel Conversion Tracking, connect your platforms, and compare a week of platform-reported purchases against your Shopify order count.
Sources
- Google Analytics Help, Set up Google tag gateway for advertisers in the Google tag with Cloudflare, support.google.com/analytics/answer/16061406, accessed August 24, 2026
- Google Ads Help, Google tag gateway for advertisers announcement and 11% signals footnote, support.google.com/google-ads/answer/16214371, accessed August 24, 2026
- Google Analytics Help, Set up Google tag gateway with Google Cloud, support.google.com/analytics/answer/16816376, accessed August 24, 2026
- Google Tag Platform developer documentation, Google tag gateway, developers.google.com/tag-platform/tag-manager/gateway, accessed August 24, 2026
- Cloudflare Docs, Google tag gateway, developers.cloudflare.com/google-tag-gateway/, accessed August 24, 2026
- Cloudflare Docs, Cloudflare for SaaS provider guide: Shopify, developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/shopify/, accessed August 24, 2026
- Google Analytics Help, Set up the Google tag on Shopify, support.google.com/analytics/answer/12183125, accessed August 24, 2026
- Fastly documentation, Fastly Ad Tag Gateway, https://www.fastly.com/documentation/guides/integrations/non-fastly-services/fastly-ad-tag-gateway/, accessed August 24, 2026