How to Set Up Stape.io in 30 Minutes:
Step-by-Step Guide for Server-Side Tracking 2026

1. What Stape.io is (and when it makes sense)

Stape.io is a managed hosting provider specifically for Google Tag Manager Server containers (sGTM). You get a preinstalled server, you don't manage Docker, Cloud Run, scaling or system updates. You click together what you need in the Stape dashboard - the rest runs in the background.

Alternatives to Stape

• Google Cloud Run (self-hosted) - the official Google guide. Pure server costs around $10-30/month, but you need DevOps know-how (Docker, GCP console, scaling rules).
• Platform apps like Elevar or TrackBee - Shopify-focused, $99-200/month, very strong UI for e-commerce.
• Other managed hosts such as Taggrs or Addingwell - comparable to Stape with slightly different feature sets.

When Stape makes sense

• You want sGTM but have no DevOps experience
• You need your own subdomain (for longer cookie lifetime & ad-blocker protection)
• You want a scalable setup without server maintenance
• You're outside Shopify (for pure Shopify stores, Elevar/TrackBee are usually faster)

2. Prerequisites

• ✓ Existing GTM Web container with an active GA4 tag
• ✓ Own domain (e.g. yourdomain.com) with access to DNS management (Cloudflare, IONOS, GoDaddy, Strato, Netlify, etc.)
• ✓ Stape account - free on the Free Tier
• ✓ Google account with GTM access (Edit rights)
• ✓ 30 minutes of time + 2-3 hours waiting time for DNS propagation

You don't need any cloud-engineering knowledge, no Docker experience and no credit card (for the Free Tier).

3. Step 1: Stape account & container (about 5 min)

1. Go to stape.io → Sign up → sign in with Google or email.
2. In the dashboard click "Create Container".
3. Choose a region. Important: pick the geographically closest region to your users - for German/EU users either Germany (Frankfurt) or EU. This saves latency AND is GDPR-relevant (data localization in the EU).
4. Pick a plan: the Free Tier (100,000 requests/month) is enough for most SMB setups; the Basic plan is $20/month for more traffic plus Power-Ups.

4. Step 2: Create GTM Server container in Google Tag Manager (about 5 min)

1. In Google Tag Manager: Admin → Add Container.
2. Container name: e.g. "Server Container".
3. Container type: select "Server".
4. Server setup: choose "Manually provision tagging server" - NOT the automatic GCP provisioning. That costs money and isn't necessary for our Stape setup.
5. GTM now shows you the Container Configuration String - a long encoded text. Copy it to your clipboard.
6. Back in the Stape dashboard: paste Container Config → Save.

Stape automatically detects you're trying to configure a container and sets up the server routing table. Official Google docs: Google Manual Setup Guide.

5. Step 3: Set up DNS custom subdomain (10 min + waiting time)

This is the most critical step - this is where most setups fail.

5.1 Pick a smart subdomain

Avoid obvious terms like gtm.yourdomain.com, track.yourdomain.com, analytics.yourdomain.com or stape.yourdomain.com. Ad blockers and browser privacy lists detect these immediately and block requests.

Recommendation: neutral subdomains like data.yourdomain.com, metrics.yourdomain.com, sgtm.yourdomain.com or custom letter combinations like ms.yourdomain.com.

5.2 Add custom subdomain in Stape

In the Stape dashboard: open container → "Custom Domain" → enter the subdomain name (e.g. data.yourdomain.com). Stape generates the DNS records you need to add - typically one or two CNAME records.

5.3 Add the DNS records at your provider

Log in to your DNS provider (Cloudflare, IONOS, GoDaddy, Strato, etc.) → DNS management for your domain → add CNAME record(s) following Stape's instructions.

5.4 Trigger verification

Back in the Stape dashboard: click "Verify". Typical wait time is 2-3 hours, in extreme cases up to 72 hours. Stape pings your DNS records until they respond correctly. You can check propagation with dnschecker.org.

6. Step 4: Set Tagging Server URL in GTM (2 min)

Once Stape gives the green light:

1. Open the GTM Server container → Admin → Container Settings.
2. Tagging Server URL: https://data.yourdomain.com (your verified subdomain).
3. Save.

This tells GTM that all events sent to this URL should be processed by the Server container.

7. Step 5: Configure GA4 client + test in DebugView (5 min)

So GA4 actually runs through server-side:

7.1 In the GTM Server container

• Clients → "New" → pick "GA4" → Save.
• Now the Server container can receive GA4 requests and forward them to the GA4 property.

7.2 In the GTM Web container

• Open the existing GA4 configuration tag.
• Under "Fields to set": new entry server_container_url = https://data.yourdomain.com.
• Save + publish the container.

7.3 Test in GA4 DebugView

• Open GA4 → Admin → DebugView.
• Load your site in Chrome (with GTM Preview mode active).
• Events should appear in DebugView AND the request path should contain data.yourdomain.com, NOT www.googletagmanager.com.

If that's the case: server-side is running. 🎉

8. Step 6: GDPR + Consent Mode v2 (3 min)

Server-side does not automatically make tracking GDPR-compliant - the legal basis still has to exist. Required settings for a clean setup:

• ✓ Consent Mode v2 must be active in the Web container and block tags until consent is given. Required for EU advertisers since March 2024.
• ✓ GeoIP anonymization enabled in Stape (Settings → "Anonymize IP").
• ✓ Data minimization per Art. 5(1)(c) GDPR: only send what you need. NEVER raw, unhashed emails - always SHA-256.
• ✓ EU region selected for your Stape server (see Step 1).
• ✓ DPA with Stape signed (Data Processing Agreement under Art. 28 GDPR).

More details on Consent Mode v2 in the pillar article on Server-Side Tracking (section "Consent Mode v2 implementation").

9. Common issues & fixes

10. What does it really cost?

The Free Tier covers smaller sites reliably. Cost comparison rolled out:

Realistic for most German SMBs: Stape Basic ($20/month, around €19), combined with a one-time setup investment. If you'd rather hand it over, I build server-side setups as a module from €400 (Stape account in your name, you stay in control).

11. Next steps

Once your server is running you can go deeper. Sensible follow-up topics:

• Meta CAPI via server-side GTM - conversion data straight from your server to Meta, much higher match rate (Stape's Atasun Optik case saw +93% conversion gains)
• Google Ads Enhanced Conversions with server-side - match rate from 60-70% to 90%+
• Bypass Safari ITP via Same-Origin Path-Based sGTM, cookies from 7 to 400 days lifetime
• Cross-domain tracking between multiple subdomains (e.g. marketing site ↔ app)

For the full background - why server-side, what it solves, what it does NOT solve - see the pillar article on Server-Side Tracking. If you'd rather hand the whole setup over: Server-Side Tracking module from €400 or get in touch directly.

12. FAQ

What does Stape.io actually cost?

Stape offers a Free Tier with 100,000 requests per month - enough for smaller sites with about 5,000 to 8,000 visitors monthly. The Basic plan costs around 20 USD/month for up to 1 million requests - typical for SMBs with newsletters, demos and moderate traffic. Pro plan and Power-Ups move between 50 and 150 USD/month for larger setups.

Do I need cloud-engineering knowledge for Stape.io?

No. Stape manages the server for you. You need GTM knowledge and access to your domain's DNS management. Docker, Kubernetes or the Google Cloud Console are not required - Stape handles that in the background.

Is Stape.io GDPR-compliant?

Stape offers EU server regions (Frankfurt) - this lets you process personal data within the EU. GDPR compliance still depends on your implementation: Consent Mode v2 must be active, GeoIP anonymization should be enabled, a Data Processing Agreement (DPA) with Stape must be signed, and data minimization (SHA-256 for emails, IP truncation) is mandatory.

What happens if the Stape server goes down?

Stape guarantees 99.9% uptime. During a temporary outage tracking events are not captured - but your website itself continues to run, because the server container is only responsible for tracking data. There is no impact on the visitor experience.

Can I later migrate from Stape to self-hosted?

Yes. The GTM Server Container itself is portable - you can use the same Container Configuration String later on your own Google Cloud Run instance or with another host like Addingwell or Taggrs. You would need to reconfigure the DNS subdomain, but the GTM container stays identical.

What if I use Cloudflare for my DNS?

Works fine. Important: turn the Proxy status (the orange cloud) to "DNS only" (grey cloud) for the Stape subdomain. If the Cloudflare proxy is active Stape cannot verify the domain, because requests get routed via Cloudflare instead of directly to Stape.