How Much Does Server-Side Tracking Cost? Stape vs Google Cloud Run (2026)
Server-side tracking has two costs: hosting for the server container, and the setup work to build and test it. For most small and mid-sized stores, hosting costs between $0 and about $100 a month. Setup is a one-off project, and it is usually the bigger number.
This guide breaks down both, shows how to estimate your own hosting bill, and explains when the cheaper option stops being cheaper.
Key takeaways
- Hosting is billed by traffic. Stape uses fixed plans by request volume; Google Cloud Run bills for the servers you run.
- Google estimates about $45 per server per month on Cloud Run and recommends at least 2 servers in production, so plan for roughly $90 a month before traffic grows.
- Stape’s paid plans start at $17 a month (billed annually) for up to 500,000 requests.
- The real cost is usually setup and maintenance: tags, consent, deduplication and testing.
What you are paying for
With normal (client-side) tracking, the visitor’s browser sends data straight to Google Analytics, Meta, TikTok and others. With server-side tracking, the browser sends data to your own tracking server first. That server, a Google Tag Manager server container, then forwards it to each platform.
The server has to run somewhere, and that is the hosting cost. The two most common choices are:
- Stape, a managed hosting service built for server-side GTM.
- Google Cloud Run, Google’s own cloud, where GTM can create the server for you.
Other hosts exist, but these two cover most setups.
Option 1: Stape pricing
Stape charges a fixed monthly price based on how many requests your server receives. These are the plans listed on Stape’s pricing page at the time of writing:
| Plan | Price per month (billed annually) | Requests per month |
|---|---|---|
| Free | $0 | Up to 10,000 |
| Pro | $17 | Up to 500,000 |
| Business | $83 | Up to 5 million |
| Enterprise | $167 | Up to 20 million |
| Custom | Quote | Unlimited |
Monthly billing costs a little more than annual billing. Check the pricing page before you buy, because plans change.
Good for: most Shopify and WooCommerce stores, agencies managing many clients, and anyone without a developer. You get a predictable bill, a dashboard, and add-ons such as custom loaders and a built-in custom domain setup.
Option 2: Google Cloud Run pricing
When you create a server container in Google Tag Manager, GTM can set it up automatically on Google Cloud Run. You pay Google for the servers.
Google’s Cloud Run setup guide estimates that each server costs approximately $45 a month, and recommends a minimum of 2 instances to reduce the risk of data loss if one goes down. That puts a basic production setup at around $90 a month, and more as traffic grows and Cloud Run adds servers.
Watch out for logging. Cloud Run writes request logs by default, and on a busy server those logs can cost more than the servers themselves. Turn off or limit request logging once everything is tested.
Good for: high-traffic sites with an in-house developer or DevOps person, and companies that need everything inside their own Google Cloud account for data or compliance reasons.
How to estimate your request volume
Hosting price depends on requests, so estimate them first:
- In GA4, open Reports → Engagement → Events for the last 30 days and note the total event count.
- Add the other platforms you will send through the server only if they use their own browser tags pointing at the server. In a typical setup, one GA4 request feeds several server tags (GA4, Meta CAPI, Google Ads), so it only counts once.
- Add 20 to 30% for growth and sale periods such as Black Friday.
Example: a store with 400,000 GA4 events a month fits Stape’s Pro plan (up to 500,000). If that store grows to 1.5 million events, it needs the Business plan.
You can also use my free sGTM cost calculator to compare plans for your traffic.
Stape vs Google Cloud Run: side-by-side
| Stape | Google Cloud Run | |
|---|---|---|
| Billing | Fixed plan by requests | Pay for servers, logs and traffic |
| Typical small-store cost | $0 to $17 a month | About $90 a month (2 servers) |
| Cost predictability | High | Medium: spikes and logging change the bill |
| Setup difficulty | Easy | Medium: needs Google Cloud access and tuning |
| Custom domain | Built-in option | You configure it yourself |
| Data stays in your own cloud account | No | Yes |
| Best for | Most stores and agencies | High traffic with a developer, or strict compliance needs |
For most small and mid-sized stores, Stape is simpler and cheaper. Cloud Run makes sense when you have the technical team to run it, or a reason to keep data in your own Google Cloud project.
The cost most people forget: setup and maintenance
Hosting is the small part. A server container that actually improves your data needs:
- Server tags for each platform: GA4, Meta Conversions API, Google Ads, TikTok Events API and others.
- Event deduplication, so Meta and TikTok don’t count the same purchase twice from the browser and the server. See my Meta Conversions API setup guide.
- Consent Mode, so you only send data you are allowed to send.
- A custom tracking domain (such as
track.yourstore.com) for first-party cookies. - Testing in GTM preview, GA4 DebugView and Meta Events Manager. Here’s how to check server-side events are reaching GA4.
- Maintenance when your theme, checkout or consent banner changes.
You can do this yourself if you are comfortable with GTM. Or you can hire a specialist, which is usually a one-off project plus occasional fixes. The price depends on how many platforms and events are involved, so ask for a written scope before you agree a price.
Is server-side tracking worth the cost?
It is usually worth it if:
- You spend a meaningful amount on Meta, Google or TikTok ads every month, and better data improves bidding.
- Your platforms report noticeably fewer purchases than your store.
- Many of your customers use Safari or iPhone, where browser tracking is most limited.
It is usually not worth it yet if:
- Your basic tracking is broken. Fix GA4 and your pixels first with a GA4 audit, because server-side tracking only forwards what the browser sends.
- You run very few ads and mostly need simple traffic reports.
Frequently asked questions
Is server-side tracking free?
The free Stape plan covers up to 10,000 requests a month, which is enough for testing or a very small site. Almost every real store needs a paid plan or Cloud Run.
Can I move from Cloud Run to Stape later?
Yes. The server container in GTM stays the same. You point it at the new host and update your tracking domain. Test thoroughly before switching traffic.
Does server-side tracking get around ad blockers and consent?
It should not be used to ignore consent. A first-party tracking domain can make data collection more reliable, but you must still respect the visitor’s consent choices.
How long does setup take?
A standard store with GA4, Meta CAPI and Google Ads usually takes a few days, including testing. Complex setups with several domains or a custom checkout take longer.
Need help?
I set up and fix server-side tracking for e-commerce stores and agencies, including Stape and Cloud Run hosting, Meta CAPI and Google Ads. See my server-side tracking and Meta CAPI service, or book a tracking audit and I’ll tell you whether server-side tracking is worth it for your store.
Need this implemented, audited, or white-labeled?
Whether you are an eCommerce brand owner fixing signal loss or a digital marketing agency needing a senior analytics engineer under strict NDA, I deliver 24–48h SLA turnaround with 8.5+ EMQ match rates.


