Tracking Pixel
A tracking pixel is a tiny, often invisible image or code snippet that sends a request to a measurement server when a page or email loads, which platforms use for measurement and attribution.

A tracking pixel is a tiny, often invisible 1×1 image or code snippet embedded in a web page or email. When the content loads, it makes a request that sends data back to an ad platform or analytics server. That request can show that the pixel was loaded, for example that a page was viewed, an email was opened or a visitor landed after a click, and the platform can tie it to identifiers it holds for measurement and attribution. It does not by itself show that a person saw the content or took an action.
How it works. When a browser or mail app renders the content, it requests the pixel from the tracking server. The request URL can carry parameters such as a campaign or click ID, and the request itself can reveal details such as the time, the device's operating system and its location, so the platform can log the event. Many pixels are now JavaScript tags that can send richer data than a bare image request, but in both cases the data reaches the collection server as a request. A request is not proof of a human action. Apple's Mail Privacy Protection downloads remote email content in the background by default, whether or not the person engages with the email, and routes it through relays that hide the reader's IP address. Gmail scans images before delivery and, depending on the reader's settings or its judgment of the sender, asks before showing them. Browser tracking-prevention settings can also block some trackers.
Why it matters. Pixels feed much of digital measurement: they support click tracking, audience building and retargeting, and they can connect ad clicks to on-site behavior when an identifier is available. A conversion pixel is a specialized tracking pixel placed on a goal page (like an order confirmation) to record completed actions. Server-side methods such as a postback URL send the event from a server instead of the visitor's browser, so they do not depend on the browser loading an image. They still need an identifier such as a click ID to tie the event to a click, and they do not replace everything a pixel does: Taboola's Realize help center notes that with server-to-server tracking alone you cannot collect audiences or retarget users. Pixels also raise consent questions. In the UK, the ICO says PECR applies to tracking pixels and other technologies that store or access information on a user's device, and allows them only in particular circumstances or with valid consent; the EDPB reads Article 5(3) of the EU ePrivacy Directive as covering tracking pixels and tracking links. In ad intelligence, a pixel found on a landing page shows which tag the page loads, not whose measurement it serves: the ICO's own example has an advertiser embedding an affiliate platform's pixel on its order confirmation page. It does not by itself reveal the advertiser's analytics or attribution stack.



