Third-party trackers explained: who is watching and how
Third-party trackers are scripts and pixels from external domains that follow you across sites. Here is how they work, how to spot them, and how to reduce their reach.
What a third-party tracker is
A third-party tracker is a resource loaded from a domain different from the site you are visiting. When you load a page, your browser fetches scripts, images, and frames from many domains; some of those are analytics, advertising, or social widgets that record your visit.
Because the same tracker domain appears on many sites, it can correlate your visits across the web and build a profile. The tracker does not need to know your name; it uses cookies, fingerprinting, or login state to recognize you.
Trackers come in several forms: JavaScript snippets, tracking pixels, iframes, and server-side tags. Each has different capabilities and visibility.
How tracking works in practice
The simplest form is a cookie: the tracker sets a first-party or third-party cookie with a unique ID, then reads it on subsequent visits. Third-party cookies are increasingly blocked, which has pushed trackers toward fingerprinting and first-party proxying.
Fingerprinting-based tracking uses browser signals instead of cookies. It is harder to block because it requires no stored state, but it is less precise and more fragile.
Server-side tracking moves collection off the browser entirely, using the site's own backend to forward data. This is invisible to browser-based tools and is growing in use.
- Cookie-based: unique ID stored in browser, read across sites
- Fingerprint-based: device signals used as identifier
- Pixel-based: 1x1 image request logs the visit
- Server-side: data forwarded by the site's backend
How to spot trackers on a page
Use the tracker detection tool on this site. It inspects the resources loaded on the current page and matches them against a client-side database of known tracker domains.
The network panel in your browser's dev tools shows the same thing: look for requests to domains you do not recognize, especially analytics, ads, and social domains.
Be aware that the tool only sees the current page. Trackers loaded on other pages are not included, and unknown trackers are not in the database.
Reducing tracker reach
Content blockers (uBlock Origin, Brave Shields, Firefox Enhanced Tracking Protection) block known tracker domains at the network level. This is the most effective single measure.
Cookie clearing and private browsing limit cookie-based tracking but do little against fingerprinting.
Browser choice matters: some browsers block trackers by default, others require extensions.
Be cautious of 'acceptable ads' programs and allowlists that let some trackers through in exchange for payment.
- Install a reputable content blocker
- Enable the browser's built-in tracking protection
- Clear cookies and site data regularly
- Use a privacy-focused browser for sensitive browsing
- Review and revoke site permissions
What this site measures
Our tracker detection matches observed resources against a local database and reports categories and counts. It does not send data anywhere. Results reflect only the current page and known trackers.