If you've ever wondered why your Facebook Ads Manager numbers don't match your Google Analytics numbers — or why those don't match your actual sales — you're not imagining things. There's a structural reason for the discrepancy, and it comes down to where your tracking data is being collected.
There are two fundamentally different ways to track what happens when someone clicks your link or visits your website: client-side and server-side. Most businesses only use client-side. And client-side has a growing problem.
Client-side tracking: the old way
"Client-side" means the tracking happens on the visitor's computer (or phone). When someone loads your webpage, their browser runs a bunch of JavaScript in the background — including your Google Analytics tag, your Facebook Pixel, and any other tracking code you've installed.
That JavaScript collects information (what page they're on, what they clicked, whether they purchased) and sends it to the analytics platform. It's like having a reporter inside the visitor's browser, filing reports back to headquarters.
This has worked well for about 15 years. The problem is that the reporter keeps getting kicked out.
Ad blockers prevent JavaScript from running. Over 40% of desktop users have some form of ad blocking installed. When an ad blocker is active, your Google Analytics tag doesn't fire. That visitor becomes invisible to your analytics.
Apple's privacy features — introduced in iOS 14 in 2021 — allow iPhone users to block cross-app tracking. Safari has built-in features that limit how long tracking cookies can persist. On an iPhone with default settings, a lot of client-side tracking simply doesn't work.
Browser privacy modes in Firefox, Brave, and even Chrome are increasingly aggressive about blocking tracking scripts.
The net effect: depending on your audience, somewhere between 20% and 50% of your visitors are effectively invisible to client-side analytics. They visit, they click around, they might even buy — and your data never sees them.
Server-side tracking: how it's different
"Server-side" moves the tracking off the visitor's computer and onto a server that you control.
Here's the simplest way to understand it: when someone clicks a tracked link, their click request goes to a server first — before their browser loads your page. The server reads the request, records everything it needs (the time, the referral source, the device type, the country), and then immediately sends the visitor on to their destination.
The whole thing takes about 30–50 milliseconds. The visitor doesn't notice.
But here's what's important: this all happens before the visitor's browser is involved. There's no JavaScript to block. No cookie to restrict. No pixel to prevent from firing. The server just reads an incoming HTTP request — the same basic thing that happens every time any link is clicked on the internet — and logs the relevant information.
The data you get is accurate regardless of what browser the visitor uses, what apps they have installed, or what privacy settings they've turned on.
What this looks like in practice
Let's say you run a Facebook ad and 500 people click it.
With client-side tracking only:
- Facebook might claim 320 conversions (using statistical modeling to fill gaps)
- Google Analytics might show 380 sessions from Facebook (missing the users with ad blockers)
- Your actual sales: 210 orders
With server-side click tracking added:
- Your link tracker shows 500 clean clicks — one for each actual person who clicked
- Google Analytics shows 380 sessions
- Facebook claims 320 conversions
- Your actual sales: 210 orders
Now you can triangulate. 500 real clicks → 380 sessions → 210 purchases. That's a 42% click-to-purchase rate, which is the number you need to evaluate the campaign. And you immediately know Facebook is over-reporting conversions by a significant margin.
How to add server-side tracking to your links today
You don't need to rebuild your entire analytics setup. The simplest way to add server-side tracking is through your links themselves.
Every link you share in an ad, email, or social post can be routed through a server-side tracker before it hits your site. The tracker logs the click on its own server (not dependent on the visitor's browser), then redirects to your destination.
gometrify does exactly this for every link you create. By default, it routes clicks through its server-side redirect engine, then decorates the destination URL with a first-party click ID.
To close the loop, gometrify offers a lightweight Conversion & Revenue Tracking Script that you install on your thank-you or confirmation page. This script reads the click ID and fires the exact conversion value back server-side, bypassing ad blockers and browser privacy protections completely.
Read our Conversion & Revenue Tracking Script Setup Guide to see how simple it is to get 100% accurate conversion data, or create a free account → to start tracking today.