Server-side tagging is sold to US online stores as the fix for lost conversions, ad blockers and Apple's privacy changes. It does help with some of those. It also costs money every month, takes skill to run, and doesn't fix a broken setup underneath.
What it is.
Normally, each tag on your site sends data straight from the visitor's browser to Google, Meta, TikTok and the rest. With server-side tagging, the browser sends one stream of data to a server you control, usually on a subdomain of your own site. That server then sends what each platform needs.
What it fixes.
- Cookies that last. Safari limits cookies set by scripts to seven days. A customer who comes back after eight days looks new, and the campaign that first brought them loses the credit. A server on your own domain can set cookies that last longer, though browsers keep tightening the rules.
- Fewer blocked requests. Some blockers stop requests to well-known tracking domains. Data sent to your own subdomain is blocked less often, though not never.
- Control over what leaves. You can remove email addresses from page addresses, drop fields a platform doesn't need, and see exactly what each vendor receives.
- A faster site. Fewer scripts in the browser means less work for the visitor's device.
- Better matching for ads. Conversion APIs, such as Meta's, can be sent from the server alongside the browser pixel, with each event counted once.
What it doesn't fix.
- Consent. Server-side tagging is not a way round privacy law. If a visitor opts out, or the law requires a yes first, the server has to respect that just as the browser does. Using it to hide tracking from visitors is a fast route to a lawsuit, as covered in why US businesses are sued over tracking pixels.
- Bad data. If purchases are counted twice or revenue includes sales tax, a server sends those mistakes on faithfully.
- Missing events. The site still has to tell the server what happened. A weak dataLayer stays weak.
What it costs.
There are two costs. Hosting, either on a managed service such as Stape or on Google Cloud, grows with traffic. And someone has to set it up, test it and keep it running when platforms change their requirements.
For a store with steady traffic and real ad spend, the gain in measured conversions usually covers both. For a small store with little paid traffic, fixing the basics first is the better use of money.
Is it worth it for your store?
It's usually worth it when:
- you spend meaningfully on Meta, Google or TikTok and want them to see every sale they drove
- many customers use Safari on iPhones and Macs
- you need to control exactly what data reaches each vendor
Get the purchase data right first, then move it server-side. The best tracking architecture for a website shows where it fits.
Marc Alexander builds server-side GTM for US stores, and on Stape where that suits. The GA4 mini audit says whether your setup is ready for it.