Server-side tracking
Tracking that does not depend on the browser.
Your purchases and leads reported to Google and Meta from your own server, so the ad platforms see the sales they are meant to optimise for.
Browser tracking runs in the visitor’s browser, and browsers limit it more every year — ad blockers, privacy settings and short cookie lifetimes all drop events before they reach Google or Meta. The platforms then optimise on an incomplete picture, and your reports disagree with your store’s own order count.
Setup from $1,500, quoted once I have seen how your store and ad accounts are wired.
Every event is checked against real orders before it is called done. No recovery percentage is promised, because it depends on your traffic.
Meta Conversions API · Google server-side tagging · Consent respected · Checked against real orders
What gets set up
Server-side events for Meta
The Conversions API sending purchases, leads and key steps from your server, deduplicated against the browser pixel so a sale counts once, not twice.
Server-side tagging for Google
A server container for Google Analytics and Google Ads conversions, on your own subdomain, so the data passes through infrastructure you control.
Consent carried through
What a visitor declined in the browser stays declined on the server. Server-side is not a way around consent, and it is not set up as one.
Checked against your orders
A test purchase, then reported conversions compared with your store’s order log, so you know the numbers line up before anyone makes a decision with them.
Pricing
Setup is quoted once I have seen how your store and ad accounts are wired. There is no recovery percentage here on purpose — it depends on your traffic, and a fixed number would be a guess.
Setup
- Price
- $1,500–$3,500
- Basis
- One-time, quoted
Monitoring
- Price
- $200–$400
- Basis
- Per month
- Required
- Optional
Questions
How much of my missing data will this recover?
I do not quote a number. It depends on your audience’s browsers, how many of them use blockers and how your site is built, so any fixed percentage would be a guess dressed as a promise.
What you get is a before and after you can check yourself: reported conversions against your store’s own order count.
Does this get around cookie consent?
No, and it should not. If a visitor declines tracking, the server respects that the same way the browser does. What it picks up are events lost for technical reasons — blocked scripts, dropped requests — not people who said no.
When should I not buy this?
If your browser tracking is not working yet, fix that first. Server-side builds on a working setup; it does not replace one, and the Retail Foundation audit is where to start. And if you do not run paid ads, the platforms have nothing to optimise, so most of the benefit is not there for you.
What does monitoring cover, and is there a hosting cost?
$200–$400 a month covers watching event volumes against orders, catching breaks after site or platform changes, and fixing them. It is optional.
Server-side tagging needs hosting of its own, billed by the hosting provider rather than by me. The cost is estimated before setup starts.
Do your ad platforms agree with your store?
Compare last month’s purchases in Meta or Google Ads with the order count in your store. Send me both numbers and I will tell you whether the gap is worth closing.