What is a tracking pixel?¶
A tracking pixel is remote content, often a tiny or hidden image, whose unique URL can generate a server record when fetched. The record shows a request associated with the message - not necessarily that a named person read it.
Remote fetching creates the tracking signal¶
The URL may encode campaign, recipient or message identifiers. A server can record request time, address and user agent. The same mechanism can use an ordinary image; literal one-pixel size is not required.
Mail providers, privacy relays, security scanners, previews and background clients can fetch content automatically. Conversely, a person can read while remote images are blocked. Recorded addresses may belong to proxy infrastructure.
Preserve without generating another event¶
Inspect preserved HTML for HTTP image sources, hidden styling and unique tokens in a controlled working copy with remote loading disabled. Record client settings and do not repeatedly open the original. If sender-side data is obtained, establish whether its “open” label means direct fetch, proxy preload or classified event and how repeats and scanners are treated.
A bounded finding is that a unique remote resource was requested. Human attention, device and location require corroboration.
The point to remember
Tracking pixels record remote-content requests, which may be caused by people, providers, privacy features or security systems.
