Understand a visit without losing control of its detail

Inspect sessions, activity, and consented profiles when your project needs individual analysis. Keep aggregate reporting available as the starting point.

Individual analysis is a deliberate choice

The People surface is off by default. An administrator enables it for the project. Your team must choose the appropriate collection regime and consent behavior.

Identified traits come from information you explicitly supply about your own users. DataVisitors does not discover a person's identity or buy enrichment data.

Review the sequence behind a question

Open a session to inspect its pages, events, and time between steps. A profile can show supplied traits, source information, device facts, activity, and recorded value.

Use the live map and session list to understand current activity. Product locations are coarse. The public demo's fictional city locations do not describe the precision of production tracking.

Keep control of access and removal

Team authorization protects individual views. Public share pages contain aggregate reports and do not expose individual profiles.

Authorized administrators can remove person traits and request event erasure. The controls distinguish those operations. Copies in independently managed backups require their own handling.

Use this detail only when it helps

Investigate a reported onboarding issue or check a known user's activation steps. Use aggregate product reports when you only need a trend.

Read privacy information and the user manual before enabling identified collection.