Free tool

Server-Side Tracking Cost Calculator

Enter your monthly visits, page views and events per visit: the tool estimates how many requests your Google Tag Manager server container receives per month, per day and per second. It then picks the smallest plan that covers them at Stape and at TAGGRS, and works out the Google Cloud Run cost from Google’s own guide.

Google puts each Cloud Run server at about $45 a month, and recommends at least 2 instances in its Cloud Run guide and at least 3 per container in its server-side tagging overview. At Stape, a request is every hit your server container receives, gtm.js and gtag.js loads included; one event sent on to several platforms still counts as one request.

Fictitious example
/mo
Your site’s sessions over one month, from your analytics tool.
/visit
Each page view sends a hit: the Google tag sends a page_view event when it loads.
/visit
Events sent on top of page views: scroll, click, add to cart, purchase.
/hit
Keep 1 if your web container sends a single stream, as Google advises: the server container then passes it on to each platform. Set 2 if each hit reaches the server in two separate streams.
/page
Stape also counts gtm.js or gtag.js loads when your server container serves them: set 1 in that case. The tool counts it on every page view, browser cache left out: a choice of the tool.
%
A choice of the tool, adjustable: 20% by default, to keep room under the plan’s quota as your traffic grows.
inst.
Google recommends at least 3 instances per container in its server-side tagging overview, and at least 2 in its Cloud Run guide: the tool starts at 3.

Requests received per month

-

Plan picked at each host, price and date the price list was read
HostPlanRequests includedPricePrice list read on
  • Prices as shown on each host’s price list, in its currency, with no conversion. The plan is picked on included requests alone: the plan’s other limits are on its price list.
  • Neither price list states whether VAT is included. Stape says it is required to charge sales tax in certain US states.
  • Stape: past the monthly quota, a free plan, or a paid plan with auto-upgrade off, stops serving traffic until the next billing period; with auto-upgrade on, the subscription moves up one tier.
  • TAGGRS: past the request limit, data is no longer sent to the platforms; automatic upgrading avoids this stop.

Google Cloud Run, from Google’s guide

The guide puts each server at about $45 a month (1 vCPU, 0.5 GB of memory, CPU always allocated); Google’s overview gives $30 to $50 per server. Performance varies with the number of tags and what they do. For a detailed amount: Cloud Run pricing and Google Cloud pricing calculator.

What the estimate leaves out

  • Traffic peaks: the tool works on an average per second, and a sales evening packs requests into a few hours.
  • Cloud Run logging and network egress: Google says large amounts of network traffic may increase the cost, with no figure the tool can reuse.
  • The preview server and the load balancer of a multi-region deployment, both in Google’s guide, are not counted.
  • Preview and bot hits, which Stape may count on top.
  • Setup and maintenance time: it depends on your tags and platforms, and the tool puts no figure on it.

Sources read on November 6, 2026: Google, Cloud Run server-side tagging guide, Google, server-side tagging overview, Google, server-side tagging fundamentals, Stape pricing, Stape, plan tiers and limits and TAGGRS pricing.

Want Server-Side Tracking Sized For Your Traffic?

When I set up your server-side tracking, I measure your site’s real request volume, choose the hosting with you and configure your Google Tag Manager server container.

20 minutes · No commitment · 100% confidential

Step 1 Of 2 · Your Project

Step 2 Of 2 · Your Details

Who are these campaigns for? *
What are you looking for in our collaboration? * You can pick several
Where do your ad campaigns stand today? *
When would you ideally like to start? *

How the tool counts requests

Requests per month = visits × [(page views + events) × streams + page views × scripts]

A server container counts like a water meter: every hit that comes in turns the meter once, whatever the number of taps it feeds downstream. Stape counts each incoming request this way, script loads included, and one event passed on to several platforms stays one request. TAGGRS counts every event on the site: page view, click, purchase. Google advises sending a single stream to the server container, which then passes it on to each platform: streams then stay at 1.

Fictitious example: 40,000 visits a month, 3 page views and 2 events per visit, one stream and no script served by the server make 40,000 × 5 = 200,000 requests. With the 20% headroom, the tool keeps 240,000 requests, or 8,000 a day and 0.09 a second on average over a 30-day month. At Stape, the Pro plan covers up to 500,000 requests; at TAGGRS, the Basic plan covers 750,000. The 30-day month and the headroom are choices of the tool.

For Cloud Run, the tool multiplies the number of instances by the cost Google’s guide gives for one server, about $45 a month: 3 instances come to about $135 a month. According to Google, 2 to 10 autoscaling servers handle 35 to 350 requests per second, depending on the number of tags and what they do. Logs, network egress and the preview server come on top depending on your usage: the tool invents no amount for them, and the Google Cloud pricing calculator puts a figure on them.

What the estimate gives you

  • Choose your hosting: see at a glance the plan that covers your traffic at Stape, at TAGGRS and on Cloud Run, each in its own currency. You know which price list to read first.
  • Prepare your tracking budget: present a monthly cost built on your own traffic before you start the project. You price server-side with your visits, not with an average.
  • Plan for growth: adjust the headroom to see at what traffic you move up a plan. You keep room under the quota before a busy season.

Frequently asked questions

What counts as a request for a server container?

At Stape, a request is every hit your Google Tag Manager server container receives: tracking hits, and also script loads such as gtm.js or gtag.js. Only incoming requests count: one event that triggers several tags for several platforms stays one request. Stape notes that preview or debug sessions and bots hitting your container domain can be counted too. TAGGRS defines a request as every event on your website, for example a page view, a click or a purchase.

How many Cloud Run instances should I plan?

Google recommends at least 3 instances per container in its server-side tagging overview, and at least 2 in its Cloud Run guide, to reduce the risk of data loss if a server goes down. The guide puts each server at about $45 a month, with 1 vCPU and 0.5 GB of memory, and says 2 to 10 autoscaling servers handle 35 to 350 requests per second, depending on your tags. The tool starts at 3 instances, and you set the number.

Why plan growth headroom?

Because a quota you go past stops tracking or changes your plan. At Stape, a free plan, or a paid plan with auto-upgrade off, stops serving traffic until the next billing period; with auto-upgrade on, the subscription moves up one tier. At TAGGRS, past the limit, data is no longer sent to the platforms unless the plan upgrades automatically. The 20% headroom is a choice of the tool, adjustable from 0 to 500%: set it to your own growth.

Are my numbers sent anywhere?

No. The calculation runs in your browser: nothing is sent or stored, and your numbers are gone when you close the page.

Théo Maupilé

Growth partner

Positioning, acquisition, innovation: together we build a lasting growth system.

Théo MaupiléFreelance Paid Media

Google PartnerSuperMalter

◉ Certifications

Official Google Partner
& SuperMalter