Server-side tracking
Also known as: Server-side tagging
Server-side tracking is a setup in which conversion and behaviour events are sent to analytics and ad platforms from a server you control, rather than directly from the shopper's browser.
Formula
Tracking coverage = orders recorded by the tracking system ÷ orders in Shopify × 100Worked example
Illustration: Shopify records 1,000 orders in a month. Browser-only tracking records 850 of them. After adding server-side events for purchases, 980 are recorded.
- Browser-only coverage = 850 ÷ 1,000 = 85%.
- With server-side events = 980 ÷ 1,000 = 98%.
- Purchases recovered = 980 − 850 = 130.
Coverage is something you can measure. Compare tracked purchases with Shopify orders to check your setup.
Why it matters for a Shopify store running ads
Ad platforms optimise on the events they receive. If 15% of purchases never reach them, the algorithm has less signal and reported ROAS understates results. Server-side tracking makes the most important events, especially purchases, much harder to lose.
It also gives you control: you decide which data leaves your server, can attach first-party identifiers consistently and can send profit-based values. It doesn't remove the need for consent, and it doesn't settle which channel deserves the credit for a sale.
Common mistakes
- Ignoring consent requirements because events are sent from the server.
- Running server-side and browser events side by side without deduplication.
- Expecting server-side tracking to fix attribution disagreements between platforms.
FAQ
Is server-side tracking the same as the Conversions API?
The Conversions API is Meta's specific endpoint for server-side events. Server-side tracking is the general approach, which can feed Meta, TikTok, Google and your own analytics.
Does server-side tracking bypass cookie consent?
No. Privacy laws apply to the data, not to where it is sent from. You still need a valid legal basis and consent where required before sending personal data to ad platforms.
Related terms
- Conversions API (CAPI)The Conversions API (CAPI) is Meta's server-to-server connection that lets a store send events such as purchases directly from its server to Meta, alongside or instead of the browser pixel.
- UTM parametersUTM parameters are tags added to the end of a link, such as utm_source and utm_campaign, that tell your analytics which source, medium, campaign and ad sent each visitor and order.
- Attribution windowAn attribution window is the period after someone clicks or views an ad during which an ad platform will credit a purchase to that ad, for example 7 days after a click or 1 day after a view.
- IncrementalityIncrementality is the share of conversions that happened because of an ad and would not have happened without it, measured by comparing a group that saw the ads with a similar group that didn't.
Want this number for your own store without a spreadsheet? ProfitFly connects Shopify, Meta and TikTok and shows your real profit every day, free up to 50 orders a month.
Start free