Find Out What’s Tracking You Online (and Turn It Off Without Breaking Sites)

You open a news article. Then you shop for running shoes. Later you watch a recipe video. The next day, those shoes follow you around the internet like a polite-but-creepy salesperson who won’t stop showing up.

That “following” usually isn’t magic. It’s a mix of trackers: small bits of code or identifiers that help companies measure, personalize, and sometimes aggressively target ads. Some tracking is used for helpful things (like keeping you logged in). Other tracking is designed to build a profile about your interests across many sites.

This guide shows how to see what’s tracking you and how to turn down the volume without wrecking the everyday stuff you need—checkout pages, sign-ins, embedded videos, and maps.

What “tracking” usually means (in plain English)

Think of a website like a small shop in a mall. The shop can notice what you do inside it. Tracking becomes more interesting (and more invasive) when information about you is shared between shops—especially by the same advertising company that has a presence in many places.

Most tracking you’ll encounter online falls into a few buckets:

• First-party cookies: Created by the site you’re currently visiting. These often keep you signed in, remember preferences, or store what’s in your cart.
• Third-party cookies: Created by a different domain than the site you’re visiting (often an ad/analytics company embedded on the page). These are commonly used to follow you across sites.
• “Pixel” trackers and scripts: Tiny images or JavaScript code that report events (page view, button click, purchase). A “pixel” is often just a 1×1 invisible image that phones home with details.
• Device/browser fingerprinting: Instead of storing a cookie, a site reads many small signals (screen size, fonts, language, time zone, etc.) to guess a unique “fingerprint.” It’s like recognizing you by your outfit rather than handing you a name tag.
• Link tracking parameters: Those long add-ons in URLs like ?utm_source= or fbclid=. They can help measure campaigns, but some parameters also act like identifiers.

If you only remember one thing: cookies are not the only way you’re tracked. That’s why a “clear cookies and you’re done” approach often feels disappointing.

Notice the pattern: the privacy-invasive stuff is often the stuff you can reduce without losing core site functionality—if you do it carefully.

Newsletter

Never miss out on great articles — just enter your email and receive a weekly update!

Go

I have read and accept the Terms & Policy

How to see trackers in real time (using tools you already have)

You don’t need special software to start investigating. Your browser already has clues. The goal isn’t to become a detective for every site—just to learn what “normal” looks like and recognize the loud offenders.

Scenario: You visit a recipe blog. The page feels slow, and you see ads. You suspect a lot is happening behind the scenes. Here’s how to confirm it.

1) Use the site info / privacy indicator

Most browsers show a small icon near the address bar (often sliders, a shield, or a lock with settings). Look for wording like “Tracking protection,” “Privacy,” or “Site settings.”

• If it shows trackers blocked, click it. You’ll often see a count and sometimes categories like “cross-site tracking” or “fingerprinters.”
• If it shows nothing blocked, it doesn’t mean nothing is happening—just that your current setting isn’t stopping it.

2) Check cookies for the site (quick and surprisingly revealing)

In many browsers you can view cookies/storage for the current site through the address bar controls or settings. You might see:

• A short list with the site’s own domain (expected).
• A longer list of unfamiliar domains (often ad tech, analytics, CDNs, A/B testing tools).

If you see dozens of third-party domains on a simple page, that’s a sign the page is inviting lots of outside companies in.

3) Use Developer Tools (optional, but eye-opening)

If you’re comfortable clicking around:

• Open Developer Tools (often F12 or right-click → Inspect).
• Go to the Network tab.
• Reload the page.

You’ll see a waterfall of requests. You don’t need to understand every file—just look at the domain names. If a recipe page is contacting 30+ different domains, a chunk of those are likely marketing/measurement services.

A practical trick: sort or scan for domains you recognize (major ad platforms, social networks, analytics providers). Then notice how many calls are going there before you even scroll.

4) Watch what happens after you click

Trackers often fire on actions: “Add to cart,” “Sign up,” “Purchase,” “Play video.” If you want to understand why you got retargeted ads, this is the moment. Click a product, add it to your cart, then check the Network tab again. You may see requests that look like event reporting.

Privacy settings that work in the real world (without constant whack-a-mole)

The goal is a setup you can live with. Not “perfect privacy” that makes every other page glitch. Use a layered approach: start with browser protections, then add one or two targeted improvements.

Layer 1: Turn on built-in tracking protection

Most modern browsers offer a tracking protection mode. Look in Settings → Privacy (wording varies). A good default is the middle option (often called “Standard” or “Balanced”).

What this typically does:

• Blocks many known cross-site trackers.
• Limits third-party cookies (or partitions them so they can’t follow you across sites as easily).
• Reduces some fingerprinting techniques.

If you jump straight to the strictest mode, you may spend your week babysitting broken embeds. If you want stricter privacy, do it with a small number of exceptions rather than a constant stream of pop-ups.

Layer 2: Decide how you want to handle third-party cookies

Third-party cookies are a big lever because they’re strongly associated with cross-site tracking. Options you’ll commonly see:

• Block third-party cookies: Strong privacy improvement. May break certain sign-in flows or embedded services on some sites.
• Allow third-party cookies only for “visited sites” or partition them: A compromise many browsers now use to reduce tracking while keeping functionality.
• Allow third-party cookies: Most compatible, least private.

Everyday-friendly move: block third-party cookies, then when something breaks that you truly need, add a site exception rather than turning everything back on globally.

Layer 3: Clean up links you share (and the ones you click)

Tracking parameters in URLs are low-hanging fruit. You’ve probably seen links like:

• https://example.com/article?utm_source=newsletter&utm_medium=email
• https://shop.com/product?fbclid=...

Those parameters can reveal where you came from and sometimes act like an identifier. Two practical habits help:

• Before sharing a link, trim it: Often you can delete everything after the ? and the page still loads.
• If a link is huge, paste it into a text editor first: Remove obvious marketing parameters (utm_*, fbclid) and test.

It’s like tearing off the store receipt before handing someone a gift bag: the gift still works, but it reveals less about where it came from.

Layer 4: Use a separate browser profile for “logged-in platforms”

This is a simple, surprisingly effective trick that doesn’t rely on blocking wars.

Mini-scenario: You use a big video/social platform for work and personal life. You’re logged in all day. That platform’s buttons and embedded content appear everywhere online.

Try this instead:

• Use one browser profile (or one browser) where you stay logged into major platforms.
• Use a separate profile for general browsing where you’re logged out most of the time.

This reduces “account-based tracking” bleed-over. It’s like having a work badge you only wear at work, not everywhere in town.

Layer 5: Add a content blocker if you want fewer surprises

If you choose to add one extension, pick a reputable content blocker (ad/tracker blocker) and leave it on the default lists for a while. This can dramatically reduce page weight and cross-site requests.

Realistic expectation: a blocker is not just about ads. It’s about cutting down the number of third-party requests that can observe you. If something breaks, disable it for that site only.

When something breaks: fix it surgically

Instead of turning off all protections, troubleshoot in this order:

1. Reload once. Some pages fail for unrelated reasons.
2. Temporarily disable blocking for that site only. If the issue disappears, you’ve confirmed the cause.
3. Add a narrow exception. Allow that site (or a specific embedded service) rather than relaxing global settings.
4. Try a private window to compare. If private works but your normal session doesn’t, it might be an old cookie or cached script.

A quick “good enough” setup for most people

• Enable your browser’s standard/balanced tracking protection.
• Block third-party cookies (or choose a partitioned/limited option if offered).
• Keep a separate profile/browser for always-logged-in platforms.
• Trim tracking parameters when sharing links.

Once you’ve done that, revisit the original problem: those running shoes that wouldn’t stop appearing. You may still see shoe ads sometimes (ads can be contextual), but the feeling of being followed from site to site usually drops noticeably—without turning the web into a brittle, broken experience.