Server-side conversions, explained
The browser pixel is the leakiest part of your funnel. Server-side conversions send the ad platforms what actually happened — from your server, not the shopper's browser.
For a decade, ad platforms learned from a snippet of JavaScript in the shopper’s browser. That snippet is now the weakest link: intelligent tracking prevention shortens or blocks its cookies, ad blockers stop it loading, consent banners gate it, and a flaky mobile connection drops the request entirely. Every one of those is a conversion the platform never learns about — and can’t optimize toward.
What 'server-side' actually means
Instead of the browser telling Meta “this person bought,” your server does — through the platform’s conversions API (Meta’s CAPI, Google’s Enhanced/Offline Conversions, TikTok’s Events API, Snapchat’s CAPI). The event originates from a system the shopper’s browser can’t block, carrying the identifiers the platform needs to match it: the click ID, a hashed email, IP, and user agent.
The browser is a nice-to-have signal. Your server is the source of truth.
Deduplication is the whole game
The obvious fear is double counting — if both the pixel and the server report the same purchase, does it count twice? No, as long as both carry the same event_id. The platform sees two reports of one event, keeps whichever arrived, and drops the duplicate. DATALYR fires the client and server events with a shared ID so you get the coverage of server-side without inflating your numbers.
This is also why sending from a clean source matters: the server event is valued from your real order data, so refunds, declines, and canceled trials never get counted as revenue in the first place.
What improves when you switch
- Coverage. Conversions that the browser dropped — blocked, throttled, or offline — still reach the platform.
- Match quality. Richer, server-side identifiers help the platform tie the conversion to the right person, which feeds better optimization.
- Accuracy. Revenue comes from Shopify/Stripe, not a client-side estimate, so ROAS reflects money you actually kept.
DATALYR wires the conversions API for each platform from the same attribution data — you map an event to an ad account with a conversion rule and it forwards server-side automatically. No pixel surgery, no manual CAPI payloads.
