Direct answer

Online tracking is the collection and use of signals about your device, browser/app behavior, and online activity—often to recognize you, measure behavior, personalize content, or build profiles for advertising and analytics. For digital nomads, it helps to think in terms of what signals are emitted, how they are stored or reused, and where the tracking can still happen even when your IP address changes.

A practical way to reduce tracking is not to chase “perfect invisibility,” but to reduce linkability (how easily different visits can be connected), limit unnecessary identifiers, and verify what is actually happening in your own browser and apps.

What it means (concepts)

Online tracking usually relies on three layers that work together:

  1. Identifiers

    • IP address and network-level signals: Your approximate location and network path.
    • Device and browser/app signals: Typical examples include user agent strings and other browser characteristics.
    • Persistent identifiers stored by services: such as cookies and local storage, which can survive across sessions.

  2. Observation (events and requests)

    • Websites and apps generate requests (for pages, scripts, images, pixels, APIs).
    • Third parties embedded on a page (ads, analytics, social widgets) can observe these requests.

  3. Reuse and coordination

    • If the same identifier (or a combination of signals) appears again, services can connect past and present activity.
    • Data can also be shared across actors (for example, ad networks and measurement providers), depending on their integration and policies.

A simple mental model: tracking becomes stronger when many services see the same device/browser signals and can store them, then later reuse them to link visits.

How it works (an easy model)

Here is a step-by-step flow you can use to reason about most tracking you encounter:

  1. You load a site or open an app Your browser or app makes network requests. Some requests go directly to the site you asked for, while others go to third parties included by that site.

  2. Scripts and “pixels” run Included code can record events (page views, clicks, logins, purchases, video plays) and send them to analytics or advertising endpoints.

  3. Storage is created or updated The browser may receive cookies or local storage data. Sometimes identifiers are also stored in app-related storage or platform-level mechanisms.

  4. Signals are tied together Subsequent visits can be recognized using stored identifiers, refreshed identifiers, or a combination of signals.

  5. Profiles and measurement continue over time Tracking can influence what you see (recommendations, ads, dynamic content) and can help platforms measure conversions and attribution.

For digital nomads, two extra realities matter: you often change networks and locations (which affects how “consistent” your signals appear), and you may use multiple devices and browsers (which can either fragment your identity—or make it easier to connect via cross-device signals, depending on the service).

Practical context for privacy-conscious nomads

To reduce tracking exposure while living across countries and networks, focus on outcomes you can control:

  • Browser and app separation: Use dedicated browser profiles for different activities (work vs. personal), so stored identifiers don’t mix.
  • Limit third-party embedding: Many tracking systems come from third-party scripts. Reducing third-party content lowers the number of observers.
  • Choose settings that limit persistence: Cookie controls, blocking of unnecessary storage, and careful handling of “remember me” features can reduce cross-session linkability.
  • Be mindful with logins: Signing into accounts can create strong linkability because services have first-party data about you.
  • Expect partial protection: Even if your traffic path is altered, tracking can still occur via identifiers stored in your browser/app, and via first-party services you intentionally interact with.

If you evaluate tools like VPNs, treat them as a network-level change, not a complete tracking solution. A VPN can change the visible origin of your traffic (for many network observers), but it does not automatically remove cookies, device/app identifiers, or third-party tracking embedded in the pages you load.

Limitations and exceptions (what to watch for)

Tracking is not a single mechanism, so protections can fail in different ways:

  • Persistent storage remains: If tracking relies on cookies or local storage, you may still be recognized across visits unless those identifiers are blocked or managed.
  • First-party services can still observe you: When you interact directly with a service you’re using (email, cloud storage, social platforms), it can often see your behavior regardless of your IP.
  • Third parties can still see events: Even with a changed network path, embedded third-party code can record activity in the browser/app.
  • Changing networks affects consistency, not intent: Switching Wi‑Fi or using mobile data can change the signals some systems use, but it may not prevent identification.
  • Performance and availability vary: Network routing choices, device constraints, and location differences can influence reliability and speed.

So the most realistic goal is reduced linkability and reduced exposure, not “perfect invisibility.”

What to verify (practical checks)

Because tracking behavior depends on your specific browser, apps, and services, verification matters. Use these practical steps:

  1. Inspect network activity in your browser Open developer tools and review which domains are contacted when you load a page. Third-party requests are often a major indicator of tracking/measurement.

  2. Check what storage is being created Look at cookies and local storage for domains involved in the page. Note whether identifiers are set, updated, or persisted across sessions.

  3. Compare “before vs. after” changes Make one change at a time (for example, stricter cookie settings, fewer third-party scripts, or a different browser profile) and observe whether the number of tracking-related requests and stored items decreases.

  4. Test with and without account logins Compare behavior on the same site while logged in versus logged out. Differences often reveal how much is tied to first-party identity.

  5. Evaluate across devices and browsers If you use multiple devices, repeat checks. Tracking can be fragmented per device, or linked depending on the service and its mechanisms.

Common mistakes to avoid

  • Assuming one setting solves everything: Tracking comes from multiple sources, so relying on a single control rarely works.