Online tracking: what problems to expect

Online tracking happens when information about your activity is collected and linked to you (or your device) to influence experiences, measure behaviour, or target ads. For someone trying to protect privacy or troubleshoot access, the core problem is that tracking rarely comes from one place. Instead, it’s usually an ecosystem of signals—network location, browser and app identifiers, cookies, cross-site storage, device attributes, and user actions—that can be combined by different parties.

In practice, users run into problems such as:

  • Confusing “who knows what” because multiple actors may see different parts of the picture.
  • Seeing continued tracking even after changing one setting (for example, because cookies or app identifiers still persist).
  • Misattributing the cause of an issue: tracking signals can look similar whether the source is browser storage, an account session, or network-layer visibility.
  • Limited observability: most tracking logic runs on third-party code, so you often can’t directly confirm what it collects.

How it works in real conditions

Tracking effectiveness depends on operating conditions. When you browse, requests are made to servers (including third parties). Your browser and apps include identifiers and metadata, such as cookies, local storage, cached resources, and a persistent login session. Many sites also load third-party scripts that may set or read storage, request additional resources, or run measurements.

A VPN changes the network path between your device and the internet. That typically affects which IP address is visible to remote services and which network-level observer can see your destination traffic. However, most tracking still uses browser and device signals that are unaffected by network routing. For example, a site can often continue identifying returning users through stored data like cookies or account sessions, even if the IP address changes.

Because of this, “online tracking problems” should be thought of as layered:

  • Network visibility layer: who can see your IP and traffic destinations.
  • Browser/app storage layer: what identifiers remain in your browser or apps.
  • Session/account layer: whether you are logged in and therefore linkable.
  • Consent and policy layer: whether tracking is allowed by site settings and your own browser controls.

What varies between situations

Results vary widely. A change that reduces tracking in one context may not help in another. Key variables include:

  • Device and operating system: browsers and apps treat storage and identifiers differently.
  • Browser settings and extensions: privacy features, blocker tools, and security settings can reduce some trackers but not others.
  • Account state: being logged in can make tracking easier regardless of network routing.
  • Location and network path: your apparent location can influence which trackers or measurements run.
  • Time and updates: websites and tracking partners change code frequently.

This is why it’s important to avoid single-cause assumptions. If tracking persists, it may be due to cookies still being present, cross-site storage behaviour, device identifiers, or account sessions—not necessarily a failure of your VPN configuration.

Limitations and what a VPN cannot verify

A VPN does not guarantee anonymity, safety or access. It may change your apparent IP address to remote services, but it can’t prove that tracking is stopped. Performance and availability also vary by network, device, location, provider and time.

Because you generally can’t observe every step of tracking, verification needs to focus on measurable signals you can check:

  • Whether your outgoing IP changes as expected.
  • Whether DNS and traffic are handled according to your intended setup.
  • Whether browser storage or sessions still identify you across visits.
  • Whether specific tracker requests appear or disappear in your browser’s network or privacy tooling.

Treat “reduced tracking” as an outcome you can test, not a guaranteed state.

Practical verification steps for troubleshooting

Use verification as a repeatable checklist. The goal is to isolate which layer still contributes to tracking.

  1. Confirm network-layer changes
  • With the VPN connected, verify your visible IP address using a trustworthy IP-check page.
  • If you expected a specific region, confirm your apparent location aligns with your VPN routing choice.
  1. Check browser storage and session state
  • Test in an incognito/private window to reduce reliance on existing cookies and cached state.
  • Sign out of accounts (or use a fresh browser profile) to see whether tracking changes without a session.
  • After testing, clear cookies and site data for the domain(s) you’re evaluating.
  1. Inspect request behaviour
  • Use your browser’s developer tools (Network tab) to observe which third-party requests still occur.
  • Compare two scenarios: VPN on vs off, and cookies intact vs cleared.
  • Look for repeated calls to tracking or advertising endpoints, and note whether they correlate with cookie presence or with account login.
  1. Validate DNS expectations (where applicable)
  • If your VPN setup includes DNS options, verify which DNS resolver your device uses during the test.
  • This helps distinguish “the VPN is routing traffic” from “DNS is still leaking via another path,” which can affect how certain services learn about your browsing context.
  1. Re-test across time and conditions
  • Run the same tests at different times or after updates to confirm that observed differences are not temporary.
  • If results fluctuate strongly, treat it as a configuration or environment variable, not as proof of a permanent privacy outcome.

If you want a structured walkthrough, you can also use the online tracking checklist for problems and verification for setup, diagnostics and troubleshooting.

What to avoid when verifying

  • Don’t assume one metric proves “no tracking.” Tracking can continue via storage and sessions even when IP changes.
  • Don’t compare results in different browser states (logged in vs logged out, cookies present vs cleared) without controlling variables.
  • Don’t treat temporary failures or slow performance as a privacy conclusion; performance and availability vary by network and time.
  • Don’t rely on a single third-party tool’s interpretation; different privacy tools report different signals.

For a more targeted approach, see what to know when evaluating online tracking during diagnosing or configuring a VPN connection.