Server-side tracking: recovering the conversions you already earned
The sales happened. You were just not being credited for them.
Server-side tracking sends conversion events directly from your server to ad platforms, recovering events that browser pixels lose to iOS restrictions and ad blockers. Events must carry a shared event id so the server and browser versions are deduplicated rather than counted twice.
Key takeaways
- Send both browser and server events with a shared event id and let the platform deduplicate.
- Include as many hashed customer parameters as you lawfully can — match quality is the whole point.
- Verify with the platform's own diagnostics rather than assuming it works.
- Recovered attribution improves delivery, not just reporting.
A meaningful share of your conversions never reach the ad platforms. The order was placed, the money arrived, and the pixel that was supposed to report it was blocked, restricted or fired after the tab closed.
Why the browser loses events
- iOS tracking restrictions limit what browser-based tracking can attribute across apps and sites.
- Ad blockers are widely used and block the pixel outright.
- Fast navigation — the user closes the tab before the tag fires.
- Cookie lifetimes in Safari and Firefox shorten the attribution window considerably.
How the server-side version works
- 01The conversion happens on your server — the order is created, the payment confirmed, the lead qualified.
- 02Your server sends the event directly to Meta's Conversions API or Google's endpoint.
- 03It includes hashed customer parameters — email, phone, name, address — for matching.
- 04The browser pixel also fires with the same event id.
- 05The platform matches the two by event id and counts one conversion.
Match quality
Meta reports an event match quality score. Low scores mean you are sending too few customer parameters and most of the benefit is being lost. Send everything you lawfully hold — hashed email, hashed phone, name, city, postcode, and the click identifier if you captured it.
The bigger win: qualified events
Once the server-side channel exists, you can send events the browser never knew about — a lead your sales team qualified, a deal that closed, an order that survived a COD verification. That is the difference between optimising for form fills and optimising for revenue, and it is described in full on Performance Marketing.