How to think about online tracking when it becomes a problem

Online tracking is the set of signals and identifiers that let websites, apps, advertisers, and platforms understand or measure your activity. For digital nomads and independent users, it becomes a practical problem when it leads to profiling that changes prices, content, or security prompts, or when it increases risk of account linkage across locations and devices.

A useful way to frame this is: tracking isn’t one thing. It can involve (1) network-level clues such as IP address and routing, (2) browser-level identifiers such as cookies and local storage, and (3) account-level linkage after you sign in. Your “verification” should therefore be about observing what actually changes for you, not about trusting marketing statements.

How it works: operating conditions that affect what you see

Tracking behavior depends on several conditions that are outside any single tool:

  1. Device and browser state
  • Cookies, local storage, cached site settings, and installed extensions can persist across sessions.
  • Fingerprinting signals can come from browser features, fonts, screen details, and how scripts behave.
  1. Account and identity signals
  • If you sign in to services, identity linkage can persist even when you change network or browser settings.
  • Auth sessions may continue to associate activity with your account.
  1. Network and geography
  • Changing networks, VPN/proxy usage, and roaming between countries can change IP-based signals.
  • Some services also use “anti-abuse” logic and may behave differently by location, time, and network reputation.
  1. Website/app behavior
  • Different sites use different third-party trackers.
  • Some trackers only load on specific pages, in response to consent, or after user interaction.

Practical context: verification checklist for problems and “proof”

Use this as a practical, repeatable checklist. The goal is to confirm what changes for your setup, and what does not.

  1. Define the outcome you’re trying to change Pick one concrete goal:
  • Reduce cross-site tracking for browsing sessions.
  • Reduce tracking correlation across countries or networks.
  • Keep advertising or profiling from being consistent across sign-ins (where feasible).
  1. Establish a baseline (before changing anything)
  • Note what you can observe: cookie prompts, “you may be interested” patterns, and whether the same ad topics reappear.
  • If you use browser tools, record indicator states (for example: whether third-party requests appear or persist).
  1. Apply one change at a time
  • Change only one variable (e.g., network routing, browser profile, or cookie state) so you can attribute what you observed.
  • Avoid stacking multiple changes; it makes verification unreliable.
  1. Test across three contexts
  • Signed out: browse a few pages without being logged into accounts.
  • Signed in: repeat key checks after logging into at least one service.
  • New session: close the browser and repeat with a fresh session state.
  1. Look for the right signals Instead of only looking at whether a page “loads,” check:
  • Whether third-party cookies and similar storage are created or reused.
  • Whether your browser identifiers persist across sessions.
  • Whether network-level signals appear to change (for example: IP-based behavior at the service level).
  • Whether content or ads appear consistently despite changes.
  1. Capture evidence you can compare
  • Screenshots, timestamps, and a short log of what you did help you notice patterns.
  • If a site asks consent for tracking, note your choices and whether the same prompts recur.

Limitations: what you cannot verify away

A complete verification approach also requires accepting important limits:

  • No single tool guarantees anonymity, safety, or guaranteed access. Tracking can still happen through multiple channels.
  • Performance and availability vary by network, device, location, provider, and time, so results may not reproduce perfectly.
  • Some tracking is account-linked. If you sign in, identity linkage can persist even when you change network routing.
  • Websites can change scripts and third-party partners over time, so a “works today” result may not hold later.

In practice, treat verification as an ongoing habit rather than a one-time pass/fail.

When is the checklist “complete” for your use case?

You can consider your verification reasonably complete when you can answer these questions for your scenario:

  • What changes for you when you modify network routing or browsing state?
  • Which tracking channels remain persistent (browser state vs. account linkage vs. service-specific behavior)?
  • Do results stay consistent across at least one repeat test (same device, same session pattern) and one change (new session or signed out vs. signed in)?

If you cannot observe a meaningful difference in your chosen outcome after controlled tests, that is also a result—you’ve learned that the problem may not be addressed by the approach you tried.

Verification steps you can do immediately (quick sequence)

  1. Pick one browser profile for testing and keep it consistent.
  2. Clear or reset the session state (cookies and site data for the relevant sites) to remove “carryover.”
  3. Do a small baseline run, noting prompts and recurring behavior.
  4. Change one variable (such as network routing) and repeat the same browsing steps signed out.
  5. Repeat signed in, then compare what stayed the same.
  6. Write down what you observed and whether the pattern held across a new session.

If you want deeper help, the most direct next step is to review guidance specifically focused on verification for privacy-conscious digital nomads: /online-tracking/verification/ and the related Q&A pages under /answers/online-tracking-verification-q1/ through /answers/online-tracking-verification-q6/.