What server-side tracking is (and what it is not)

Ad platforms learn which ads work from conversion events: a view, an add to cart, a purchase. Traditionally a browser script (the Meta Pixel, the Google tag) sends those events straight from the shopper's browser to the platform. Server-side tracking sends them from a server instead, over the platform's official server API: the Conversions API for Meta and the Measurement Protocol for Google Analytics 4.

Why browser-only tracking undercounts

• Content blockers stop requests to well-known tracking domains, so the pixel never loads.
• Safari limits how long script-created cookies live, so a returning buyer can arrive without the ad click cookie that attributes the sale.
• Slow connections and closed tabs: the purchase event can be lost if the page is left before the script finishes.

None of these touch your server. When your store sends the purchase from the order it just created, the event does not depend on the shopper's browser at all.

The two halves that work together

Good setups use both. A small first-party browser SDK captures what only the browser knows (page views, the ad click id in the landing URL, the browser identifier) and stores it in first-party cookies on your own domain. Your server sends the authoritative purchase, carrying those identifiers plus the customer's hashed email and phone. The platform receives both copies with the same event id and keeps one.

What a first-party domain changes

Serving the SDK and receiving events on a subdomain of your store (track.yourstore.com) makes tracking part of your own site. Blockers that match known third-party tracking domains do not match your subdomain. It is one CNAME record and does not affect your website or email.

What it is not

Server-side tracking is not a way around consent. If a shopper declines advertising consent, a correct setup sends nothing to ad platforms and sets no ad cookies. The shopper's choice is recorded on each event, and delivery is gated on it. Moving measurement to the server makes it reliable, not invisible.

Do you need it?

If you run paid ads and your ad platform reports noticeably fewer purchases than your order system, the gap is lost signal, and the platform is optimizing on incomplete data. Server-side tracking is how you close that gap within the platforms' own rules.