← Back to Blog

The Three Ways to Deploy Google Tag Gateway — and Which Fits Your Stack

Quick Answer: There are 3 ways to deploy Google Tag Gateway: with a CDN such as Cloudflare, Fastly, or Akamai, with server-side tagging through a tagging server and custom domain, or via manual self-service setup. Google recommends CDN plus server-side for the most durable first-party configuration. A Google Cloud one-click path was added in 2026. The server-side route configures 2 paths — a collection path for events and a script path for first-party script serving. CDN options have limits: Fastly and Akamai support only 1 Google tag per setup, and Akamai caps at 100 domains.

What are the main ways to deploy Google Tag Gateway?

There are 3 ways: with a CDN, with server-side tagging, or via manual self-service, and Google recommends CDN plus server-side for the most durable setup (Google for Developers, 2026). Each method serves the same purpose — routing Google’s measurement scripts and event collection through your own domain — but they differ sharply in complexity, control, and what you need in place before you start.

The CDN path puts a proxy in front of Google’s tag infrastructure using your existing content delivery network. Cloudflare, Fastly, and Akamai all have automated integrations. The server-side path runs a tagging server you control, giving you full ownership of the event pipeline. The manual path is self-service configuration where you update script references yourself. Google’s recommendation — CDN plus server-side together — gives you first-party script serving and first-party event collection in one setup, which is the most resistant to ad blockers and browser privacy restrictions.

The choice isn’t about which is “best.” It’s about which matches what you already have. A store on Cloudflare can be up in minutes. A store with a DevOps team and specific data residency requirements needs server-side. A store with neither has a different path entirely.

There are 3 ways to deploy Google Tag Gateway: CDN, server-side tagging, or manual self-service, and Google recommends CDN plus server-side for durability (Google for Developers, 2026).

Which CDN deployment is easiest?

Automated integrations exist for Cloudflare, Fastly, and Akamai, with a Google Cloud one-click path added in 2026 (Search Engine Land, 2026). For most WooCommerce stores, Cloudflare is the fastest route — its Worker-based integration configures the gateway without touching your origin server, and the free tier handles the proxy traffic.

The Google Cloud deployment, launched in 2026, is the newest option. It’s a one-click setup inside GCP that provisions the gateway infrastructure automatically. If your hosting or analytics stack already runs on Google Cloud, this path avoids adding another vendor. For everyone else, the CDN you already use is the path of least resistance.

Fastly and Akamai integrations are available but come with constraints. Both support only 1 Google tag configuration per setup (Tag Manager Help, 2026), which means stores running multiple Google tags — a common setup when GA4 and Google Ads use separate measurement IDs — either need to consolidate or choose a different deployment method for the additional tags.

Related: Google Tag Gateway vs Server-Side GTM: which one does your WooCommerce store need?

What does the server-side deployment require?

It needs a server container, a tagging server, and a configured custom server domain before you load Google scripts first-party (Google for Developers, 2026). This is the most involved path, and it’s the one that gives you the most control. You own the server. You own the domain. You control what happens to events before they reach Google.

In practice, that means provisioning a GTM server-side container (typically on Google Cloud Run or App Engine), pointing a subdomain to it (something like data.yourstore.com), and configuring the gateway to route through that subdomain. The tagging server then acts as both a proxy for Google’s scripts and a relay for event data — all from your first-party domain.

The upside is durability and enrichment. Because events pass through your server, you can validate, transform, and enrich them before forwarding to Google — adding server-side customer data, stripping PII, or deduplicating conversions. The downside is operational: you now own a piece of infrastructure that needs monitoring, scaling, and maintenance. For stores without a DevOps team, that ongoing cost is the real barrier — not the initial setup.

What two paths does the server-side setup configure?

It configures 2 paths: a collection path that forwards events to your tagging server and a script path that serves first-party scripts (Google for Developers, 2026). These two paths are the core of what makes Tag Gateway work at the infrastructure level, and understanding them explains why the setup is more complex than the CDN route.

The script path replaces Google’s default script domain (googletagmanager.com) with your own. When a browser loads your page, it requests the Google tag JavaScript from data.yourstore.com instead of from Google. This makes the script a first-party resource — same domain as the page — which means ad blockers that target third-party script domains don’t block it.

The collection path handles the data flowing back. When a user triggers an event — a page view, a purchase, a form submission — the browser sends the event data to your collection endpoint, not to Google’s. Your tagging server receives it, processes it, and forwards it to Google’s measurement endpoints. The browser never talks to Google directly, which is why this setup survives privacy restrictions that block third-party requests.

Server-side Tag Gateway configures 2 paths: a collection path that forwards events to your tagging server and a script path that serves first-party scripts (Google for Developers, 2026).

Related: What is Google Tag Gateway for WooCommerce?

When must I manually re-tag my site?

With guided or self-service setup you must manually replace each Google tag script source with your new measurement path (Google Ads Help, 2026). This applies when you’re not using a CDN integration that handles the rewrite automatically. You find every instance of the Google tag snippet in your site — header scripts, plugin settings, hardcoded embeds — and change the script source URL from Google’s domain to your gateway domain.

For WooCommerce stores, this typically means updating the script source in your tracking plugin’s settings, your theme’s header.php or functions.php, and any manual script injections added through plugins like Insert Headers and Footers. Miss one, and that tag still loads from Google’s third-party domain — visible to ad blockers and subject to browser privacy restrictions.

The CDN integrations avoid this entirely because they intercept the request at the network level. Cloudflare’s Worker rewrites the domain transparently; the browser requests Google’s default URL, and Cloudflare serves it from your domain. No code changes needed. That’s why the CDN path is faster — it doesn’t require touching your site’s markup at all.

Does any CDN option limit the number of tags?

Yes — Tag Gateway on Fastly and Akamai supports only 1 Google tag configuration per setup (Tag Manager Help, 2026). If your site uses multiple Google tags — a GA4 measurement ID and a separate Google Ads conversion tag, for instance — only one can run through the gateway. The other still loads from Google’s third-party domain, which defeats the purpose for that tag.

Cloudflare’s integration doesn’t have the same per-tag limitation, which is one reason it’s the more practical choice for stores with multiple measurement endpoints. The Google Cloud deployment also handles multiple tags, though it requires GCP infrastructure.

The workaround for Fastly and Akamai is tag consolidation. If you can route all your measurement through a single Google tag (using the Google tag’s built-in destination linking), the one-tag limit doesn’t matter. But consolidation isn’t always possible — some setups legitimately need separate tags for separate Google products — and in those cases, Fastly and Akamai aren’t the right gateway deployment.

LIFETIME LOCK on Harvest Annual Plan

Push your WordPress event data server-side seamlessly into BigQuery so AI can analyse it.

Let's Do It !

Is there a cap on domains in one setup?

On Akamai, selecting more than 100 domains triggers an error and disables the complete-setup button (Tag Manager Help, 2026). Most WooCommerce stores won’t hit this limit — a single-domain store or a store with a handful of country-specific subdomains is well within range. But enterprise deployments with extensive subdomain structures or multi-brand portfolios could run into it.

The 100-domain cap is specific to Akamai’s Tag Gateway integration. Cloudflare and Fastly don’t document the same restriction. For a WooCommerce store running a single domain with a www and non-www variant, this limit is irrelevant. For an agency managing dozens of client domains through a single Akamai property, it’s a planning constraint that determines how many separate gateway configurations you need.

CDNTags per SetupDomain CapBest For
CloudflareMultipleNot documentedMost WooCommerce stores — free tier, no tag limit
Google CloudMultipleNot documentedStores already on GCP — one-click deploy
Fastly1Not documentedEnterprise sites already on Fastly
Akamai1100Enterprise sites already on Akamai
Tag Gateway on Fastly and Akamai supports only 1 Google tag configuration per setup, limiting multi-tag deployments (Tag Manager Help, 2026).

Which path fits a store with no infrastructure team?

A CDN integration such as Cloudflare or a managed tracking layer fits teams without infrastructure skills, while server-side suits those who need full control (Google for Developers, 2026). The CDN route automates the heavy lifting — no server provisioning, no container management, no custom domain DNS. For WooCommerce stores without a DevOps team, it’s the practical starting point.

But Tag Gateway — even via CDN — still only proxies Google’s scripts and collection. It makes your existing client-side tags first-party. It doesn’t add server-side event processing, conversion enrichment, or data warehousing. If what you need is first-party script serving and nothing else, Tag Gateway through Cloudflare is the right fit.

If you need the data layer that sits behind first-party serving — server-side event routing to GA4, Google Ads, and BigQuery, conversion deduplication, and event enrichment — that’s a different infrastructure requirement. Tools like Transmute Engine provide managed server-side tracking for WooCommerce that handles the event pipeline end-to-end, from your store’s backend to every measurement destination, without requiring you to provision or maintain tagging servers. That’s the managed route for stores that want first-party serving plus enrichment without owning the infrastructure.

Related: Google Tag Gateway vs Server-Side GTM for WooCommerce — one simplifies, one controls

LIFETIME LOCK on Harvest Annual Plan

Push your WordPress event data server-side seamlessly into BigQuery so AI can analyse it.

Start NOW !

Key Takeaways

  • 3 deployment paths: CDN (Cloudflare, Fastly, Akamai, Google Cloud), server-side tagging, or manual self-service — Google recommends combining CDN and server-side.
  • CDN is fastest: Cloudflare’s integration works without touching your site’s code and has no per-tag limit.
  • Server-side gives control: 2 configured paths — collection and script — let you enrich events and own the infrastructure.
  • Watch the limits: Fastly and Akamai support only 1 Google tag per setup; Akamai caps at 100 domains.
  • No DevOps team? Start with a CDN integration or a managed tracking layer that handles first-party serving for you.
What are the main ways to deploy Google Tag Gateway?

There are 3 ways: with a CDN such as Cloudflare, Fastly, or Akamai, with server-side tagging through a tagging server, or via manual self-service. Google recommends combining CDN and server-side for the most durable first-party setup. Each method serves Google scripts from your own domain rather than from Google’s.

Which CDN deployment is easiest?

Automated integrations exist for Cloudflare, Fastly, and Akamai, with a Google Cloud one-click path added in 2026. Cloudflare’s integration is the most accessible for stores already on the Cloudflare network — it configures the gateway through Cloudflare Workers without touching your server.

What does the server-side deployment require?

It needs a server container, a tagging server, and a configured custom server domain before you can load Google scripts first-party. This is the most involved setup but gives the most control — you own the infrastructure and can enrich events before they reach Google’s endpoints.

What two paths does the server-side setup configure?

It configures a collection path that forwards events to your tagging server and a script path that serves first-party scripts. The collection path handles outbound measurement data. The script path serves Google’s tag JavaScript from your domain, making it resistant to ad blockers.

When must I manually re-tag my site?

With guided or self-service setup you must manually replace each Google tag script source with your new measurement path. This means finding every instance of the Google tag snippet across your site and updating the script source URL to point to your gateway domain.

Does any CDN option limit the number of tags?

Yes. Tag Gateway on Fastly and Akamai supports only 1 Google tag configuration per setup. If your site uses multiple Google tags — for example, separate GA4 and Google Ads tags — you’ll need to consolidate them or choose a different deployment method.

Is there a cap on domains in one setup?

On Akamai, selecting more than 100 domains triggers an error and disables the complete-setup button. Stores with fewer domains won’t hit this limit, but enterprise deployments with many subdomains may need to split their configuration across multiple setups.

Which path fits a store with no infrastructure team?

A CDN integration such as Cloudflare or a managed tracking layer fits teams without infrastructure skills, while server-side suits those who need full control. The CDN route automates the heavy lifting — no server provisioning, no container management, no custom domain DNS.

References

  1. Google for Developers (2026). Google tag gateway for advertisers. Source
  2. Search Engine Land (2026). Google rolls out Tag Gateway via Google Cloud. Source
  3. Google for Developers (2026). Tag gateway: load Google scripts first-party. Source
  4. Google Ads Help (2026). Set up Google tag gateway in the Google tag with Cloudflare. Source
  5. Tag Manager Help (2026). Set up Google tag gateway with Fastly. Source
  6. Tag Manager Help (2026). Set up Google tag gateway using Akamai. Source