What Is a Tracking Pixel? (And Why They Are Fading)
Tracking pixels explained: the 1×1 image trick, where pixels still live in email and ads, and why first-party events replace them.
A tracking pixel is a 1×1 transparent image whose entire purpose is the HTTP request that fetches it: the URL carries data (page, campaign, user identifiers), the request's headers carry more (IP, user agent, cookies), and the server logs it all. A 1996-era hack that quietly became the load-bearing infrastructure of ad tech.
Where pixels live today
- Email opens: the pixel that tells senders you opened the message — now largely neutered by Apple Mail Privacy Protection pre-fetching everything, which is why open rates became fiction (newsletter measurement after MPP).
- Ad conversion tracking: Meta and Google pixels matching your purchasers against their user graphs — the part that consent banners, ad blockers, and ITP have been dismantling (the first-party alternative).
- No-JS analytics fallback: the one honest survivor — when JavaScript is unavailable, an image request can still count a pageview. Clycyo's own collector supports a GET pixel fallback for exactly this.
Pixel vs script vs event
The pixel's distinguishing feature is also its limitation: it fires once, blind, with whatever the URL was composed to carry. A script tracker observes context (timing, events, errors); a server-side event carries verified data. Modern measurement uses the trio deliberately: script for behavior, server events for money, pixel only as last-resort fallback.
The privacy line
Nothing about a 1×1 image is inherently invasive — the question is what rides the request. A pixel carrying page-and-campaign to your own first-party collector is benign counting; a pixel carrying a cross-site cookie to an ad network is profiling, and is exactly what ePrivacy consent rules gate. The technology was never the issue; the identifier economy built on it was — and that economy, not the pixel, is what is fading.