A tracking pixel can be one pixel tall.
It can also be completely invisible.
The important part is not the picture.
The important part is the request.
When a browser loads an ordinary web page, that page can instruct it to fetch additional resources from other servers: images, scripts, fonts, analytics endpoints, advertisements, social widgets, or a tiny transparent image whose visual contribution is essentially zero.
Fetching that resource tells the receiving server that a browser loaded it.
That sounds trivial until the request is connected to an identifier.
A page can quietly contact companies you never visited
Suppose you visit:
localnews.example/story
The page includes an image from:
tracker.example/pixel.gif?id=847219
Your browser may then contact tracker.example even though you never typed that domain into the address bar.
Depending on the request and browser configuration, the server can receive information such as the requesting IP address, browser headers, the requested URL, timing, referrer information, and cookies previously associated with that tracker.
Mozilla’s privacy documentation describes third-party tracking as the collection of browsing activity through resources embedded across multiple sites. Its broader web-privacy guide also notes that tracking can occur through cookies, referrer information, decorated links, redirects, and other mechanisms. See MDN’s Privacy on the web.
The pixel is therefore less like a microscopic camera and more like a doorbell.
Loading the page rings it.
The visible request is evidence, not the whole data map
Browser developer tools can often reveal that the request occurred.
That is useful evidence.
It does not automatically tell you everything the receiving company later does with the event.
A network request may contain an identifier but not reveal the database record attached to it. The server might discard the request, count it anonymously, associate it with an advertising profile, combine it with account information, or forward it elsewhere.
The browser-visible packet does not answer all of those questions.
Likewise, seeing a third-party request does not automatically prove that the company is following the person across multiple sites. Cross-site tracking requires some way to recognize or link activity between contexts.
Modern browsers block some of this machinery
Firefox’s Enhanced Tracking Protection blocks known cross-site trackers and isolates other third-party cookies using Total Cookie Protection. Safari’s tracking-prevention system also restricts multiple forms of cross-site tracking. See Firefox’s tracking-protection documentation and WebKit’s Tracking Prevention Policy.
Those defenses make old tracking techniques less reliable.
They do not make embedded requests disappear as a concept.
Ordinary pages still load resources from other places constantly.
That is the first lesson of the Surveillance Economy.
The page in front of you may belong to one website.
The network conversation behind it may involve several more.