In brief
- Server-side tracking becomes useful when you buy advertising optimised on conversions and at least one other situation applies: a purchase cycle longer than a week, the need to send margin, the wish to filter what leaves your site, figures that no longer reconcile.
- It is not a way past ad blockers. On 14 October 2026 we tested twelve measurement URLs against that day’s EasyPrivacy list: a tagging server installed on your own subdomain but keeping Google’s paths is blocked just like Google itself, three times out of three.
- The same list contains 35,621 rules naming measurement subdomains disguised as the site’s own domain, across more than 21,000 domain names.
- What it really brings: cookies that last more than seven days on Safari, a more complete conversion signal for Meta and Google, and control over what leaves, field by field.
- It never removes the need for consent, and it costs at least one server to monitor.
Server-side tracking stops being a luxury when your ad campaigns optimise on conversions the browser no longer sees in full: a purchase cycle longer than seven days on Safari, sales to be linked to a margin, platforms asking for a server feed alongside the pixel. It remains a luxury if your only argument is getting past ad blockers: our test of 14 October 2026 shows that a standard setup is blocked just like the pixel it replaces.
How we checked On 14 October 2026 we ran twelve measurement URLs (Google, Meta and TikTok scripts and hits, a tagging server on a subdomain, a site’s own collection endpoint) through Brave’s open-source filtering engine, loaded with EasyList, EasyPrivacy (version of 13 October 2026, 23:05 UTC) and the uBlock Origin lists. We then counted, in EasyPrivacy, the rules in the sections dedicated to disguised measurement subdomains. Safari’s cookie rules, Meta’s recommendation and the cost given by Google come from their official documentation, read the same day. Sources are listed at the end of the article.
What does server-side tracking actually change?
In a classic setup, the visitor’s browser loads the Google, Meta or TikTok scripts and sends each event to them itself. With server-side, the browser sends events to your server, which then relays them to each platform. Two legs instead of one: from the browser to your server, then from your server to the platforms.
The second leg is out of the browser’s reach: that is where you add margin, remove a field, attach a refund. The first leg remains a browser request like any other, and that is where the ad blocker question is decided.
Does server-side get past ad blockers?
Not in its most common configuration. Here is what our test gave, all lists combined.
| URL tested | Result | Blocking rule |
|---|---|---|
| Google Analytics, Google Tag Manager, Meta pixel and TikTok pixel scripts and hits (6 URLs) | Blocked, 6 out of 6 | Rules targeting the platforms’ domains |
Tagging server on your subdomain, Google’s paths kept (/gtm.js, /gtag/js, /g/collect) |
Blocked, 3 out of 3 | Generic rules on the path, whatever the domain |
| Tagging server with renamed paths, site’s own collection endpoint (3 URLs) | Pass, 3 out of 3, on that day | None |
Two lessons. First, moving Google onto your subdomain without changing its paths changes nothing for a blocker: the rule targets /gtm.js or /collect?v=, not the server’s address. Second, what passes today may not pass tomorrow. EasyPrivacy updates every few days, and its 13 October version contains 35,621 rules, spread over twenty sections, that name measurement subdomains set up under the site’s name, across more than 21,000 domain names. The lists add sites one by one.
Above all, there is a reason of principle not to build a project on this: a visitor who installs a blocker is expressing a choice. Server-side is for measuring properly the visitors who accepted measurement, not for measuring those who made it clear they did not want it.
So when is server-side worth its cost?
Our rule: the first of the following five situations, plus at least one other.
1. Your campaigns optimise on conversions. Meta’s and Google’s bidding algorithms learn from the conversions they receive. Meta itself recommends implementing its Conversions API “alongside” the pixel, in a setup it calls redundant, with a shared event identifier for deduplication. If you only do brand awareness or organic search, this argument falls away.
2. Your purchase cycle is longer than seven days, and some of your visitors use Safari. Since 2019, Safari has capped at seven days the lifetime of cookies created by a script in the page, the ones classic measurement tools use. A customer who comes back to buy ten days later becomes a new visitor, and the campaign that brought them loses the sale. A cookie set by your own server, in the HTTP response, is not covered by this rule. Watch the setup: since 2020, Safari applies the same seven-day cap to cookies set by a third-party server simply hidden behind a subdomain of the site. The server must genuinely be yours.
3. You want to send margin, not just revenue. The browser does not know your purchase cost, and should not. The server does. That is the condition for steering your campaigns on margin, as in our method for building the POAS column in Google Ads, and for removing refunded sales from a campaign.
4. You want to know, and decide, what leaves your site. With a pixel, the platform’s script chooses what it collects from the page. With a server, you filter field by field and keep a record of what was sent. It is a compliance argument as much as a quality one.
5. Your figures no longer reconcile. If the sales counted by GA4, by Google Ads and by your back office diverge with no explanation, going through the server lets you link each conversion to a real order, provided you then monitor that reconciliation. We described in your tracking may be lying in silence what happens when nobody does.
When it is not the right investment
- You do not buy advertising on conversions. A well-configured consent-exempt audience measurement is usually enough, for far less.
- Your problem is consent. If most of your visitors refuse measurement, server-side changes nothing: without agreement, nothing should be sent, through the browser or through the server. Our article on audience measurement without consent explains why.
- Nobody will be able to monitor it. A measurement server that goes down does not bring the site down: conversions disappear silently. Without alerts and without reconciliation against orders, you have added an invisible point of failure.
How much does it cost?
For a tagging server hosted by Google, its documentation gives about 45 dollars per month per server in the default configuration, and recommends running at least two to limit the risk of data loss if a server fails, so about 90 dollars per month in hosting. Managed offers exist, billed by event volume. In both cases, the biggest cost is elsewhere: the initial configuration, deduplication with what the browser still sends, and ongoing monitoring.
How to decide in an hour
- List your ad platforms and check which ones optimise on conversions.
- Measure your purchase delay: the share of orders placed more than seven days after the first visit.
- Look at Safari’s share of your visits, on desktop and mobile.
- Compare over a month the sales in your back office, in GA4 and in your ad platforms.
- Decide who will monitor the setup once in place, before installing it.
What our test does not tell you It covers filter lists, not every blocker or every browser, which do not all enable the same lists. It gives the state on 14 October 2026: lists change every few days. Nor does it measure the share of your own visitors who use a blocker.
What this says about the bigger picture
Server-side is often sold as a workaround: for blockers, for browsers, sometimes even for consent. That is the wrong reason, and our test shows it does not last. The right reason is more mundane and more durable: taking back control of the data you send to your platforms, enriching it with what only you know, and checking it against your real orders.
That reconciliation between what the tools say and what was actually sold is at the heart of our data, analytics and performance expertise.
Sources
Pages opened on 14 October 2026.
- EasyPrivacy, version 202610132305 (13 October 2026, 23:05 UTC), sections
easyprivacy_specific_cname_*and generic rules/gtm.js,/gtag/js?,/collect?v=. View - Brave’s filtering engine (adblock-rust), used through its Python binding
adblock0.6.0. View - WebKit, “Intelligent Tracking Prevention 2.1”, February 2019: cookies created through
document.cookiecapped at seven days. View - WebKit, “CNAME Cloaking and Bounce Tracking Defense”, 12 November 2020: cookies set by a third-party server hidden behind a subdomain capped at seven days. View
- Meta for Developers, “Handling duplicate Pixel and Conversions API events”. View
- Google for Developers, “Set up server-side tagging with Cloud Run”, updated 12 May 2026: about $45 per server per month, at least two instances recommended. View
FAQ
Does server-side tracking get past ad blockers?
Not in its most common configuration. On 14 October 2026, a tagging server installed on the site’s subdomain but keeping Google’s paths (/gtm.js, /gtag/js, /g/collect) was blocked three times out of three by the EasyPrivacy list, which also contains 35,621 rules naming measurement subdomains. And a visitor who installs a blocker is expressing a choice that should be respected.
When should you move to server-side?
When your campaigns optimise on conversions and at least one other situation applies: a purchase cycle longer than seven days with some visitors on Safari, the need to send margin, the wish to filter what leaves, or figures that no longer reconcile between GA4, your platforms and your back office.
Does server-side remove the need for consent?
No. It changes the data’s path, not the nature of the processing. Without consent, nothing should be sent to an ad platform, whether through the browser or through your server.
How much does a tagging server cost?
Hosted by Google, about 45 dollars per month per server according to its documentation, with at least two servers recommended, so about 90 dollars per month. Configuration, deduplication and monitoring cost more than the hosting.
Can Dotsland help?
Yes. We run the one-hour diagnosis described above with you, then, if server-side is justified, the tagging plan, deduplication and reconciliation with your orders. Start with the list above, then get in touch.