When I recommend server-side tracking to a client, the next question is almost always "where does the server live?" Server-side Google Tag Manager needs a cloud server to run on, and for most of the businesses I work with, that server is hosted on Stape. Many store owners have seen the name in a setup guide or an invoice without knowing what it actually does. This guide explains Stape in plain English: what it is, how it fits into your tracking, what it costs and when it is the right choice.
What is Stape?
Stape (stape.io) is a hosting platform for server-side Google Tag Manager. Google Tag Manager has two kinds of containers: the normal web container that runs in the visitor's browser, and a server container that runs on a cloud server. Google provides the software for the server container, but you have to host it somewhere. Stape is a service that runs that server for you, keeps it updated and adds extra tools built for tracking.
In practice, Stape does three jobs:
- Hosting: it runs your server-side GTM container in a region you choose, such as the US or Europe.
- Custom domain: it connects the container to a tracking subdomain on your website, for example
data.yourstore.com, so requests stay first-party. - Extras: it adds features called power-ups, plus ready-made tags, apps and plugins for platforms like Shopify and WordPress.
You still build your tags, triggers and variables inside Google Tag Manager. Stape is the place where the server container runs, not a replacement for GTM.
How does Stape fit into a tracking setup?
Stape sits between your website and the ad platforms. Your web GTM container sends events to your Stape server container, and the server container forwards them to GA4, Google Ads, Meta and others. A typical flow looks like this:
- A shopper adds a product to the cart, and the website pushes an
add_to_cartevent to the data layer. - Your web GTM container sends that event to your tracking subdomain instead of straight to Google.
- The Stape server container receives the request through a client, such as the GA4 client.
- Server tags send the event on: a GA4 tag, a Google Ads conversion tag, the Meta Conversions API tag, a TikTok Events API tag and so on.
- The server can set first-party cookies, add customer data for matching and remove fields you do not want to share.
If you are new to the concept, my guide on what server-side tracking is and whether you need it covers the general idea before Stape enters the picture.
Browser-only vs Stape server-side
| Browser-only tags | Server-side GTM on Stape | |
|---|---|---|
| Where tags run | In each visitor's browser | On your Stape server container |
| Requests to ad platforms | One per platform, from the browser | Mainly one, to your own subdomain |
| Control over shared data | Limited | You choose fields per platform |
| Meta Conversions API | Needs a separate integration | Built from the same event stream |
| Hosting | None | Stape plan (free tier available) |
Why do businesses choose Stape?
Businesses choose Stape because it removes the server work from server-side tracking. Running server-side GTM on Google Cloud yourself means creating Cloud Run services, scaling settings, a preview server, logging and a load balancer for your custom domain. Stape replaces that with a guided setup: you paste your container configuration, pick a server location and add a DNS record.
The other reasons I see most often:
- Faster setup: a working server container with a custom domain usually takes minutes to create, which leaves more time for the part that matters, the tags.
- Predictable pricing: plans are priced by the number of requests your container receives each month, so cost grows with traffic.
- Tracking-specific features: power-ups such as Custom Loader and Cookie Keeper solve problems that generic cloud hosting does not. I explain each one in Stape power-ups explained.
- Ready-made tags and apps: Stape publishes server tags for Meta, TikTok and other platforms, and apps for Shopify and WordPress that create a clean ecommerce data layer.
- Logs and monitoring: you can see request volume and logs in one dashboard, which helps when something stops firing.
How much does Stape cost?
Stape charges by monthly requests, and it has a free plan for low-traffic sites. At the time of writing, the free plan covers a limited number of requests per month, and paid plans start at a low monthly price for hundreds of thousands of requests, with larger plans for busier stores. Some power-ups are only available on paid plans. Prices and limits change, so always check stape.io before you budget.
A request is any hit your server container receives, including page views and script loads, so a busy store uses requests faster than its order count suggests. From my own projects:
- An online course website I set up, Lesson Computer, runs a Stape Pro container handling over 21,000 requests a month.
- Every client tracking project I have delivered runs on its own Stape Pro container, from small Shopify stores to busier WooCommerce shops.
If you are comparing Stape with hosting on Google Cloud yourself, I break down the trade-offs in Stape vs Google Cloud Run for server-side GTM.
How do you set up a Stape server container?
Setting up Stape takes five main steps, and the DNS step is the one people most often skip. Here is the order I follow:
- Create a server container in Google Tag Manager and copy its container configuration string.
- Create a container on Stape, paste the configuration and choose a server location close to your customers.
- Add a custom domain, such as
sst.yourstore.com, by creating the CNAME or A record Stape shows you in your DNS settings. Wait until Stape marks it as Ready. - Point your web tags to the server, for example by setting the server container URL in your Google tag, so GA4 hits go to your subdomain.
- Build server tags for each platform, test them in GTM Preview on both containers, and check that each platform receives the events, with Meta deduplicating browser and server copies.
Website → web GTM → https://sst.yourstore.com (Stape) → GA4 / Google Ads / Meta CAPI / TikTok
On Amanda Trends and Venture's Wix store, for example, the Stape container sits behind a custom tracking subdomain verified with a CNAME record, and every funnel event reaches Meta through the Conversions API. You can see the full build in the Amanda Trends and Venture case study.
What Stape does not do
Stape makes server-side tracking easier, but it does not make bad tracking good. Three limits are worth knowing before you start:
- It does not fix your data layer. If purchase events fire twice or send the wrong value in the browser, the server forwards the same mistakes.
- It does not replace consent. You still need a consent banner and Consent Mode v2, and server tags should respect the visitor's choice.
- It does not stop every ad blocker. A first-party subdomain and Custom Loader reduce blocking, but some privacy tools still block tracking.
When should you use Stape?
Use Stape when paid ads are an important part of your revenue and you want server-side tracking without managing cloud infrastructure. It is a strong fit for:
- Shopify, WooCommerce, Wix and custom stores running Meta and Google Ads.
- Lead-generation sites that want Meta Conversions API and Google Ads enhanced conversions from one setup.
- Agencies that manage many client containers and want one dashboard.
It is less necessary for a small site with very little ad spend, where a clean browser setup may be enough for now.
Final thoughts
Stape is the hosting layer that makes server-side GTM practical for most small and mid-sized businesses. The value still comes from the setup: a clean data layer, a first-party subdomain, correct deduplication and testing in every platform. If you want me to check your current tracking and tell you whether Stape makes sense for your store, you can book a free tracking audit or see how I approach advanced conversion tracking.