Visitor Detail Drawer

Click any visitor avatar — on the world map, the big chart, or the live activity feed — and a side panel slides in from the right. It’s everything we know about that one visitor, all sessions, all events, all logs.

Press Esc or click outside to close.

Header

The visitor’s Notionist avatar + auto-generated readable name (same name shown everywhere else in the UI for this visitor_id).
Country flag, city, device type, browser, OS — pulled from the most recent session.

Stats row

Four cards across the top:

Sessions — total session count for this visitor (all-time).
Pageviews — total pageviews across all sessions.
Events — total events including pageviews + custom + pageview_ends.
Time on site — sum of every session’s duration.

Below the stats: first seen + last seen as relative timestamps, plus a “See in logs page” link that opens /logs filtered to this visitor’s logs.

Web Vitals row

If the SDK captured any Core Web Vitals for this visitor (LCP, FID, INP, CLS, FCP), they show here as a horizontal strip. Each metric is color-coded against Google’s thresholds: green = good, yellow = needs improvement, red = poor.

Two tabs

Events tab (default)

Lists every session, newest first. Each session row shows:

Start time, duration, page count.
Entry page → exit page (when different).

Click a session to expand its timeline. You see every event in chronological order:

Pageviews as dotted blue rows.
Custom events highlighted in yellow with the event name.
Referrer shown on the very first event (← google.com etc).

The newest session is auto-expanded when the drawer opens — usually what you want.

Logs tab

Switches to the visitor’s log records (errors, warnings, console messages — anything Loguro.error() / .warning() / etc. captured). Same virtualized renderer as the main /logs page — quick view, expand for full context, all the standard goodies.

The tab badge shows the log count once fetched.

Note: Logs are correlated to visitors via context.visitor_id, which is auto-injected when analytics is enabled. If you disabled analytics (DNT or data-analytics="none"), logs from that visitor stay anonymous and won’t show here. See Identity & Sessions.

Deep link to logs page

The “See in logs page” link in the stats bar opens /logs with the filter pre-applied:

?filter=context.visitor_id:"<the_visitor_id>"

Useful when you want the full logs UI — saved views, advanced filters, AI-powered investigation — scoped to this one person.

When the drawer is most useful

Support ticket triage — user reports a bug, you have their user_id or visitor_id → open the drawer, see exactly what they did, what they saw, what errored.
First-impression debugging — a visitor signed up but never returned → look at their first session, see where they got stuck.
High-value visitor inspection — someone hit your pricing page 6 times this week → see if they’re the same person across all 6 visits.