Visitor location

What you get

When the location toggle is on, every session is enriched with:

• Country (e.g. United States).
• Region / state (e.g. California).
• City (e.g. San Francisco).

The location pill shows up on /live, on each session row inside a contact, and on the replay page.

Turning it on

Head to /settings → Tracking tab. You'll find two independent toggles under Visitor location:

• Location for contacts. Applies to sessions from identified contacts.
• Location for anonymous visitors. Applies to sessions captured by anonymous tracking. Disabled until that feature is on.

Existing sessions aren't backfilled — the lookup happens at session start.

How the lookup works

• The visitor's IP is read transiently from edge headers (Cloudflare / Vercel) for the first request of a session.
• We look up country / region / city against the network's geo metadata.
• The lookup result is written to the session row.
• The raw IP itself is never persisted in our database.

Privacy considerations

Many privacy regimes (GDPR, CCPA, LGPD) treat IP-derived geolocation as personal data. Two things to know:

• The toggle is off by default in every new workspace.
• When on, only the derived fields are stored. There's no IP, no carrier, no fingerprint.

If your privacy policy already covers IP-based geolocation for product analytics or fraud prevention, you're typically fine. If not, a short addendum is enough — we can share boilerplate on request.