Self-hosting sGTM on Google Cloud (App Engine or Cloud Run)? This guide walks you through migrating to DataNostro — less config to maintain, predictable pricing, EU-only servers, and Czech-language server-side support.
Why migrate from GCP
- Pricing: Google Cloud sGTM runs $80–250 / month depending on traffic + egress. DataNostro starts at 990 CZK (~$42), no egress fees.
- Maintenance: App Engine Node version bumps, IAM roles, Cloud Logging quota — all on you. Not here.
- EU-only: single Frankfurt region. No US, no APAC. GDPR-friendly out of the box.
- Native CZ connectors: Sklik and Heureka outside GTM (direct server-side request).
Pre-flight checklist
- Owner / Editor access on the Google Cloud project running sGTM
- Access to your GTM sGTM workspace
- DNS control of the tracking subdomain
- Current App Engine / Cloud Run URL (e.g.
tagmanager-xyz.appspot.com) and custom domain
Step 1 — DataNostro account
Sign up, pick a plan. For reference: a F2 App Engine instance with 5 min-instances costs ~$80/mo = DataNostro STANDARD (990 CZK/mo).
Step 2 — Tracking domain
Same as Stape: add the domain in dashboard (e.g. track.yourshop.com), get the A/CNAME target, but don't flip DNS yet.
Step 3 — Export GTM container
GTM workspace → Admin → Export Container. Then DataNostro Containers → Import GTM, upload JSON. DataNostro deploys a Docker container with your config — no App Engine boilerplate, no Cloud Run cold starts.
Step 4 — Environment variables
If you have App Engine env vars (typically CONTAINER_CONFIG, RUN_AS_PREVIEW_SERVER=false, PREVIEW_SERVER_URL), DataNostro picks them up automatically from the GTM export. CONTAINER_CONFIG is embedded in the export JSON.
Step 5 — Preview server
If you ran a separate App Engine preview service, DataNostro gives you one for free with every container. No second instance, no double billing.
Step 6 — Test & cutover
- Send test event from the dashboard — verify per-platform response codes
- Lower DNS TTL → switch A/CNAME to DataNostro → verify with
dig - After 24 h: compare request count to GCP Cloud Logging
- After 48 h: delete the App Engine service / Cloud Run revisions, billing drops next cycle
How much you save
Real customer example (e-shop, ~5M requests / month):
| Line item | GCP App Engine | DataNostro |
|---|---|---|
| sGTM hosting | $95 | 2,990 CZK (~$127) |
| Egress (5M × ~2KB) | $24 | $0 |
| Logging quota | $8 | $0 |
| Engineer time / mo | $200 (2 h × $100) | $0 |
| Total | $327 | ~$127 |
~60 % savings + you stop maintaining a category of GCP-specific overhead (IAM, billing alerts, secrets manager).
FAQ
What about my Cloud Logging history?
Cloud Logging stays in your GCP project — export with gcloud logging if you want to keep it. DataNostro logs live in the dashboard (Activity) with 30-day retention.
I have Identity-Aware Proxy in front of sGTM
You shouldn't be using IAP on the public tracking endpoint (it would break web tracking). If IAP is only on an admin endpoint, you don't need it on DataNostro — admin is gated by the dashboard login.
My App Engine is in US-East, can't I just migrate?
That's a reason to migrate. EU servers cut latency for CZ/SK visitors by 80–120 ms and align you with GDPR data residency.