Once a business decides to use server-side Google Tag Manager, the next decision is where to host the server container. The two options I am asked about most are Stape, a managed hosting service, and Google Cloud Run, Google's own platform for running containers. Both run exactly the same server container software from Google. The difference is who manages the servers, how you pay and how much work goes into setup and maintenance. This guide compares them honestly so you can choose the right one for your business.
What is the difference between Stape and Google Cloud Run?
The difference is who runs the infrastructure. With Google Cloud Run, you create and manage the server-side GTM services inside your own Google Cloud project. With Stape, you paste your container configuration into Stape's dashboard and it runs the servers for you, with a custom domain and extra tracking features added on top.
Your tags, triggers and variables live in Google Tag Manager either way. Moving between the two later is possible because the container itself does not change. If you are still deciding whether you need a server container at all, read what server-side tracking is and whether you need it first.
Side-by-side comparison
| Stape | Google Cloud Run | |
|---|---|---|
| Who manages servers | Stape | You (or your developer) |
| Setup time | Minutes, guided | Hours, manual configuration |
| Pricing model | Monthly plans by request volume, free tier | Pay for compute, logging and network use |
| Production minimum | Small plan is enough for many sites | Google recommends more than one always-on server |
| Custom domain | Guided DNS setup in the dashboard | Load balancer or mapping you configure |
| Preview server | Included | You set it up separately |
| Tracking extras | Power-ups, ready-made tags, Shopify and WordPress apps | None built in |
| Logs and monitoring | Stape dashboard | Google Cloud logging and monitoring |
| Data location | Region you choose on Stape | Region you choose in your Cloud project |
| Best for | Small and mid-sized businesses, agencies | Teams with cloud skills, strict data policies |
Setup: how much work is each option?
Stape is faster to set up because most of the infrastructure is created for you. The usual steps are to create a container, paste the configuration string from GTM, pick a region and add the DNS record for your tracking subdomain. Stape creates the preview server and gives you a status for the custom domain.
Google Cloud Run takes more steps. Google provides an automatic provisioning option and a manual guide, and a production setup typically involves:
- Creating a Google Cloud project with billing enabled.
- Deploying the tagging server and a separate preview server.
- Setting the minimum and maximum number of instances and the CPU allocation.
- Mapping a custom domain, usually through a load balancer, and issuing an SSL certificate.
- Setting up logging, alerts and budgets so you notice problems and costs.
None of this is difficult for a developer who knows Google Cloud, but it is real work, and it has to be maintained when Google updates the server image.
Cost: what will you actually pay?
Stape is usually cheaper and more predictable for small and mid-sized sites, while Cloud Run can become competitive at very high volumes. The pricing models are different, so compare them on your own traffic.
- Stape charges by the number of requests your container receives each month. There is a free plan for low traffic and paid plans that step up in volume. At the time of writing, the first paid plan is priced for hundreds of thousands of requests, which covers many small stores.
- Google Cloud Run charges for compute time, memory, logging and network traffic. Google's own guidance for production server-side tagging recommends keeping servers always allocated and running more than one instance to reduce the risk of losing data, which creates a higher monthly floor even for small sites.
Two costs are easy to forget:
- Logging: Cloud Run logs every request by default, and log storage can add noticeable cost on busy sites unless you reduce it.
- Time: someone has to monitor, update and fix the Cloud setup. For a business without a developer, that time often costs more than the hosting.
Prices on both sides change, so always check stape.io and Google's server-side tagging documentation before you commit.
Features: what does Stape add?
Stape adds tracking-specific features that Cloud Run does not include. The most useful ones are Custom Loader, which serves GTM scripts from your own domain, and Cookie Keeper or Own CDN, which help first-party cookies last longer in Safari. I cover each in detail in Stape power-ups explained.
Stape also publishes ready-made server tags and apps, for example for Meta Conversions API and Shopify, which speed up common setups. On Cloud Run you can achieve the same results with community templates and your own configuration, but nothing is pre-built.
Control and compliance
Google Cloud Run gives you the most control. Everything runs inside your own Google Cloud project, under your own billing, access rules and data region. Some larger companies and legal teams prefer this because no extra vendor processes the data.
Stape is a third-party processor, but it lets you choose the server region, including EU locations, and offers privacy features such as data anonymization. For most small and mid-sized businesses this is acceptable, as long as it is listed in the privacy policy. Either way, consent still comes first: server-side tracking should respect the choices captured by your banner and Consent Mode v2.
Which should you choose?
Choose Stape if you want a reliable server container quickly and do not have a developer to manage cloud infrastructure. Choose Google Cloud Run if you already work in Google Cloud, need everything inside your own account or run very high traffic where self-managed hosting is worth the effort.
A quick decision guide:
- Shopify, WooCommerce, Wix or a small custom store: Stape.
- Agency managing many client containers: Stape, for one dashboard and quick setups.
- Enterprise with an in-house cloud team and strict data rules: Google Cloud Run.
- Very high traffic and cost-sensitive with technical staff: compare both on your real request volume.
In my own projects, most clients run on Stape. Respivox's Shopify store, for example, sends Meta, GA4 and Google Ads events through one Stape container on a custom tagging subdomain, which kept setup time focused on the tags rather than the servers.
Final thoughts
Stape and Google Cloud Run host the same container; the right choice depends on your team, your traffic and your data policies, not on which one is "better". If you would like me to recommend a setup for your store and estimate the monthly cost, I can do that in a free tracking audit or as part of an advanced conversion tracking project.