What “online tracking” means, in practice

Online tracking is the process of collecting information about your activity online and using that information to understand, profile, measure, or target you. “Tracking” can be done by the site you visited and by other parties that appear during the page load—such as advertisers, analytics providers, or measurement services.

A key concept for diagnosis is that tracking is not one single mechanism. It can involve several layers working together:

  • Client-side signals from your browser or device (for example, browser capabilities, installed features, or behaviors).
  • Cookie and similar storage (such as identifiers kept in the browser to recognize a user across sessions).
  • Network observations (for example, the IP address your device appears to use).
  • Cross-site correlation through shared identifiers or repeated visits.

When you use a VPN, the most consistent change is typically at the network layer: the IP address and related routing information that sites and third parties may see. Many other tracking signals are still produced by your device and browser, and those may continue unless you change the relevant browser or app behaviors.

How tracking typically operates during a browsing session

A common flow looks like this:

  1. You request a page (from your browser or an app). The page may load not only the main content, but also additional resources.
  2. Scripts and embedded resources run as the page loads. These can read or write browser storage, trigger requests to analytics or advertising endpoints, and record events.
  3. Identifiers are created or reused. If the browser already has cookies or similar stored identifiers, scripts can read them and continue a profile. If not, new identifiers may be generated.
  4. Requests carry signals. Network requests include your apparent IP and other request metadata. Client code may add device/browser attributes.
  5. Data is stored and used. Tracking parties may store events and identifiers server-side and later match them to create or update profiles.

Operating conditions that affect what gets tracked

What you experience depends on conditions that can vary even for the same user:

  • Browser state: whether cookies and other storage are allowed, cleared, blocked, or partitioned.
  • Third-party resource behavior: whether embedded scripts are permitted to run.
  • Device and app settings: some tracking signals can come from the operating system, the browser, or installed app components.
  • Network path: with a VPN, the observed network location changes; without it, your local IP path is exposed.

Important limitation to understand

A VPN is mainly a network-layer tool. It can reduce exposure of your local IP to websites and third parties, but it usually does not remove all identification signals created by your browser or by scripts running on pages you visit. As a result, “tracking reduction” should be treated as a partial change rather than a complete stop.

Differences per situation: what to expect from your setup

Different goals lead to different expectations. For example:

  • Main concern: IP visibility. In many cases, a VPN can change what IP address websites see. However, other signals can still allow some level of profiling.
  • Main concern: repeated recognition across visits. Blocking or limiting cookies and similar storage typically matters more than only changing the network path.
  • Main concern: tracking from embedded third parties. Browser settings that restrict third-party cookies, site data, or script execution can influence this more directly.
  • Main concern: measurement and analytics. Even if some identifiers are blocked, sites can still collect approximate or aggregated telemetry depending on how they operate.

Why performance and availability matter

When you add a VPN, browsing experience can change. Performance and availability can vary by network, device, location, provider, and time. That means a tracking-related troubleshooting plan should include checking whether the VPN connection is stable and whether page loading still works as expected.

What to control and check (practical verification steps)

Use the following practical, user-level checks to understand what changes in your environment.

1) Compare the same action with and without the VPN

Pick a specific test scenario—such as visiting one site with embedded trackers—and compare:

  • Whether key requests still happen during page load.
  • Whether cookies or other storage are created or updated.
  • Whether the apparent network location differs.

Keep conditions consistent: same device, same browser, and the same time window as much as possible.

2) Review cookies and site storage changes

In your browser’s site settings or developer tools, look for:

  • Cookies created by the main site versus third-party domains.
  • Whether cookie blocking or “clear on exit” is taking effect.
  • Whether identifiers persist after you restart the browser.

If you see identifiers being created repeatedly, that suggests the browsing session is still allowing recognition mechanisms.

3) Inspect requests and network endpoints

Browser developer tools (Network panel) can help you see:

  • Which third-party endpoints are contacted.
  • Whether requests continue even when network changes (VPN on/off).

This doesn’t prove “who tracks you,” but it helps you confirm whether the page is still loading tracking-related resources.

4) Test in multiple browsers and profiles

Track behavior can differ between browsers and even between profiles because storage and settings are separate. Use at least one additional profile to check whether your changes are tied to one browser state.

5) Verify claims with measurable outcomes

Be cautious with statements like “anonymity” or “no tracking.” A more reliable verification approach is to ask: What exactly changes in my observable data?

For example:

  • Does the apparent IP shown to sites change?
  • Do cookies get blocked or cleared?
  • Do requests to certain third-party endpoints stop?

Only trust conclusions that match what you can observe in your own setup.

Limitations and uncertainty to keep in mind

  • No guarantee of anonymity or safety: using a VPN does not guarantee anonymity, safety, or access.
  • Results vary: performance and availability can vary by network, device, location, provider, and time.
  • Tracking is multi-factor: even if one signal changes (like IP), other signals from the browser and session can remain.
  • “Stops tracking” is hard to prove: what you can verify is specific to your browser, settings, and what the site is doing at that moment.

If you want, tell me your device (Windows/macOS/Android/iOS), browser, and VPN protocol (if you know it). I can suggest a structured troubleshooting checklist tailored to what you’re trying to reduce—IP exposure, cookie persistence, or third-party scripts.