Direct answer

When you diagnose or configure a VPN connection, “concepts and operation” in the context of online tracking mainly means: what tracking inputs are available to websites and advertisers, how those inputs change when you use a VPN, and what that implies for testing. In general, a VPN alters the network path so the outside world typically sees the VPN server’s network location rather than your usual one, while tracking can still occur through other identifiers and behaviors.

How it works

Online tracking commonly combines multiple signal types:

  • Network signals: IP address and related routing/region cues.
  • Web identifiers: cookies and local storage created by websites.
  • Browser/device fingerprints: stable characteristics derived from browser settings and behavior.
  • Content and interaction signals: URLs visited, timestamps, and actions.
  • Account and log-in context: when users authenticate, identifiers can persist across sessions.

A VPN sits between your device and the internet. For your browsing traffic, it typically changes what is visible to remote services at the network layer (for example, the IP address used for the connection). However, if a website can still set or read cookies, recognize the same browser/device, or connect to an existing account, tracking can continue even with a VPN.

Operating conditions matter: results depend on your browser state (cookies/logins), what the websites you visit do, and how the VPN is configured on your device.

Practical context for VPN diagnosis

A useful way to reason about your setup is to separate outcomes into “network-layer changes” and “application-layer tracking.”

  • If your goal is to verify network-layer changes, compare the visible network location and connection behavior with VPN on vs off using the same browser profile.
  • If your goal is to reduce tracking, focus on browser-side controls too (cookie handling, site permissions, and whether you’re logged in).
  • During troubleshooting, keep variables stable: same device, same browser profile, same websites, and similar time windows.

Because performance and availability vary by network, device, location, and service policies, you may also see differences that are unrelated to tracking (for example, slower loading or intermittent connectivity).