Server-side GTM hosting: Cloud Run, a managed host or Google tag gateway, and who maintains what.
- “where to host server-side GTM”
- “server-side GTM hosting options”
- “Cloud Run vs Stape server-side GTM”
- “Stape vs Google Cloud server-side tagging”
- “managed server-side GTM hosting”
- “who maintains a server-side GTM container”
- “how to update the server-side GTM tagging server”
- “tag gateway instead of a server container”
- “do I need Google Cloud for server-side tagging”
- “move server-side GTM from Cloud Run to Stape”
Baris Asa, tracking consultant, London · Last checked: November 2026
Run server-side GTM on Cloud Run if someone already looks after your Google Cloud, and on a managed host such as Stape or Addingwell if nobody does. On Cloud Run you own the updates, the capacity, the logs and the bill; on a managed host the host runs the servers, and you still own the tags and the domain. Google tag gateway is not a place to run it: it serves Google’s tags from your domain and sends nothing to Meta.So if Meta purchases are what you are missing, tag gateway alone won’t bring them back. Pick the route by one question: when it breaks on a sale day, who answers, and do they have the access to fix it?
Not sure what you have now? In Tag Manager, open the server container, then Admin, Container Settings, and read the server container URL. Then ask who gets the bill for it:
- an address ending
run.app, or a Google Cloud invoice: Cloud Run; - a Stape, Addingwell or similar invoice: a managed host;
- no server container at all: the Google tag in the browser, perhaps with tag gateway on your CDN.
Seeing errors now (Preview empty, purchases missing, failures on busy days)? Start with Server-side GTM errors. This page is about where it runs and who keeps it running.
I have no partnership, affiliate or commission arrangement with any host or CDN on this page.
Which route fits?
- A managed host fits most brands that want server-side GTM, for Meta’s Conversions API or to control what each platform receives, with nobody on the team who looks after cloud servers.
- Cloud Run fits if someone already runs your Google Cloud, or your policy says data and billing stay in your own project. Tag Manager can set it up for you (Google: Cloud Run set-up).
- Your own servers fit only if you have an infrastructure team. Google’s manual set-up guide covers it.
- Google tag gateway alone fits if you need nothing sent from a server (no Meta Conversions API, no filtering of what each platform receives) and want Google’s tags loaded from your own domain. It is a setting on your CDN (the service in front of your site, such as Cloudflare) or load balancer. For server-side set-ups, Google recommends doing both: a custom domain for the server, and Google’s scripts loaded through tag gateway (Google: tag gateway).
Not sure you need server-side tagging at all? Start with You don’t need server-side tracking (yet).
Who maintains what on each route?
| Job | Cloud Run | Managed host | Tag gateway |
|---|---|---|---|
| Server updates | You | The host | None to do |
| Capacity at peak | You | The host | Your CDN |
| Domain record | You | You add the host’s record | Your CDN setting |
| Logs | You, in Google Cloud | The host’s tools | Your CDN’s |
| Tags and triggers | You | You | Your web container, in the browser |
| Consent | You | You | Your Consent Mode set-up |
| The bill | Your Google Cloud account | The host’s plan | Your CDN plan |
“You” means whoever you hire or employ for it. The row people miss: on every server-side route, the container is still yours. A host keeps the servers running. It does not check that your Meta tag fires on the right event, or only for visitors who agreed to advertising cookies (F-201 , and Consent Mode v2 with server-side GTM).
The container also moves with you. Changing host later means a new tagging server and a new DNS record, not a rebuild; the steps are in the questions at the end.
Cloud Run: what someone on your side must do
If you choose Cloud Run, these five jobs sit with you. If nobody can own them, pick a managed host. All five are from Google’s Cloud Run guide unless linked.
- Update the server. Deploy a new revision with the
stableimage, at least for each major release. Google says updates carry security fixes and new features. Check afterwards in Preview, on the Console tab. - Set capacity. Instances are copies of the server running at once. Google recommends at least two, to reduce data loss if one fails. The maximum caps both the scaling and the worst-case bill. Set it too low and requests are refused on your busiest day (Cloud Run 429 and 500 errors).
- Decide on logs. Cloud Run logs every request by default, and Google warns of significant logging charges on busy sites. You can exclude request logs, but then they can’t explain a sale-day gap later.
- Put it on your domain. The default
run.appaddress can’t set cookies from the server. Google calls same-origin serving (a path on your own site, through a CDN or load balancer) best practice; a subdomain with a DNS record also lets the server set cookies (Google: custom domain). - Keep the preview server. It is a separate service that makes Preview work. Delete it and you lose your main test tool.
Still on App Engine from an older set-up? Google’s Cloud Run guide says to disable App Engine once no traffic reaches it, to avoid unexpected charges.
A managed host: what you still own
A managed host runs the tagging server on its own infrastructure. Stape says it “handles cloud setup, scaling, and maintenance”. Addingwell runs the server on a subdomain of your site and monitors the events it receives and sends on. Your server container is the same one you would build for Cloud Run.
You still own:
- The server container in Tag Manager: every tag, trigger and consent condition.
- The subdomain’s DNS record, the line in your domain settings that points your tracking subdomain at the host. A site rebuild or a domain move can drop it, and collection stops with it.
- Access. The brand should own the Tag Manager account and the hosting account, with the agency or contractor added as users.
Five questions to ask any host before you sign up:
- How and when do you update the tagging server?
- Where do my logs live, and for how long?
- Which region do the servers run in (UK or EU, if that matters to you)?
- What happens to requests above my plan’s limits on a sale day?
- Who receives alerts when the server stops answering?
Google’s manual set-up guide adds one more point: whoever owns the server environment may have access to your data. Read the host’s terms.
Google tag gateway: what it does and doesn’t do
Tag gateway sits between your site and Google. Your site loads the Google tag from a path on your own domain, and some measurement requests go to Google through it (Google: set up tag gateway). Google’s help pages cover Cloudflare, Akamai, Fastly, Amazon CloudFront and Google Cloud’s load balancer (Google: tag gateway with your CDN).
Before you switch it on:
- It runs nothing of yours. No Meta tag, no Conversions API, no control over what is sent.
- On Cloudflare it covers the whole domain. Cloudflare says it applies to every hostname and subdomain in the zone (your domain on Cloudflare), and its first-party tag overrides the existing script (Cloudflare: Google tag gateway).
- It doesn’t change who sets the cookie. Safari’s limits on cookies set in the browser still apply: F-401 , and I turned on Google Tag Gateway, but my Safari conversions still die after 7 days.
With a server container as well, Google’s scripts can be served first-party through your CDN or through the tagging server (Google: first-party scripts). Where that step fits when you move an existing site over is in moving from client-side to server-side GTM.
What to write down, whichever route you choose
One page, kept with your tracking plan:
- where the tagging server runs, and the account it is billed to;
- the server container URL and the DNS record behind it;
- who updates the server, and when they last did;
- where the logs are, and who can read them;
- who to call when Preview shows nothing.
Without that page the route doesn’t matter, because nobody knows where to look. A full tracking handover is described under tracking plan and documentation.
Who should set it up and look after it?
I’m Baris Asa, a London tracking consultant: eight years in tracking, 19 faults filed in the archive. I set up server-side GTM on whichever route fits, for ecommerce brands and the agencies behind them, fix it when it fails, and leave the brand owning every account, with the page above written. Already broken? The checks are in Server-side GTM errors. Send your store platform and the server container URL you found above to [email protected].
Hosting is one question of several. Server-side tracking explained shows where the others are answered.
Common questions
Do I need Google Cloud to run server-side GTM?
No. Cloud Run in your own Google Cloud project is the route Google documents first, and Tag Manager can set it up for you. Managed hosts such as Stape and Addingwell run the same tagging server for you, and Google’s manual set-up guide covers running it on your own servers. The server container you build in Tag Manager is the same on all three.
Can Google tag gateway replace a server container?
Only if all you need is Google’s tags loaded from your own domain. On a CDN integration such as Cloudflare it is a setting, with nothing for you to update or scale; on your own load balancer or web server, your team maintains the route. Either way it runs none of your tags and sends nothing to Meta. Meta’s Conversions API, or control over what each platform receives, still needs a server container. Its effect on Safari cookies is a separate question, covered in the tag gateway note.
Who updates the server-side GTM tagging server?
On Cloud Run, whoever runs your Google Cloud project. Google’s guide says to deploy a new revision with the stable image at least for each major release, because updates carry security fixes and new features. On your own servers, you update the preview server and every tagging server. On a managed host, the host runs the servers; ask them in writing how and when they update.
Can I move server-side GTM from Cloud Run to a managed host later?
Yes. The server container stays in Tag Manager. Set up the new tagging server with the container config, test it on a temporary subdomain, then add its address to the server container URLs in Tag Manager’s container settings and move the main subdomain’s DNS record. Keep the old server running until Preview on the new one shows every purchase tag firing. The same steps work in reverse.
Who should look after server-side GTM if we have no developer?
Usually a managed host for the servers, plus one named person for the container, the tags and the domain record. That person can be in-house, at your agency, or a contractor. The brand should own the accounts, with a one-page note of where everything runs and who to call.
Sources
Read on 7 November 2026:
- Google for Developers: Cloud Run set-up (automatic or manual provisioning, at least two instances, maximum instances and worst-case cost, updating with the
stableimage, request logging charges, App Engine), manual set-up (container config, one preview server, updates, data access by the environment owner), custom domain (same origin as best practice, subdomain, default domain), first-party scripts, Google tag gateway and its set-up guide - Tag Manager Help: Google tag gateway with your CDN
- Cloudflare: Google tag gateway (measurement path, zone-wide, overrides the existing script)
- Stape: sGTM hosting provider; Addingwell: documentation (subdomain, event monitoring)