What is server-side tracking and do you need it?

How is server-side GTM different from normal GTM?

With a normal web container, every platform loads its own script in the visitor's browser and sends data directly to its own domain. Ad blockers and privacy features recognise those domains and block or shorten them, so you lose conversions without noticing.

With server-side GTM, the web container sends events to a tagging server on a subdomain of your site, such as data.yourdomain.com. That server runs a second GTM container where clients receive the data and tags send it on to each platform. Because the request goes to your own domain, cookies are first party and far fewer requests are blocked.

When is server-side tracking worth the cost?

Server-side tracking has a monthly hosting cost and more moving parts, so it is not the first fix for every account. I usually recommend it when:

• You spend enough on Google or Meta that a few percent more matched conversions pays for the hosting many times over.
• You run ecommerce, especially Shopify, where checkout events are hard to capture reliably in the browser.
• You need offline conversions from a CRM, ServiceM8 or GoHighLevel, because the server container can receive webhooks as well as browser events.
• You want the Meta Conversions API, TikTok Events API or similar server events without paying for a separate app per platform.
• You need tight control over personal data for privacy or compliance reasons.

If basic web tracking is still broken, I fix that first. Server-side tracking cannot repair events that were never set up correctly in the browser.

How do I set up server-side tracking on Stape?

1. 1

   Audit the current tags

   List every pixel, conversion action and data layer event, and find what is duplicated, missing or misconfigured before anything moves.

2. 2

   Create the server container on a first-party subdomain

   Host the server-side GTM container on Stape, map a subdomain with a DNS record, and enable the Custom Loader so the GTM script itself loads from your domain.

3. 3

   Rebuild the data layer

   Send clean ecommerce or lead events with order IDs, values and user data. On Shopify this usually means a custom pixel instead of relying on app auto-detection.

4. 4

   Configure Consent Mode v2

   Respect the visitor's choices for ad storage, analytics storage, ad user data and ad personalisation, so the server only forwards what consent allows.

5. 5

   Connect each platform

   GA4, Google Ads conversions with Enhanced Conversions, Meta Conversions API with deduplication, plus other platforms as needed.

6. 6

   Validate against the source of truth

   Compare conversions with real orders in Shopify or real leads in the CRM over several days, not just the GTM preview.

Does server-side tracking get around consent rules?

No, and it should not be sold that way. Server-side tracking changes where the data flows, not whether you are allowed to collect it. A good setup reads the same consent state as your cookie banner and only sends ad data when consent allows. What it does fix is data that is lost for technical reasons, such as blocked third-party domains and short cookie lifetimes, even when the visitor has said yes.

What results should you expect?

Expect more complete and more trustworthy numbers, not a sudden jump in sales. Typical outcomes are fewer missing purchases in Google Ads, better event match quality in Meta, matching order IDs across platforms, and a faster site because fewer vendor scripts load in the browser. The bigger win is usually what bidding does over the following weeks once it gets better data.