Do I need server-side tracking?
Five checks you can run yourself in about five minutes, using accounts you already have. If the checks come back clean, your tracking is fine and you should not spend money fixing it. That outcome is a real result, not a failed sales page.
Last reviewed July 2026 by Eptekhar Hasan
The problem, in one paragraph
A normal Meta Pixel or GA4 tag runs inside the visitor's browser. Ad blockers, Safari's tracking prevention, iOS privacy settings and cookie banners can all stop it before it sends anything. When that happens the sale still goes through, but Meta and Google never hear about it. Your ads then optimise on partial data and your reports understate what is actually working. Server-side tracking sends the same event from a server instead, so a much larger share of it gets through.
The 5-minute check
01 Compare last month's revenue in two places
Open your store's own sales report for last month. Then open GA4, go to Reports, Monetisation, Overview, and set the same date range. Write both totals down.
Warning sign
GA4 is more than 10% below your store total.
Healthy
The two are within about 5% of each other.
02 Check your Meta event match quality
Open Meta Events Manager, select your Pixel, open the Overview tab and find the Purchase event. Meta scores it out of 10.
Warning sign
Score below 6.0, or no score shown at all.
Healthy
Score of 7.0 or above.
03 Count purchases in Meta against real orders
In Events Manager, look at how many Purchase events arrived in the last 7 days. Compare that to the real order count in your store for the same 7 days.
Warning sign
Meta received noticeably fewer purchases than you actually had.
Healthy
The two counts are close, within a small margin.
04 Look for the opposite problem, double counting
Still in Events Manager, check whether Meta flags any events as duplicates, or whether reported conversions look higher than your real order count.
Warning sign
Meta reports more purchases than your store did.
Healthy
No duplicate warnings, and the counts line up.
05 Check whether consent is actually handled
If you sell to the EU or UK and show a cookie banner, check whether a consent state is passed to your tags, or whether they simply fire for everyone regardless.
Warning sign
Tags fire the same way no matter what the visitor clicks.
Healthy
Consent Mode is configured and respected.
Reading your result
No warning signs
Your tracking is in good shape. You do not need server-side tracking right now, and you should not pay anyone to add it.
One warning sign
Usually a single broken tag or a missing parameter. This is a small fix, not a rebuild. Server-side tracking would be overkill.
Two or more
Data is genuinely leaking. Server-side tracking addresses the root cause instead of patching symptoms, and it is worth the monthly hosting cost.
What it takes, if you decide to go ahead
Access, not passwords
Google Tag Manager, GA4 and Meta Business Manager access, granted as an invite or a partner request. Nobody needs your login details.
One DNS record
A single CNAME for a tracking subdomain on your own domain, for example track.yourdomain.com. This is what makes cookies first-party.
A hosting account
The server container runs on Stape or your own Google Cloud project, billed to you from roughly $20 per month. It is never part of a setup fee, and you should be suspicious of anyone who does not mention it upfront.
Two to four days
A realistic window for setup, testing and a written verification report. Anyone promising it in an hour is skipping the testing.
When you should not do this
Server-side tracking is not right for everyone. If you run little or no paid advertising, the benefit is small and the monthly hosting cost is not worth it. If only one of the five checks failed, you probably have a single broken tag, and paying for a full rebuild would be waste. We would rather tell you that than sell you a setup you do not need.
Send us your site and we will tell you which case you are inCommon questions
What is server-side tracking, in plain terms?
A normal Meta Pixel or GA4 tag runs inside the visitor's browser. Server-side tracking moves that job to a server you control, usually a server-side Google Tag Manager container. The browser tells your server what happened, and your server tells Meta and Google. Because the second step never touches the visitor's browser, ad blockers and browser privacy settings cannot stop it.
Why does browser-only tracking lose conversions?
Ad blockers, Safari's Intelligent Tracking Prevention, iOS privacy settings and cookie banners can all block or shorten browser tags before they send anything. The sale still happens, but the ad platform never hears about it, so your reported conversions are lower than your real ones.
Will server-side tracking double count my conversions?
Not if it is set up correctly. The browser event and the server event carry the same event_id, which is how Meta recognises them as one conversion and deduplicates them. If your reported conversions jump above your real order count after a setup, deduplication was not configured and it needs fixing.
What is a good Meta event match quality score?
Meta scores each event out of 10. Below 6.0 means a large share of your conversions cannot be matched to a person who saw your ads, and your campaigns are optimising on weak data. 7.0 or above is healthy. Server-side tracking with hashed customer data is usually what moves the number.
How much does server-side tracking cost to run?
The container has to be hosted somewhere. Stape starts at roughly $20 per month, and a self-managed Google Cloud Run deployment can be cheaper at low traffic but needs maintenance. This is an ongoing cost billed to you, separate from any one-off setup fee. If the subscription lapses, server-side tracking stops and you fall back to browser-only data.
Stape or Google Cloud, which should I choose?
Stape is faster to set up, handles updates and includes ready-made power-ups for Meta Conversions API and GA4, at a predictable monthly price. Your own Google Cloud project gives you full control and can cost less at low traffic, but you own the maintenance, scaling and monitoring. For most businesses under a few hundred thousand monthly events, Stape is the practical choice.
Do I need this if I do not run paid ads?
Usually no. The main benefit is feeding better data back to ad platforms so they optimise properly. If you are not spending on ads, the monthly hosting cost buys you cleaner analytics and little else. Fix your browser tags instead and revisit this when you start advertising.
Does server-side tracking make me GDPR compliant?
No. Moving a tag to a server does not remove the need for consent. You still need a consent banner and Consent Mode v2 wired so that tags respect what the visitor chose. Server-side tracking done without a consent signal is arguably worse, because it is harder for the visitor to block.
How long does a setup take?
Two to four days is realistic for one website, including a container, a tracking subdomain, Meta Conversions API with deduplication, GA4 server-side tagging and a round of testing in Meta Test Events and GA4 DebugView.
Written by Eptekhar Hasan, who sets up server-side tracking for ecommerce stores and lead-generation sites. Every delivery includes a written report showing your event match quality before and after, taken from your own accounts.