Skip to main content
TrackingConsultingFree audit
Server-Side GTMServer-side GTM

Get your Server-Side GTM tracking to 95%+ accuracy guaranteed in writing.

iOS, Safari ITP, ad blockers, consent banners — every single one of them eats browser-side tags. The only setup that survives is server-side. We deploy sGTM on your subdomain in 5 days, wire CAPI / Enhanced Conversions / GA4 / TikTok, and hand over a runbook your team can extend without us.

Get my free conversion tracking auditSee what we check

Free30 minutesNo obligation

By Ariful IslamHow Server-Side GTM works ↓

Server-Side GTM · what breaks

Why you need sGTM — Server-Side GTM

  1. 01

    Browser tracking is half-blind

    iOS + ad blockers.

  2. 02

    Vendor lock-in

    Stape only is fine, but ownership matters at scale.

  3. 03

    Latency / Core Web Vitals

    Heavy front-end pixels hurt LCP/INP.

  4. 04

    GDPR data residency

    EU traffic should stay in EU.

Server-Side GTM · the fix

Outcomes — Server-Side GTM

  • Subdomain sGTM live

    data.yourdomain.com

  • All major destinations wired

    Meta / Google / TikTok / GA4 / others

  • Better Core Web Vitals

    Lighter front-end stack

  • EU residency option

    If needed

Server-Side GTM · architecture

What a server-side GTM setup actually looks like once it is running

Server-side tagging does not remove the browser. It moves the decision about what leaves your site, and who it goes to, out of the visitor's browser and onto infrastructure you control.

  1. 1

    The browser sends one request, to your own domain

    Instead of a dozen vendor scripts each opening their own connection, the page sends events to a subdomain of your site — tracking.yourdomain.com, or similar. One request, first-party, on your certificate.

  2. 2

    A server container receives and enriches it

    The container runs your tagging logic on a server rather than in the page. It can read the order from your backend, add hashed customer data, and drop anything that should not leave.

  3. 3

    Cookies are set server-side with a real lifetime

    A cookie written by your own server in an HTTP response is not subject to the seven-day cap Safari's ITP applies to cookies written by JavaScript. This is the single largest practical gain.

  4. 4

    The container fans out to each destination

    Meta CAPI, Google Ads, GA4, TikTok, Microsoft, LinkedIn — each gets exactly the fields it should have, no more. The visitor's browser never talks to any of them.

  5. 5

    Consent decisions are enforced before the fan-out

    A blocked destination is blocked at the container, not by hoping a vendor script honors a flag. That is a materially stronger compliance position than client-side gating.

Server-Side GTM · events

What moves to the server, and what stays in the browser

Not everything belongs server-side. Interaction signals need the browser. Money needs the server. Here is how we split it.

Page viewBoth, dedupedBrowser gives speed and referrer; server gives durability against blocking
Scroll, clicks, video, engagementBrowser onlyThese exist only in the page and have no server-side truth to draw on
Add to cart, begin checkoutBoth, dedupedCart state is known in both places; the server copy survives blocking
PurchaseServer authoritativeThe order exists in your backend whether or not the browser survived the redirect
Refunds and cancellationsServer onlyThere is no browser session when a refund is issued days later
Subscription renewalsServer onlyNo visitor is present at all
Qualified lead, closed dealServer onlyThe event happens in your CRM, weeks after the session ended
Hashed customer identifiersServer onlyNever expose them to the page, where any script on the site can read them

Server-Side GTM · diagnose

How we work out whether server-side is your actual problem

Server-side tagging fixes a specific set of failures. Running it before you know which failure you have is how people spend money and see nothing change.

  1. 01

    Measure the real gap first

    Reconcile one fully closed week of backend orders against each ad platform. If the gap is small, the problem is elsewhere and server-side will not move it.

  2. 02

    Establish how much traffic is Safari and iOS

    ITP's seven-day cookie cap is the mechanism server-side cookies defeat. The more of your traffic sits behind it, the larger the gain.

  3. 03

    Check whether the browser events are even correct

    Moving a broken event to a server produces a broken server event. Correctness first, then durability.

  4. 04

    Identify every existing tracking path

    Theme-hardcoded tags, platform apps, partner integrations, an old container. All of them keep running after the server container goes live unless they are deliberately removed.

  5. 05

    Confirm you can reach order data server-side

    A webhook, an API, or a datalayer with real order fields. Without a backend source of truth, a server container is just a proxy.

  6. 06

    Decide hosting before building

    Cloud Run, Stape or self-hosted all work. Cost, data residency and who holds the keys differ, and that decision is easier before the tags exist than after.

Server-Side GTM · prove

How we prove a server-side container is doing its job

The container responding to requests proves it is alive. These prove it is working.

Source of truth

Backend order records for ecommerce, CRM stage records for lead generation

  • The tagging subdomain resolves to your own certificate, with a valid CNAME and no mixed-content warnings.
  • First-party cookies set in an HTTP response header, with a lifetime beyond seven days, confirmed in Safari specifically.
  • Purchase events arriving server-side within a few percent of backend orders for a fully closed week, matched on order ID.
  • Deduplication confirmed at every destination that supports it, not just Meta.
  • Every legacy firing path removed or deliberately kept, documented either way.
  • Consent blocking verified by denying consent and confirming nothing leaves the container.
  • Container response times and error rates monitored, so a silent failure surfaces as an alert.

Server-Side GTM · free audit

What we check in the free audit

  • Measure the real gap first
  • Establish how much traffic is Safari and iOS
  • Check whether the browser events are even correct
  • Identify every existing tracking path
  • Confirm you can reach order data server-side
  • Decide hosting before building

Checked against

Backend order records for ecommerce, CRM stage records for lead generation

Get my free conversion tracking audit

Free30 minutesNo obligation

Server-Side GTM · when not to buy

When server-side tagging is not worth it

This is the service we most often talk people out of, because the case for it is narrower than the industry suggests.

  • You spend under roughly $5,000 a month across all paid channels. The monthly hosting and the build cost will outrun the recovered signal.
  • Your client-side tracking has never been audited. Fix and verify what you have; a meaningful share of accounts need nothing more.
  • Almost none of your traffic is Safari or iOS. The main mechanism server-side defeats barely applies to you.
  • You have no backend order source the container can read. Without it you get a proxy, not a source of truth.
  • Nobody on your side will own it. A server container is infrastructure. It needs monitoring and someone who notices when it breaks.

Server-Side GTM · what we deliver

Deliverables — Server-Side GTM

  • sGTM container

    Stape Pro / self-hosted GCR

  • Custom subdomain DNS

    Configured & SSL

  • All destination tags

    Meta CAPI / Google EC / GA4 / TikTok

  • QA + Notion runbook

    Plus 30-day support

Written guarantee

95%+ tracking accuracy

Measured against Backend order records for ecommerce, CRM stage records for lead generation. Miss it and we keep working at no cost.

Get my free conversion tracking audit

Pricing

Pick the package that fits your ad spend

sGTM — Starter

$400one-time setup

Stape-hosted sGTM with 1 channel wired (Meta CAPI or Google EC). Right when you're testing server-side for the first time.

  • Stape Pro container
  • Custom subdomain + SSL
  • 1 channel wired (Meta or Google)
  • Live-fire QA
  • 30-day support
Start with starter

sGTM — Recommended

Recommended

$800one-time setup

Production sGTM with all major channels wired (Meta + Google + TikTok + GA4) and dedup discipline. The standard.

  • Stape Pro or self-hosted
  • Custom subdomain + SSL
  • Meta CAPI + Google EC + TikTok + GA4
  • Browser ↔ server dedup
  • Notion runbook
  • 30-day support
Get the recommended package

sGTM — Enterprise

$1,800one-time + optional retainer

Self-hosted sGTM (your GCP/AWS), EU + US regions, all major CAPIs, BigQuery, Looker dashboard, and 90-day support.

  • Self-hosted on your GCP/AWS
  • EU + US regions
  • Meta + Google + TikTok + Pinterest + Snap
  • BigQuery export + Looker dashboard
  • Quarterly health check
  • 90-day support
Get enterprise scope

FAQ

Server-Side GTM questions, answered

Stape for speed-to-launch. Self-hosted for cost at scale (>10M req/mo).

More on Server-Side GTM

Free · 30 min

Get a free sGTM scoping call

Book a scoping call WhatsApp

Free30 minutesNo obligation