On server to server tracking vs pixel tracking, the verdict for most affiliates is clear: use server-to-server (S2S) postbacks as your primary source of conversion data, because they do not depend on the visitor's browser, cookies or ad blocker. Keep pixels for situations where S2S is not available or where you need browser-side events, and treat pixel data as a useful but incomplete signal.
The rest of this guide explains why, where pixels still earn their place, and what each method means for privacy compliance.
Pixel tracking and S2S tracking in plain English
Pixel tracking (client side)
A pixel is a snippet, either a tiny image or a piece of JavaScript, placed on the advertiser's confirmation page. When the visitor's browser loads that page, it also loads the pixel, which calls your tracker. The tracker recognises the visitor through a cookie it set at the click, and records the conversion. Everything depends on the browser: the cookie must still exist and the pixel request must not be blocked.
Server-to-server tracking
With S2S, your tracker passes a click ID to the network in the affiliate link. The network stores it. When the visitor converts, the network's server calls your postback URL with that click ID. The browser is not involved in reporting the conversion. Our explainer on what a postback URL is walks through a full example.
S2S vs pixel: side-by-side comparison
| Factor | Pixel (client side) | S2S postback (server side) |
|---|---|---|
| Reliability | Lost if cookies are deleted, blocked or expire, or if the pixel request is blocked | Works as long as the click ID survives to the network and the network fires the postback |
| Ad-blocker resilience | Low; tracking domains are often on block lists | High; no browser request at conversion |
| Browser privacy features | Hit by third-party cookie blocking and cookie lifetime limits | Largely unaffected, though click IDs in URLs can be stripped in some contexts |
| Setup effort | Low: paste code on a page, if the advertiser allows it | Moderate: configure click ID passing and macros correctly |
| Who needs access | The advertiser's confirmation page | The network's postback settings |
| Cross-device | Fails if the visitor converts on another device | Can work if the network ties the account to the original click |
| Data richness | Can capture browser-side data on the page | Only what the network sends in the postback |
| Fraud risk | Pixels can be fired by anyone who loads the page | Endpoint can be secured with tokens and IP whitelists |
Why pixel tracking loses conversions
Browsers have spent years restricting the tracking that pixels depend on. Firefox has isolated cookies per site by default since its Total Cookie Protection rollout in 2022, and Safari's Intelligent Tracking Prevention blocks third-party cookies and limits the lifetime of script-set cookies. Chrome is the notable exception: Google has stepped back from removing third-party cookies, but you cannot plan around a single browser.
On top of that, ad blockers and privacy extensions frequently block known tracking domains, and consent banners can stop pixels loading if the visitor declines. Each of these quietly removes conversions from pixel reports. For the Safari specifics, see our guide to Safari ITP and affiliate tracking.
S2S has weak points too
Server-to-server tracking is more robust, not infallible. It fails if the click ID is dropped in a redirect, passed in the wrong sub-ID field or truncated by a program that limits parameter length. It also depends on the network firing the postback for every paid event, including rebills and reversals. And because the conversion is reported by the partner's server, you are trusting their system to record it. That is why a test conversion before launch, and a regular reconciliation of your tracker against the network's approved figures, still matter with S2S.
When pixel tracking still makes sense
Pixels are not obsolete. They are the practical choice when:
- The partner does not support postbacks. Some smaller programs or direct advertisers only offer a pixel slot.
- You own the conversion page. If the sale happens on your site, a first-party script on your own domain avoids many third-party problems.
- You need on-page events. Scroll depth, form starts and other micro-conversions happen in the browser.
- Ad platforms need browser signals. Many traffic sources pair a browser pixel with a server-side API. Running both, with deduplication, gives them the best signal.
If you must use a pixel, ask the advertiser to load it from your own custom tracking domain, which is less likely to be blocked than a shared one.
The hybrid approach most buyers use
In practice, many media buyers set S2S postbacks as the source of truth for conversions and payouts, and run a pixel alongside where available as a back-up and for extra signals. The rules that make a hybrid work:
- Decide which method is authoritative for revenue. Usually the postback.
- Deduplicate using a shared transaction ID so one sale is not counted twice.
- Compare the two regularly. A widening gap between postback and pixel conversions tells you how much browser-side tracking is losing.
Hypothetical example: a buyer sees 100 conversions by postback and 78 by pixel in a week. The postback is the figure to report and pay against; the 22-conversion gap is the cost of relying on pixels alone for that traffic mix.
Privacy and consent: server side is not a loophole
It is tempting to think that moving tracking to the server takes it outside cookie law. It does not. In the EU, the European Data Protection Board's Guidelines 2/2023 on the technical scope of Article 5(3) of the ePrivacy Directive, adopted in October 2024, say URL and pixel tracking can fall within the consent rules. And any click ID linked to an individual is likely to be personal data under the GDPR, wherever it is processed.
What S2S does change is resilience and data minimisation: postbacks can carry a pseudonymous ID and a payout rather than the visitor's browser data. Our compliance guides on server-side tracking and the GDPR and whether affiliate cookies need consent cover the legal detail. This is general information, not legal advice.
Which should you choose?
- Buying paid traffic to network offers: S2S postbacks, without exception if the network supports them.
- Content site sending clicks to programs: rely on the program's own tracking, use sub-IDs, and add postbacks if you run a tracker.
- Selling on your own site: first-party, server-side events plus a first-party script for on-page behaviour. Our guide to server-side tagging for affiliate sites explains the set-up.
- Partner only offers a pixel: use it, but test it, and value that traffic with a margin for under-reporting.
Next steps
If you are planning for a future with even less browser-side tracking, read our guide to cookieless affiliate tracking. To find a tracker that handles postbacks well, compare tools in our affiliate tracking platforms directory.