GTM (web) runs in the browser. sGTM runs on the server. Both do the same thing — receive an event and send it to the platforms — but the latter is resistant to ad-blockers, ITP, and privacy modes.
When web GTM is enough
- The site has under 50k visits/month.
- Your main advertising is via SEO/Sklik (relatively tolerant).
- You don't use lookalike audiences, retargeting, or CAPI.
- Most visits are from desktop Chrome / Firefox without an ad-blocker.
When you need sGTM
- You advertise on Meta / TikTok / Google Ads and want full attribution.
- A large share of visits is from Safari (iOS) — ITP deletes your cookies.
- You need Consent Mode v2 (EU) without losing attribution signals.
- You want data-driven attribution in Google Ads — it requires >50 conversions/month.
- You target recurring revenue (subscriptions) and want purchase events from Stripe webhooks.
What changes after switching
We build you a container under your subdomain (e.g. track.store.cz),
connect the same tags as in GTM (GA4, Meta, Ads, Sklik), but dispatch them
via server-side tag templates. You no longer send the Pixel from the browser —
instead you send one event to your track endpoint and it fans out.
The DataNostro Care Standard package covers this in 5-7 days with none of your time — we build it, test it, and hand it over finished.