What it means
Pixel Tracking places a small piece of code (historically a 1×1 image) on a thank-you or confirmation page. When the page loads, the pixel fires and records the conversion client-side. It is easy to deploy but increasingly affected by browser privacy and ad-blocking, which is why many advertisers add postbacks.
Pixel tracking records a conversion by loading a tiny snippet, historically a 1x1 transparent image and now often a JavaScript tag, on the page a user reaches after completing an action. When the confirmation or thank-you page loads, the pixel fires a request to the tracking platform, which reads the affiliate cookie set at click time and logs the sale. It is the browser-side counterpart to server-to-server postbacks.
The mechanism depends on two things happening in the same browser: a cookie dropped when the user clicked the affiliate link, and the pixel firing later to look that cookie up. Image pixels can pass only limited data through the URL, so many programs use JavaScript tags that can read order values, currencies, and transaction IDs before sending them. Placement on the exact confirmation page is essential, because a pixel on the wrong page fires at the wrong time or not at all.
Pixels are easy to deploy, requiring only a copy-and-paste into a page template, which makes them popular with smaller advertisers and quick campaign launches. That convenience is also their weakness: because they run in the browser, ad blockers, script errors, cookie deletion, and privacy features routinely prevent them from firing, causing conversions to go unrecorded. Duplicate firing on page refresh is another frequent problem that inflates counts.
As browsers tighten cookie and script controls, pixel-only tracking has become unreliable enough that many networks pair it with, or replace it by, server-side postbacks. Where pixels remain, best practice is to place them on a genuine confirmation page, deduplicate on transaction ID, and avoid pages a user might reload. Advertisers should treat pixel counts as a floor rather than a complete measure of conversions.
Key points
- Fires a snippet on the confirmation page to log a conversion
- Reads the affiliate cookie set at click time
- JavaScript tags can pass order value and transaction ID
- Blocked by ad blockers, cookie deletion, and script errors
- Deduplicate on transaction ID to avoid refresh double-counts
Example
A store places a JavaScript conversion pixel on its order-confirmation page. When a shopper who clicked an affiliate link completes a $85 purchase, the pixel reads the affiliate cookie and reports order_value=85 with a unique order ID. If the shopper reloads the confirmation page, deduplication on that order ID prevents the sale from being counted twice.