marketing
Server-Side Tracking
Recording visits and conversions on your own server and reporting them to ad platforms through their APIs, instead of relying on browser pixels that blockers and privacy rules strip away.
A traditional tracking pixel is a script from the ad platform running in the shopper's browser. Server-side tracking flips it: your store's own infrastructure records the session and the sale as first-party data, then tells each ad platform what happened through a server-to-server connection - Meta's Conversions API (CAPI), Google's enhanced conversions, TikTok's Events API.
The matching depends on click IDs: parameters like fbclid/fbc, gclid and gbraid, and ttclid that platforms attach to ad clicks. Capture and store them at the visit, send them back with the conversion, and the platform can credit the right ad even when its own pixel saw nothing. A serious setup captures the full set across platforms, not just Meta's.
Server-side tracking is also what makes late conversion feedback possible: when an order lands hours or days after the click - or gets matched to a customer later - the stored click ID lets you report it back so the platform's optimization learns from it.
It is not a magic wand. It restores what the browser lost, but attribution questions (which channel really drove the sale, whether the customer would have bought anyway) still need attribution models and incrementality testing on top of the cleaner data.
What is the difference between a pixel and CAPI?
A pixel is the ad platform's script running in the shopper's browser, which ad blockers and privacy rules can strip. CAPI (Meta's Conversions API) is a server-to-server channel: your store reports the conversion directly, with identifiers like the fbc click ID so Meta can match it to the ad click. Most stores should run both - the platforms deduplicate the two signals.
Does server-side tracking improve ROAS?
It improves measured ROAS by restoring conversions the pixel missed, and it can improve real performance over time because the platform's algorithm optimizes on more complete data. It does not make ads better by itself - a tracking fix recovers visibility, not demand.
Which click IDs should a Shopify store capture?
At minimum the big three ad platforms' IDs: fbclid/fbc and fbp for Meta, gclid plus gbraid and wbraid for Google, and ttclid for TikTok. Broader setups (Vibel captures 16 identifiers) also cover Pinterest's epik, Microsoft, Snap, and email-platform IDs, so late conversions can be fed back to every channel, not just Meta.
Related terms
See Server-Side Tracking live in your store.
Vibel tracks Server-Side Tracking across every channel and surfaces it alongside contribution margin, LTV and every other metric that matters.
Get started free