Server-side tagging (a server-side GTM container, or similar) moves your tracking off the browser and onto a server you control. It fixes real problems like ad blocker data loss and iOS tracking gaps, but it also adds cost and maintenance. Answer 6 questions below to get a straight answer for your setup.
The 6-question check
How to use this calculator
Answer each of the 6 questions based on your current setup, not where you hope to be in a year. Traffic volume and ad spend carry the most weight, since server-side tagging pays off fastest for sites with real data loss to recover and enough ad spend for accuracy to matter. Click See my result and you'll get a score plus the specific reasons behind it, so you know exactly what's driving the recommendation.
How server-side tagging actually works
Normally, a tag like Google Analytics or the Meta Pixel fires directly from the visitor's browser to the vendor's servers. Ad blockers, browser privacy features, and iOS's Intelligent Tracking Prevention (ITP) are all designed to catch and block exactly this kind of third-party request.
A server-side setup adds a step in between. The browser sends the event to a server you control, usually hosted on your own subdomain, and that server forwards the data on to GA4, Google Ads, Meta, or wherever else it needs to go. Because the first request comes from your own domain, it's treated very differently by browsers and blockers, so far less of it gets dropped.
It's not free, though. You're paying for and maintaining a small piece of server infrastructure, and someone needs to keep the tag configuration in sync. That's why this only makes sense once the data loss you're recovering is worth more than the setup and upkeep cost.
Frequently asked questions
What's the difference between client-side and server-side tagging?
Client-side tagging fires tracking requests straight from the visitor's browser. Server-side tagging routes those same events through a server you control first, which makes them far less likely to be blocked by ad blockers or browser privacy features.
How much does server-side tagging cost to set up?
Costs vary by traffic volume and complexity, but most setups involve hosting a small server container plus developer time to configure and test it. Ongoing hosting is usually modest; the bigger cost is the initial setup and any future maintenance.
Will server-side tagging fix all my data loss?
No. It significantly reduces data loss from ad blockers and browser tracking prevention, but it can't recover data a visitor actively opted out of, and it doesn't replace proper consent management.
Do small websites need server-side tagging?
Usually not yet. The setup and maintenance cost is hard to justify until you have enough traffic or ad spend that the recovered data is worth more than the ongoing upkeep.
Does server-side tagging help with GDPR or CCPA compliance?
It can help, since it gives you one place to filter, hash, or drop data before it reaches third-party vendors. It's a useful piece of a compliance strategy, but it's not a substitute for proper consent management.
What tools are used for server-side tagging?
A common setup is a server-side Google Tag Manager container, hosted on Stape (this is my preferred set-up) or on Google Cloud Platform, though other tag management and hosting combinations exist.