Blog

What server-side GTM really costs per month

Published JAYC Consultancy6 min read

  • Server-Side Tagging
  • Google Tag Manager
  • Tracking & Analytics

Server-side Google Tag Manager (GTM) promises cleaner data and more control over what your tracking shares. The sensible next question is: "What will it cost us every month?"

A standard web container is free, but a server container needs a server, and servers cost money. The good news is that the costs are predictable once you know where they come from.

All prices below were checked in November 2026 and are shown in US dollars, as Google and Stape publish them. Your actual bill will vary with traffic, region, configuration and exchange rates, so please treat every figure as a guide, not a quote.

Where the money goes

A server-side GTM setup usually has four running costs:

  • Hosting for the tagging servers that receive and forward your data.
  • A preview server for testing changes.
  • Logging, which is easy to overlook.
  • People time for updates and health checks.

Google's own setup hosts the servers on Google Cloud Run, a pay-as-you-go service. You can also use a managed host, which we cover below.

What Google says to expect

Google's Cloud Run setup guide for server-side tagging gives a rough starting point. It says that, in its recommended configuration, "each server costs approximately $45 /month (USD)", based on a Cloud Run instance with 1 vCPU and 0.5 GB of memory, with the CPU always allocated.

What matters most is how many servers you run. Google recommends "a minimum of 2 instances to reduce the risk of data loss in case of a server outage". It also says it expects autoscaling between 2 and 10 servers to handle 35 to 350 requests per second, though performance varies with the number of tags and what they do.

So a production setup following Google's advice starts with at least two always-on servers. Google notes that the maximum instance setting is your worst case for cost, and suggests a billing alert to avoid surprises.

You'll also need a preview server. Google's manual setup guide says to deploy exactly one, without scaling it beyond a single instance.

An illustrative estimate for a UK-hosted setup

Here's a worked example built from Google's published Cloud Run prices. This is an illustrative estimate, not a quote.

Cloud Run prices depend on the region. London (europe-west2) is in Google's higher "Tier 2" price band. As of November 2026, Google lists these instance-based billing prices for London:

  • CPU: $0.0000216 per vCPU-second
  • Memory: $0.0000024 per GiB-second

Assume two servers, each with 1 vCPU and 0.5 GiB of memory, running all month (730 hours, or 2,628,000 seconds each):

  • CPU: 2 × 2,628,000 vCPU-seconds × $0.0000216 = $113.53
  • Memory: 2 × 2,628,000 × 0.5 GiB-seconds × $0.0000024 = $6.31
  • Subtotal: $119.84

Cloud Run's free tier for instance-based billing covers the first 240,000 vCPU-seconds and 450,000 GiB-seconds each month, per billing account, applied as a discount at Tier 1 prices ($0.000018 and $0.000002). That's worth about $5.22, bringing the estimate to roughly $114.62 a month for the tagging servers.

This is higher than Google's "approximately $45" per server, partly because London is in the pricier band, so check your own figures with the Google Cloud pricing calculator. It also excludes the preview server, extra servers at busy times, logging and tax. Outbound internet traffic is billed separately at Google Cloud networking rates, and a multi-region setup needs a load balancer, which has its own charges.

Logging: the cost people forget

This one is easy to miss. Google's setup guide warns that, by default, "information about every single request" is logged. It adds that if your server handles a lot of requests (it gives the example of more than 1 million a month), "those log messages may incur significant logging charges".

According to Google Cloud Observability pricing, as of November 2026:

  • the first 50 GiB of logs per project per month is free
  • after that, logging storage costs $0.50 per GiB, including up to 30 days' storage
  • keeping logs for longer than 30 days costs $0.01 per GiB per month

So every 10 GiB above the free allowance adds about $5. Google's guide explains how to exclude request logs and noisy tag messages using the Logs Router. Keep what you need for troubleshooting and switch off the rest.

Managed hosting: the alternative

If you'd rather not manage Google Cloud yourself, managed providers host the container for a fixed monthly fee. As one example, Stape's pricing page lists these plans as of November 2026:

  • Free: $0, up to 10,000 requests
  • Pro: $20 a month billed monthly ($17 a month billed annually), up to 500,000 requests
  • Business: $100 a month billed monthly ($83 billed annually), up to 5 million requests
  • Enterprise: $200 a month billed monthly ($167 billed annually), up to 20 million requests

Plans are based on requests, not visitors, so check how requests are counted before choosing. Compare features, support and where your data is hosted, not just the price.

Don't forget consent and people time

Server-side tagging doesn't remove the need for consent, as we explain in why server-side tracking still needs consent. In the UK, the relevant rules sit in the UK GDPR and PECR. This is general information, not legal advice.

Changes can also mean extra work. From January 2027, Google's ad tags in server containers will receive full IP addresses unless you opt out, as we explain in our post on server-side GTM and full IP addresses.

Google also recommends updating your tagging server for each major version release, a small but regular job.

Your monthly cost checklist

  • Count your servers. How many always-on instances are you running, and what's the maximum?
  • Check your region. London is in a higher price band than some other European regions.
  • Check the billing model. Is CPU always allocated, or billed per request?
  • Look at your logs. Are you above the 50 GiB free allowance? Do you need request logs?
  • Review data transfer and load balancer costs, especially for multi-region setups.
  • Set a billing alert in Google Cloud so a spike doesn't go unnoticed.
  • Compare managed hosting if you'd prefer a fixed monthly fee.
  • Allow for exchange rates and tax, as Google and Stape publish prices in US dollars.
  • Budget time for updates and checks, not just hosting.
  • Check your numbers after any change. Our guide to why GA4 and Google Ads numbers differ explains which gaps are normal.

Getting value from every pound

Server-side GTM doesn't have to be expensive, but it should be set up with running costs in mind. In our experience, the biggest savings come from running the right number of servers, keeping logging sensible and being clear about what the setup is for.

If you'd like help estimating what server-side tagging would cost for your site, or reviewing an existing setup, take a look at our services and get in touch.

Sources

All pages checked in November 2026. Prices are in US dollars and may change.

Back to blog

Want this sorted for your own tracking?

A free 30-minute call. We'll look at your tracking with you and tell you what's broken and what to fix first.

Book a free call See all services