Online tracking, defined — and what “setup and decisions” really mean

Online tracking is the collection of signals that let services recognize and measure user activity across sessions, pages, apps, and sometimes devices. For digital nomads and independent users, “setup and decisions” means the practical choices you make across your browser, apps, accounts, and networks—before and during travel—to reduce linkability, limit what’s shared by default, and spot when a tool’s claims don’t match reality.

Two operating conditions matter most:

  • You are identified by some combination of data, such as account logins, device or browser identifiers, cookies, and app permissions.
  • Tracking behavior changes with context, including the country, the network you use (home Wi‑Fi vs. public Wi‑Fi), the device you carry, and the specific apps and sites you visit.

How online tracking works (simple model)

A useful mental model is a loop:

  1. Signals are created in your browser or app (page visits, clicks, ad requests, device details, timestamps, language/locale, and sometimes unique identifiers).
  2. Signals are sent to first parties (the site/app you use) and often to third parties embedded on the page (analytics, advertising, performance measurement).
  3. Signals are stored and reused via cookies, local storage, device identifiers, account profiles, and other mechanisms.
  4. Signals are matched over time to estimate an identity or profile, even if you never explicitly log in.

Important limitations and nuance:

  • Tracking can happen without ads (analytics, fraud prevention, site security, personalization).
  • Some mechanisms are hard to fully block, because sites need certain storage for core functionality, and some identifiers can be reintroduced by reloading environments.
  • Even when a component is blocked (for example, third-party requests), first-party storage and account-based identity can still allow recognition.

Practical context: how this affects a digital nomad

If you move between countries and networks, the risk isn’t only “being tracked”; it’s also how easy it becomes to link those sessions into one story.

Common situations:

  • Account-based tracking: Logging into the same account on a device (or in multiple apps) can tie activity together.
  • Browser state continuity: Carrying cookies/storage across sessions makes long-term recognition easier.
  • App permissions: Location, device identifiers, and advertising-related permissions can increase linkability.
  • Network-dependent behavior: Some trackers and scripts behave differently depending on IP, geolocation, or performance expectations.

A privacy-minded approach for nomads usually aims for resilience rather than perfection: reduce unnecessary identifiers, compartmentalize where reasonable, and check that your choices are actually working on the sites and apps you use.

Limitations you should assume

When making decisions, treat the following as baseline constraints:

  • No single setting guarantees anonymity, safety, or uninterrupted access. Protections can break with updates, site policies, or authentication requirements.
  • Performance and availability vary by device, network, location, and service behavior.
  • Not all tracking is preventable in the same way. Some data comes from what you choose to share (accounts, logins) and can persist even if you block certain scripts.
  • Product or legal claims may change over time and should be considered only after you verify them against your current environment.

Verification steps that don’t rely on marketing

Because claims can drift, verification should be repeatable. Here are practical checks you can run:

1) Confirm what you’re actually blocking

  • Use your browser’s developer tools (Network/Console) to see whether requests to tracking/analytics endpoints still occur.
  • Check whether storage is being written (cookies, local storage) after visiting a site.

2) Test linkability in a controlled way

  • Compare behavior with and without a key change (e.g., logged in vs. logged out, default vs. hardened browser profile, different browser/container).
  • If possible, repeat the same visit sequence and observe whether you get consistent “same user” behavior from the site (for example, personalization or re-targeting signals).

3) Measure side effects on functionality

  • Make sure essential workflows still work: logins, payments, required scripts, and CAPTCHA flows.
  • Note which protections cause usability problems. A tool that “works in theory” but breaks daily tasks often won’t stay enabled.

4) Validate provider claims with your own evidence

If you evaluate a privacy tool, treat it as a hypothesis:

  • Does it reduce the categories of requests you care about?
  • Does it change where identifiable requests appear to originate?
  • Do your logs and observations match the claimed outcome?

5) Re-check after travel and updates

Because context changes, do a quick re-test when:

  • you switch networks (public Wi‑Fi vs. mobile hotspot),
  • you change cities/countries,
  • your browser or OS updates,
  • app versions change.

Decision checklist: what to choose, and what to avoid

When you’re deciding on an approach to online tracking, prioritize decisions you can verify:

  • Choose identity hygiene: Use separate profiles for different roles (work vs. personal) when it fits your workflow.
  • Control browser and app permissions: Reduce broad permissions that aren’t necessary for your tasks.
  • Limit continuous storage where you can: Clear session data when it matches your threat model and doesn’t break your services.
  • Avoid absolute promises: If a claim suggests “perfect” or “guaranteed” outcomes, treat it as marketing language and rely on your own checks.
  • Prefer transparency over complexity: The more opaque the mechanism, the harder it is to validate.

How to refine your setup without getting stuck

If you want fewer headaches, iterate:

  1. Pick one change (browser settings, privacy mode, or permission reduction).
  2. Visit a small set of sites you commonly use.
  3. Run the verification checks above.
  4. Keep what reduces tracking without breaking your essentials.

Over time, you’ll build a setup that matches your travel realities: frequent network changes, multiple devices, and varied site behavior.

You can also explore deeper context on evaluating privacy choices in specific scenarios:

  • /online-tracking/setup/
  • /answers/online-tracking-setup-q5/
  • /answers/online-tracking-setup-q6/