Data & Tracking
Stape: hosting server-side Google Tag Manager without your own cloud server
Copy for AI
Stape hosts the server container of Google Tag Manager for you.
Instead of setting up a server on Google Cloud Run yourself, you paste your server container’s configuration into Stape. Then you choose a server location and connect a subdomain of your own website.
The verdict: Stape is the simplest way to run server-side tracking for most B2B sites. Pick Cloud Run only when you need full logs or your IT team already lives in Google Cloud.
Your tags send their data to that server first. The server forwards it to GA4, Google Ads, Meta or LinkedIn.
Stape has a free plan for small volumes and paid plans based on the number of requests.
This article is about the hosting choice and the practical setup. What server-side tagging is, and why it makes measurement sturdier, is in our guide to server-side tagging.
For advertising specifically, read server-side tracking for Google Ads.
What exactly does Stape do?
It runs the second half of server-side Google Tag Manager for you.
Server-side GTM has two containers:
- Web container: the regular one, running in the browser
- Server container: a separate one, running on a server
That server has to live somewhere. Google’s standard route is Google Cloud Run in your own cloud project.
What you get on top of hosting
Stape offers the same server as a managed service, with extras on top:
- Hosting of the server container in a region of your choice, with scaling without managing servers yourself.
- Custom domain connection, so your server runs on a subdomain of your own site.
- Power-ups such as a custom loader (loading GTM through your own domain), a global CDN and Own CDN, where your server domain runs through the same IP address as your website.
- Templates and connectors for the Meta Conversions API, Google Ads and LinkedIn, among others.
So you don’t manage a server, but you still decide what each tag sends.
What does Stape cost?
Stape charges per month, based on the number of requests your server container processes.
According to Stape’s pricing page (checked 5 November 2026, in US dollars, with annual billing):
| Plan | Requests per month | Logs | Price per month |
|---|---|---|---|
| Free | up to 10,000 | not stated | 0 dollar |
| Pro | up to 500,000 | 3 days | 17 dollar |
| Business | up to 5 million | 10 days | 83 dollar |
| Enterprise | up to 20 million | export to S3/GCS | 167 dollar |
| Custom | unlimited | custom | on request |
These are the vendor’s prices, not ours.
Here’s where to check them yourself:
What counts as a request?
A request is every hit your server receives: a page view, an event, a script load.
For example, say a B2B site gets 20,000 visits a month with a handful of events per visit. That site quickly goes over the free plan’s 10,000 requests.
Rule of thumb: the free plan is for testing; production usually needs Pro or higher.
Stape or Google Cloud Run?
For most B2B sites, Stape: it’s cheaper to start and needs no server management.
In its Cloud Run setup guide, Google recommends running at least 2 instances to limit data loss during an outage. It says each server costs approximately 45 dollars per month.
A setup on Cloud Run therefore starts at around 90 dollars per month, plus your own time for management.
Here’s how that compares with Stape’s plans:
Cloud Run’s figure excludes your own management hours. Stape’s includes the management.
Side by side
| Stape | Google Cloud Run | |
|---|---|---|
| Setup | Paste configuration, choose region | Own GCP project, deployment, scaling |
| Pricing model | Fixed per plan, based on requests | Per instance and usage |
| Logs | Limited on smaller plans | Complete in Cloud Logging |
| Management | By Stape | By you |
| Extras | Custom loader, Own CDN, connectors | Everything GCP offers |
| Suited to | SMEs and most B2B sites | Large volumes, strict IT requirements |
Why log retention matters
The shorter log retention is the point that comes up most in practice.
Logs are your evidence when a conversion value is unrealistically high or an event arrives twice. With 3 days of logs, you have to be quick.
Best for Cloud Run: an IT department that already works on Google Cloud.
Setting up Stape in six steps
You work in two containers and one DNS panel, in this order.
Step 1: Create a server container in GTM
In Tag Manager, create a new container with “Server” as the target platform. Copy the container configuration.
Step 2: Create the container at Stape
Paste the configuration and choose a server location.
Tip: for Belgian and Dutch sites, pick an EU region.
Step 3: Connect a custom domain
Stape says it literally in its setup guide: use a custom domain to set first-party cookies, on the same root domain as your website.
For example: sst.yourcompany.com.
You add the DNS records Stape shows you. Verification usually takes 2 to 3 hours, sometimes up to 72 hours.
Step 4: Point your web container to the server
In your web container, set the server_container_url parameter in the Google tag to your subdomain.
Your GA4 hits then go to your own server instead of directly to Google.
Step 5: Build your server tags
In the server container, add three kinds of tags:
- GA4: the server-side GA4 tag
- Google Ads: the conversion tag
- Connectors: such as the Meta Conversions API
Every tag gets the same consent logic as in the browser.
A clean data layer in the web container makes this step far easier, because every event arrives with the same fields.
Step 6: Test and publish both containers
Preview the web container and the server container together. Check that every event arrives once.
Here’s the view to watch in the server container:
The mistakes we see most often
Five mistakes undo most of the benefit.
No custom domain
The server runs on Stape’s default domain.
Then you set no first-party cookies and lose the biggest benefit. Why that matters is explained in third party cookies.
Duplicate conversions in Meta
You send a Lead event through the Meta Pixel and through the Conversions API, without the same event_id.
Meta only deduplicates when event_id and the event name match within 48 hours.
This is the classic cause of duplicate purchases or leads after a move to server-side.
Skipping consent
Server-side feels like “outside the browser, so outside the banner”. That isn’t true.
On your server, too, you only forward what the visitor allowed. Pass your consent state, for example from Cookiebot, along with every event.
Forwarding personal data unfiltered
On your server, you can strip IP addresses and parameters before sending data to a platform.
Do so. It’s one of the main reasons to run a server at all.
Not looking at the logs
If you see a strange conversion value, check the logs within your plan’s retention period.
On Pro, that’s 3 days.
How do you check that it works?
Run five checks, from browser to ad platform:
| Check | Where | What you want to see |
|---|---|---|
| Hits go through your subdomain | Browser, Network tab | Requests to sst.yourcompany.com, not to google-analytics.com |
| Server receives and forwards | Server container Preview | Incoming request, outgoing tags with status 200 |
| GA4 receives | GA4 DebugView and real time | Events with the right parameters |
| Meta deduplicates | Events Manager, Test Events | Browser and server event with the same event_id, counted once |
| Google Ads | Conversion diagnostics | Conversions active, no duplicate actions |
The Google Ads check
In Google Ads, look at the conversion list. You want one action per real conversion, marked Primary:
The All conversions list in our own Google Ads account, October 2026. One primary action per conversion means no double counting.
Two primary actions for the same form usually mean the browser tag and the server tag both count.
Compare with your CRM
Then compare the leads in Google Ads, Meta and your CRM for a week.
Server-side tagging usually delivers a more complete signal. But you have to see the difference in your own data, not in a promise.
It also helps to send qualified leads back through offline conversions from your CRM.
Need help with server-side tagging?
It touches GTM, consent, your ad platforms and your DNS at the same time.
At Kaizo we built the chain for GA4, Google Ads and Meta; read the setup. At Suivo, lead tracking ran all the way into the CRM.
Not sure whether server-side makes sense for you? Start with a tracking audit.
If you want it built on Stape or Cloud Run, our tracking specialist does it. Pricing on request.
Frequently asked questions
What is Stape?
Stape is a hosting platform for server-side Google Tag Manager. It runs your server container, connects your own subdomain and offers extras such as a custom loader, CDN options and connectors for ad platforms.
Is Stape free?
There’s a free plan up to 10,000 requests per month, enough for testing. For a production site you usually need a paid plan.
Is Stape better than Google Cloud Run?
Stape is simpler and more predictable in price; Cloud Run gives more control and complete logs, but needs technical management and at least two instances.
Do I still need a cookie banner with server-side tracking?
Yes. Server-side tagging changes where the data is processed, not whether you need consent. Also read Consent Mode v2.
Where are Stape’s servers located?
You choose the server location yourself when you create your container. For European visitors, choose an EU region.
So should you use Stape?
If you want server-side tracking without running servers, yes.
Connect a custom domain on day one, deduplicate with event_id and keep consent in the chain.
Free website scan
Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.
We only use your details for your scan. No spam, unsubscribe anytime.