← Blog ·
What is server-side tracking, and why your pixel misses sales
Ad blockers, Safari ITP and iOS opt-outs hide a large share of conversions from the browser pixel. Server-side tracking sends them anyway.
The browser pixel is a messenger that often doesn't arrive
A Meta Pixel is JavaScript that runs in your visitor's browser and tells Meta "this person viewed a product", "added to cart", "bought". It only works when the browser lets it: the script must load, run, and reach facebook.com. Increasingly, it doesn't.
- Ad blockers and privacy browsers block requests to Meta outright.
- Safari's Intelligent Tracking Prevention shortens cookie lifetimes, so a buyer who comes back after a week looks like a stranger.
- iOS App Tracking Transparency: many people tapped "Ask App Not to Track", and in-app browsers limit what the pixel can see.
- Slow pages and redirects: a buyer pays via a gateway and never returns to the thank-you page where the Purchase pixel lives.
Every lost event means Meta's algorithm learns from fewer conversions. Campaigns optimise worse, reported ROAS looks lower than reality, and retargeting audiences shrink.
Server-side tracking sends the event from a server
With server-side tracking the same event also goes from a server to Meta's Conversions API (CAPI). Servers aren't affected by ad blockers or browser restrictions, and they can add data the pixel can't always send reliably: the order value from your database, hashed email and phone, the visitor's IP and user agent, and the fbp/fbc click identifiers.
Why not only the server?
The browser still knows things the server doesn't — the exact page, the click ID in the URL, the browser cookie. The best setup is both: browser pixel plus server events, deduplicated so each real action counts once. That's what Meta recommends, and what TrackPilot sets up with one script. See how deduplication works.
What it takes
Traditionally: a Google Tag Manager server container, a cloud server to host it, and someone to configure tags. With TrackPilot: paste one script above your pixel (or install the WooCommerce plugin), connect your pixel's access token, and check the event log. Getting started →