Browser tracking vs server-side tracking

Browser tracking is the pixel you add to your store. When someone buys, a script in their browser tells Meta or Google about the purchase. It's easy to set up, but it fails more often than you'd think: ad blockers stop it, Safari limits how long its cookies last, shoppers decline cookie banners, and some checkouts take people off your store before the thank-you page loads.

Server-side tracking sends the same information from a server instead. Your store knows about every order, so a server can send each one to Meta and Google directly, whatever the shopper's browser does.

Most stores run both. The browser pixel catches details only the browser has, like the click ID in the landing URL. The server fills in what the pixel missed.

One order, two ways

A shopper taps your Meta ad on their phone, browses, and buys on Safari with an ad blocker on.

Browser only: the Meta pixel is blocked at checkout. Shopify records the order, but Meta never hears about it, so the ad looks like it sold nothing.
With server-side tracking: the order is sent to Meta's Conversions API from a server, with the shopper's hashed email and the click ID saved from their first visit. Meta matches it to the ad click and counts the sale.
Both working: on a normal browser the pixel and the server both send the same purchase. They share an event_id, so Meta keeps one and drops the duplicate.

The names you'll see

Meta Conversions API (CAPI): Meta's way to receive events from a server. When the pixel and the server both send the same purchase, they share an event_id so Meta counts it once (Meta docs).
Google enhanced conversions: sends hashed customer details (like email) with a conversion so Google can match it to an ad click when the cookie is missing.
Google Data Manager API: Google's newer route for sending conversions and customer data from a server.
Server-side Google Tag Manager (sGTM): your own tracking server that receives events and forwards them to many platforms. Powerful, but you run and pay for the server.
Conversions API Gateway: Meta's packaged setup that runs the Conversions API on a cloud server you control. Meta only.

What Shopify already does

You may have server-side tracking without realising it. Shopify's Facebook & Instagram app has data-sharing levels: Standard uses the browser pixel only, while Enhanced and Maximum add the Conversions API (Shopify Help). Shopify's Google & YouTube app sets up Google Ads conversion tracking too, so check its settings as well.

Check those settings before buying a separate tool. If you add another server-side app on top, make sure the two aren't both sending purchases to Meta without a shared event_id, or Meta may count your sales twice.

What it fixes and what it doesn't

Server-side tracking helps the ad platforms see sales their pixel missed, so their reporting and bidding work from a fuller picture.

It doesn't:

Get around consent. If a shopper declines tracking, the server still needs to respect that.
Join up visits across devices by itself. A sale on a laptop after a phone ad click is only matched if the platform can recognise the shopper, usually through hashed email or phone.
Tell you which channel earned the sale. Each platform still credits itself. Sending Meta more purchases makes Meta's number bigger; it doesn't make it agree with Google's or Shopify's.
Create sales. It changes what gets reported, not how many people buy.

Be wary of headline recovery figures. Vendors quote anything from 15 to 60 percent more conversions, with no independent studies behind them. The real number depends on your traffic, your checkout and what you already have set up.

How this shows up in Shopify

Your Shopify orders don't change. Server-side tracking only affects what Meta, Google and others see, so after turning it on, expect the ad platforms' reported conversions to rise while Shopify stays the same. Why ad platforms miss your Shopify sales explains the gap in more detail.

How Prism handles it

Prism's Conversion Recovery sends sales the browser pixel missed to Google Ads and Meta from the server, matched to the original ad click where it can be. Google also gets updated values after refunds and cancellations. Separately, Prism's attribution credits each Shopify order once across the channels that led to it.