Server-Side Tagging · Shopify Specialist
Server-Side Tracking, Done Properly
Browsers don't like tracking any more. Safari bins cookies after seven days, ad blockers strip pixels out, and Shopify runs your checkout tags in a sandbox. Server-side tracking sends events from your own server instead of the shopper's browser, so your numbers stop quietly falling apart. If GA4 and Shopify have been drifting further apart every month, this is usually part of the answer.
20+
Years Experience
100+
Clients Helped
5.0
Google Rating
First-Party DataFrom Your Own Domain
Evidence > GuessworkHow I Work
What Server-Side Tracking Actually Is
Normally your tracking runs in the shopper's browser, the GA4 tag, the Meta pixel, all of it. The browser is hostile territory now. With server-side tagging, the browser sends one event to a container on your own domain, and your server forwards it on to Google, Meta and anyone else who needs it. Same data, much sturdier route. Here's what that fixes.
GA4 Undercounting
GA4 quietly misses orders that Shopify counts, blocked tags, sandboxed checkouts, lost sessions. Sending purchases from the server closes most of that gap. Why GA4 doesn't match Shopify.
Meta Match Quality
The Conversions API sends purchase events with properly hashed customer data, which pushes your Event Match Quality up and your cost per result down. More on Event Match Quality.
Short Cookie Lifetimes
Safari caps cookies set by JavaScript at seven days, sometimes 24 hours. So a customer who buys in week two looks like a brand new visitor. Cookies set the right way from your own server can last far longer, so returning customers stay attributed.
Ad Blockers
A decent chunk of shoppers run an ad blocker, and the first thing it does is bin your pixels. A tag served from your own domain is far less likely to get stripped out. Those sales were always happening, you just couldn't see them.
Google Ads Conversions
Smart Bidding is only as clever as the conversion data you feed it. A server-side setup gets more of your real conversions back into Google Ads, so the bidding stops flying half blind.
Fewer Scripts, Faster Pages
Every vendor pixel you move to the server is one less third-party script slowing your storefront down. Your customers get a faster site, and the vendors still get their data.
What's Involved on a Shopify Store
This isn't an app you install and forget. It's a small piece of infrastructure, built once, that everything else runs through. Four main parts.
First-Party Tagging Domain
A subdomain of your own store, something like track.yourstore.com, so your tracking data flows through a domain the browser actually trusts, not a third-party one it's trying to block.
Server GTM Container
A Google Tag Manager container running on a small cloud server. This is where the forwarding logic lives, one event in, clean copies out to GA4, Google Ads, Meta and whoever else.
Checkout Event Relay
Shopify's checkout runs custom pixels in a locked-down sandbox, which is where most tracking quietly dies. Purchase events get relayed properly, with transaction IDs so nothing counts twice. Especially important since the Checkout Extensibility migration.
Custom Loader
The tagging script itself gets served from your own domain rather than Google's. It's the difference between a setup that ad blockers ignore and one they bin on sight.
20+
Years Experience
100+
Clients Helped
5.0
Google Rating
1st
Party Tagging
When You Don't Actually Need It
Plenty of people will sell you server-side tracking whether you need it or not. Honest answer: some stores don't. Here's when I'd tell you to keep your money.
You're a Smaller Store
If you're doing a handful of orders a day and spending a few hundred pounds a month on ads, the hosting cost and added complexity probably isn't worth it yet. Get the client-side basics right, come back when the numbers justify it.
Your Basics Are Broken
Server-side tracking on top of a broken setup just delivers wrong numbers more reliably. If events are duplicated, missing or misfiring, that gets fixed first. That's exactly what the tracking audit is for.
You're Expecting a Miracle
Server-side tracking doesn't create sales, it recovers data about sales you're already making. If the real problem is the ads or the offer, better measurement just tells you that with more confidence.
What It Costs
Two costs to know about, and only one of them goes to me.
Running costs. The server GTM container needs a small cloud server, which typically runs somewhere between £20 and £100 a month depending on your traffic. That goes to the hosting provider, not me, and it's yours, you keep it whether we work together forever or not.
The build. My fee is a fixed project price, agreed up front before any work starts. Every store's setup is different enough that a number on a page would be a guess, and this whole section of the site is about not guessing. Start with a tracking audit and I'll quote from what it finds.
How It Works With Me
No mystery, no drip-fed deliverables. Four steps, in this order, every time.
1
Start With a Tracking Audit
I don't build server-side tracking blind. The audit shows exactly what's broken, what's double-counting and whether server-side is even the right fix for you.
2
A Fixed Price Up Front
You get a written scope and a fixed project price before anything starts. No day-rate meter running, no surprise invoices.
3
The Build
Tagging domain, server container, checkout event relay, custom loader. Built on your accounts and your infrastructure, so you own all of it.
4
Verify Against Reality
I run the new setup alongside the old numbers and against Shopify's own order data before anything gets trusted. Evidence, not guesswork, it's how I found a store reporting growth that didn't exist.
Questions People Ask
Here are the ones I get most often. If yours isn't here, just ask.
Maybe not. If you're spending serious money on ads and your platforms disagree with Shopify by 20% or more, probably yes. If you're a smaller store with a tidy client-side setup, the running costs may not be worth it yet. A tracking audit will tell you which camp you're in before you spend anything on a build.
It helps, honestly it does, longer-lived cookies and better match rates recover a good chunk of what Safari throws away. But nothing turns the clock back to 2019. Anyone promising you'll see every single iOS conversion again is selling something.
No, and it shouldn't. Consent choices pass through to the server container and get respected, same as they would in the browser. If your conversions fell off a cliff when your cookie banner went in, that's usually a consent mode configuration problem, which is a different fix.
The build itself is days, not months. What takes the time is getting DNS access sorted, agreeing what fires where, and verifying the numbers side by side before switching over. A couple of weeks end to end is typical for a Shopify store.
Hosting for the server container is typically £20 to £100 a month depending on traffic, paid straight to the hosting provider. My build fee is a fixed project price agreed up front, no meter, no surprises.
Yes, and it usually goes smoothly, developers tend to like working with someone who reads the raw requests rather than pointing at a dashboard. I'll handle the tagging side, they keep the theme and the store, and everything gets documented so nobody's guessing later.
Let's Have a Chat
Drop me a message or give me a ring. No hard sell, just an honest conversation about whether server-side tracking is actually worth it for your store.
More Than Just the Plumbing
Server-side tracking is one piece of getting your measurement straight. If you're not sure where your setup is going wrong, the tracking audit is the place to start, and if GA4 itself is the mess, I offer GA4 help too. If your Meta pixel shows connected but tracks nothing, that's a common one as well.
Once the data's trustworthy, I can put it to work: Google Ads, Facebook advertising and ecommerce PPC. Based in Abergele, North Wales, working with Shopify stores across the UK.