A pixel is a small piece of code on a web page that tells another system “this visitor just did something”, such as viewing a page or completing a purchase. It runs in the visitor’s browser. That makes it easy to install and also easy to block, which is why serious tracking pairs it with server-side methods.
A tracking pixel is a client-side tag, originally a 1×1 transparent image and today usually a JavaScript snippet, that sends an event to a third-party server when it loads in the user’s browser. Ad platforms use pixels to measure conversions and build audiences (the Meta Pixel, the Google tag, the TikTok Pixel), analytics tools use them to record visits and events, and affiliate trackers and networks offer pixels as the simplest way to report a conversion: the advertiser places the pixel on the thank-you page, and when it fires the conversion is attributed to the click stored in a cookie.
Because it runs in the browser, a pixel depends on everything the browser allows. Safari’s Intelligent Tracking Prevention, first introduced in 2017, restricted third-party cookies, and ITP 2.1, announced in February 2019, capped first-party cookies set by JavaScript at seven days. Apple’s App Tracking Transparency (iOS 14.5, April 2021) made cross-app tracking opt-in, and Meta introduced Aggregated Event Measurement for iOS web events in response. Ad and tracker blockers stop many pixels outright, and pixels do not fire if the user closes the page before the thank-you page loads or if the thank-you page sits on a domain the pixel cannot read cookies from.
The answer the industry converged on is to keep pixels for what they are good at, audience building and on-site event capture, and to report conversions server-side as well. Meta’s Conversions API and Google’s enhanced conversions and offline imports are the platform versions; postbacks are the affiliate version. When both are sent, platforms deduplicate the two using a shared event ID so a conversion is not counted twice.
For affiliates, a pixel is acceptable on low-stakes setups and on offers where the advertiser cannot fire a postback, but it should not be the only record of revenue. A tracker showing fewer pixel conversions than the network shows approved conversions is the classic sign of pixel loss.
An advertiser records 1,000 confirmed purchases from your traffic in a month. You compare what each tracking method captured.
| Method | Conversions captured | Main losses |
|---|---|---|
| Thank-you page pixel only | 810 | ad blockers, Safari cookie limits, closed tabs, iOS opt-outs |
| Postback from advertiser server | 990 | a few lost click IDs |
| Pixel + server-side with event ID deduplication | 995 | — |
The pixel misses close to a fifth of real purchases. On a self-serve platform that bids on pixel data, that missing fifth is invisible to the algorithm, so campaigns that actually perform look weaker and bids fall. Adding the server-side record restores the signal without double counting, because both events carry the same ID. Numbers are illustrative; the direction of the gap is consistent across sources.
What a tracking pixel is, how it fires in the browser, how it differs from server-to-server tracking, and where the Meta Pixel, the Conversions API...
Intermediate · 10 min readHow S2S postback tracking works: click ID, macros, where the postback URL goes, testing, deduplication, and why server-side is the durable standard...
Beginner · 6 min readHow affiliate tracking really works: clicks, click IDs, postbacks, server-to-server flows and why clean attribution is the foundation of a profitab...
Advanced · 11 min readHow to diagnose affiliate tracking problems: which tracker, network and platform discrepancies are normal and which are alarming, plus broken postb...
A small client-side tag, usually JavaScript, that reports an event such as a page view or a purchase from the user’s browser to an ad platform, analytics tool or tracker.
A pixel fires in the browser and depends on cookies and the page loading; a postback is a server-to-server request sent when the conversion is recorded. Postbacks are more reliable; pixels are easier to install.
Ad blockers, browser cookie limits such as Safari’s ITP, iOS tracking opt-outs and users leaving before the thank-you page loads all prevent pixels from firing.
Often yes, for audience building and on-site events. Send both with a shared event ID so the platform can deduplicate them.
References are listed as plain text on purpose; look them up by title and publisher. Updated: 2026-10-06.
Run them inside a network with real tracking, roughly 48-hour payouts and a dedicated manager.
Join the network