Case study:
HIGH END SHOPIFY BRAND

How Server-Side GTM Restored Attribution Across a Multi-Domain Store to reduce cost-per-aquisition and regain control of long-lost attribution and ad performance.

High growth shopify brands which operate cross-channel often require a more complex tracking set-up. This is to ensure complete attribution and minimise the risk of lost data.

Marketing for cross-domain shopify store

Key Journey

For this specific client, a premium Shopify e-commerce store operating across multiple domains; modern privacy regulations and cross-domain journeys created a series of analytical blind spots.

  1. UTMs disappearing between domains

  2. Click IDs (gclid, fbclid) being dropped

  3. Paid media appearing to underperform

  4. New vs returning customer analysis becoming unreliable

This case study shows how implementing server-side Google Tag Manager and GA4 restored attribution, unlocked funnel clarity, and enabled incrementality analysis across domains.

The Problem: Cross-Domain Shopify Tracking Breaks Attribution

The client’s user customer journey looks simple on the surface: a user clicks an ad, lands on their website and proceeds to their shop (shop.client.com). But behind the scenes this setup was quietly breaking their data.

What Was Going Wrong?
When the users moved from the main site over to the shopify, or naviaged through a purchase journey on the same domain they often lost:

  • UTM parameters
  • Click IDs
  • GA4 treated users as new sessions / new users
  • Paid conversions were misattributed to Direct or Organic

This issue often occurs with multi-domain shopify stores, client-side only GA4 setups and browser based tracking under modern privacy rules

WHY DO CLICK ID's matter more than ever?

Click IDs (like gclid, fbclid, ttclid) are a backbone of modern attribution.

When they’re lost:

  • Google Ads can’t optimise properly
  • Meta struggles with conversion modelling
  • Incrementality testing becomes unreliable
  • New vs existing customer cohorts blur together

In this client’s case, click IDs were being dropped at the exact point users crossed domains.

The solution: server-side tracking

Server-side tracking allowed us to overcome this, as it’s designed specifically for cross-domain tracking

We deployed:

  • Server-Side Google Tag Manager
  • GA4 configured server-side
  • First-party cookie storage
  • Cross-domain parameter persistence
  • Unified measurement across domains

All events were routed through a single server-side endpoint, allowing data to be:

  • Cleaned
  • Normalised
  • Persistent across domains
Server side tracking explained

How server side tracking solves cross-domain attribution

Server-side tracking fixes cross-domain attribution by moving data collection and identifying resolutions away from the browser and into a single, central server-side Google Tag Manager container.

As shown in the example diagram above, all Shopify storefronts (Store A, Store B), the main brand website, and partner or collaboration sites send their events to one server-side endpoint rather than firing tags independently in the browser.

This allows click IDs, UTMs, and first-party identifiers to be captured once and then persisted consistently across domains, even as users move between sites. Instead of losing parameters during cross-domain navigation.

The server-side GTM acts as the source of truth normalising events, maintaining session continuity, and forwarding clean, unified data into a single GA4 property. The result is accurate attribution, reliable new vs returning customer analysis, and a complete view of the funnel across every domain in the ecosystem.

Results and Impact

How to have a multi-domain tracking model?

Once server-side tracking was live:

  • UTMs persisted correctly between domains
  • Click IDs were retained through checkout
  • GA4 sessions remained intact
  • Paid media attribution stabilised
If  you’d like to check out the impact of server-side tracking on ROAD and Cost Per Acquisition check out our skincare e-commerce brand case study.

Unlocking Funnel & Incrementality Analysis

With clean, server-side data sending to GA4, the client could finally:

  1. Analyse True Customer Journeys
    Landing page → education → product → checkout. Without session resets between domains
  2. Separate New vs Existing Customers Reliably. With Accurate cohorting; Better LTV modelling; Cleaner CAC calculations
  3. Diagnose Incrementality. Understand which channels were truly driving new customers. Overall, Reduce wasted spend on non-incremental traffic

This allowed them to make confident media decisions

This level of clarity is impossible with broken client-side tracking alone.

Why Server-Side Tracking Is Essential for Multi-Domain Shopify Stores

For brands operating across: multiple domains; international storefronts; hybrid shopify setups. 

Client-side tracking is no longer enough to capture the full picture. With server-side tracking you own your own data; transfer identifiers across domains; protects measurements from browser restrictions; ensure a complete attribution path. 

Server-side tracking allows you to build a future-proof marketing strategy fuelled by accurate, clean data.