Server-Side Tracking Explained for Ecommerce: What It Is and Whether You Need It
Joshua Gewargis · 18 October 2026 · 9 min read
If your Google Ads or Meta reports show fewer sales than your store, you are not imagining it. Browser-based tracking loses some conversions, and the platforms optimise on whatever they can see.
Server-side tracking is the usual fix. This guide explains how it works, how to tell whether you need it, and what it takes.
How normal tracking works, and where it leaks
With standard tracking, a snippet of code runs in the shopper's browser and sends purchase and behaviour events straight to Google, Meta and others. That has several weak points:
- Ad blockers and privacy browsers can stop the snippet or block its requests.
- Browsers such as Safari limit how long tracking cookies last, so a returning shopper can look like a stranger.
- Slow pages, closed tabs and failed requests mean some events never arrive.
What server-side tracking changes
With a server-side setup, the browser sends events to a server you control, on your own domain. That server then forwards them to Google, Meta and other platforms. Because the request goes to your own domain, it is far less likely to be blocked, and cookies can be set from your server with longer lifetimes.
- More of your real purchases reach the ad platforms.
- Better matching of ads to sales means smarter bidding.
- You control exactly which data leaves your site.
How to check whether you are losing conversions
- Compare orders in your store for last month with conversions in Google Ads and in GA4.
- Expect some gap, since attribution windows and consent affect the numbers. A large, consistent gap is the signal.
- Look at the share of purchases attributed to direct or unassigned traffic, which often rises when tracking is leaking.
- In Google Ads, check the status of your conversion actions and enhanced conversions.
What it takes to set up
Typically a server-side Google Tag Manager container is hosted on a service such as Stape, your tags are connected to it, and a custom domain is pointed at it so tracking runs on your own address. Purchase events from your store are sent through it, and Meta and Google Ads receive them with the extra matching data they need.
The hosting cost is modest and is based on how many requests you send. The larger cost is the setup work and testing, which is why many stores have it done for them.
Privacy and consent still apply
Moving tracking to a server does not remove your obligations. You still need to respect the consent choices your visitors make and describe what you collect in your privacy policy. Server-side tracking gives you more control over data, not permission to ignore it.
TrueTag sets up and manages server-side tracking for ecommerce stores, so your ad platforms see the sales you actually made.