Home › Blog · Tracking basics · 19 November 2026 · 5 min read

What is server-side tracking?

Server-side tracking reports conversions from a server instead of the visitor's browser. Here is what it recovers and what it cannot fix.

Server-side tracking means a conversion, such as a purchase or a lead, is reported to an ad platform by a server instead of by the visitor's browser. It recovers events that browsers lose to ad blockers, cookie limits and network errors, and it leaves consent, attribution rules and wrong data exactly as they were.

How browser tracking works

A tag is a small piece of JavaScript that an ad platform asks you to put on your site. When a visitor buys something, the tag runs in the visitor's browser and sends a request to the platform. The request carries the event name, the order value, the currency, and a few identifiers: a cookie that recognizes the browser and, when there is one, the click ID that the platform added to the URL when the visitor clicked the ad.

The platform uses those identifiers to connect the purchase to an ad. Every step depends on the browser. The script has to load, it has to run, the request has to leave the device, and the cookie has to still exist. If any one of those fails, the platform never hears about the sale.

How server-side tracking works

With server-side tracking, the event goes to a server first, and the server passes it to the platform through an API (a documented way for two systems to talk to each other). Meta calls its version the Conversions API. TikTok calls its version the Events API.

The server can learn about the event in two ways:

  • From your own backend. Your shop software knows an order was created, so it reports the order directly. The visitor's browser is not involved at all.
  • From a first-party collection point. Your tag sends the event to an address you or your tracking tool control, and that server forwards it to each platform.

In both cases the server attaches the same kind of identifiers the browser would have sent: the click ID, the browser cookie value, the visitor's IP address and browser name, and often a hashed e-mail address. Hashing turns the address into a fixed string of characters that cannot be read back.

Browser and server, side by side

Browser trackingServer-side tracking
Who sends the eventThe visitor's browserYour server or your tracking tool's server
Affected by ad blockersYesMuch less
Affected by a closed tab or slow pageYesNo, when the event comes from the backend
Needs consent where the law asks for itYesYes
Setup effortPaste a tagAn API token and a server, or a tool that provides both
Risk of double countingLowHigh if you send both without deduplication

What it recovers

Server-side tracking helps with losses that happen between your site and the platform.

  • Blocked requests. Ad blockers and some browsers stop requests to known tracking addresses. A call from your server to the platform does not pass through the visitor's browser, so nothing there can block it.
  • Events that never fire. A buyer pays on an external payment page and closes the tab before your thank-you page loads. The browser tag never runs. Your backend still knows the order exists and can report it.
  • Weak matching. A server usually knows more about the order than the page does. It can send the hashed e-mail and phone number from the checkout, which helps the platform recognize the buyer when cookies are missing.
  • Fragile cookies. Safari shortens the life of cookies written by scripts. A server can keep the click ID alongside the visitor's session or order, so the link to the ad is less likely to disappear before the purchase.

The size of the gain differs from one site to the next. It depends on your audience, their devices and how your checkout works. Our article on why ad platforms miss conversions goes through each cause.

What it does not fix

Server-side tracking is a delivery method. It changes how an event travels and nothing else.

  • Consent. If a visitor in a region with consent rules refuses advertising tracking, that choice covers the server too. Sending the event by another route does not make it allowed. See consent mode and conversion tracking.
  • Platform privacy limits. When someone has asked an app on their iPhone not to track them, the platform restricts how it uses events tied to that person, whichever way the events arrive.
  • Attribution disagreements. Each platform still credits itself by its own rules. Meta and Google will keep claiming some of the same orders. Better delivery makes each platform's count more complete, and the counts will still add up to more than your real sales.
  • Wrong data. A purchase sent with the wrong value, a missing currency or a test order mixed in is just as wrong when a server sends it.
  • Unknown visitors. If a buyer arrives with no click ID, no cookie and gives an e-mail address the platform has never seen, there is nothing to match.

Send both, and deduplicate

Most sites keep the browser tag and add the server. The browser sees things the server may not, such as the platform's own cookies. The server delivers when the browser cannot. Sending from both gives the platform the best chance of receiving each event.

It also creates a new risk. If the platform receives the same purchase twice and treats it as two sales, your reported revenue doubles and bidding is trained on false numbers. The answer is deduplication: both copies carry the same event name and the same event ID, and the platform keeps one. Our guide to the Meta Conversions API shows how this works in detail.

When it is worth setting up

A simple check tells you whether you have a gap. Take one week. Count the orders in your shop's admin. Count the purchases each ad platform's events tool received for the same days, before any attribution. If the platform received clearly fewer events than you had orders, browser tracking is losing some of them.

Server-side delivery matters most when you use automatic bidding, because the platform's algorithm learns from the conversions it receives. It matters less for a site with a handful of orders a month and no ad budget.

Where Tagbreeze fits

Tagbreeze installs one tag for the whole site. It sends conversions to Meta, Google Analytics 4, Google Ads and TikTok from the browser, and it sends them to Meta and TikTok from its own servers too, with deduplication already in place. In the EEA, the UK and Switzerland it waits for consent before sending anything.

In short

  • Browser tracking depends on a script running on the visitor's device. Server-side tracking sends the event from a server through the platform's API.
  • It recovers events lost to blockers, closed tabs and short-lived cookies, and it improves matching.
  • It does not replace consent, settle attribution or correct bad data.
  • Send from both browser and server with a shared event ID so each sale is counted once.

If you would like this set up for you, add your site.

Know what your ads really bring in.

It takes a few minutes. Nothing is changed on your site until you install the tag.

Add your site
Hands on a laptop beside parcels ready to ship