How tracking usually works, and why it leaks

Most ad tracking starts with a pixel: a small piece of code from Meta, Google or TikTok that sits on your website. When a shopper buys, the pixel runs inside their browser and reports the sale back to the ad platform.

The weakness is that the browser belongs to the shopper. Ad blockers can stop the pixel from loading. Privacy features in browsers and phones limit what it can store. A slow connection or a closed tab can cut it off before it fires. Each of those gaps is a real sale the ad platform never hears about, which makes your ads look worse than they are and gives the platform's bidding system less to learn from.

What server-side tracking changes

With server-side tracking, the report comes from a computer you control instead of the shopper's browser. Your store or payment system already knows when an order is paid, so it sends that fact directly to the ad platform.

Google describes its server-side tagging as processing data on a server you control, rather than in the user's browser, and notes that only you have access to the data in the server until you choose to send it elsewhere. That control is the second big benefit: you decide exactly which fields leave your system.

How US adults feel about companies and their personal data (2023)
  • Feel little or no control over what companies do with their data73%
  • Want more regulation than there is now72%
  • Understand little to nothing of what companies do with it67%
  • Often click agree on privacy policies without reading56%

Each bar is the share of US adults who agreed, from one Pew Research Center survey conducted in May 2023.

Source: Pew Research Center

The main conversion APIs

Each ad platform offers its own server-side doorway:

  • Meta Conversions API: connects your marketing data to Meta's systems, and server events are processed like events sent using the Meta Pixel. In an April 2026 update, Meta said advertisers with a Conversions API setup for web events saw an average 17.8% lower cost per result than those without it. That is Meta's own figure, measured against having no server connection at all.
  • Google enhanced conversions: adds customer details such as an email address or phone number to your conversion tags, hashed with SHA256, a one-way scrambling method, before it is sent. The goal is to match more of your sales to the ads that preceded them.
  • TikTok offers a similar server-side Events API, and many store platforms offer plug-ins for one or more of these.

Avoid counting every sale twice

Most setups run the pixel and the server connection together, because each catches some sales the other misses. That creates a risk: the same order reported twice.

Platforms handle this with deduplication, which means matching and removing duplicate reports. Meta's deduplication guide says a pixel's event ID must match the Conversions API's event ID, and the event names must match too. It also notes that events are only deduplicated if they arrive within 48 hours of each other. Get this wrong and your reported sales jump overnight for no real reason. Comparing claimed conversions with your actual orders, as in our guide to reconciling ad data with sales records, catches it quickly.

What server-side tracking does not fix

Server-side is not a way around privacy rules. If a shopper declines tracking under GDPR or a US state privacy law, sending their data from your server instead of their browser doesn't make it acceptable. Our guide to consent and Consent Mode covers what to respect.

Shoppers care about this. In a 2023 Pew Research Center survey, 73% of US adults said they have little to no control over what companies do with their data. Treat customer data as something you hold in trust, and send the minimum each platform needs.

It also doesn't settle attribution. A platform that receives more of your sales can still claim credit for orders it didn't cause. Meanwhile, browser rules keep shifting: in October 2025 Google said Chrome will keep offering users a choice about third-party cookies and retired several Privacy Sandbox technologies, including the Attribution Reporting API. Your own records stay the steadiest base. Read more in our piece on first-party data.

Matrix ROI, a product of Smith App Studio, takes in sales from Stripe, webhooks or any JSON API and sets them beside each platform's claims. You can try it for 14 days without a card.