Understand the activity within a visit
Group pageviews and custom events into observed visits. Inspect engagement metrics and event activity without relying on a browser session cookie.
How to install ↗Visits reconstructed from events
A session is a sequence of received page and track activity for one daily anonymous ID. A gap longer than 30 minutes or a UTC-day change starts another sequence. Overview sessions require at least one pageview.
Explain engagement consistently
Pages per session divides pageviews by sessions. Average session duration uses the first-to-last event span. A session with one recorded event has zero observed duration; that does not prove the person immediately left.
Explore the event feed
Profile activity groups events in collapsible sections, with device, country, browser, and operating-system context when available. Paginate the feed to inspect older activity.
Separate the ID from the visit
The current event envelope’s session_id is a daily server identifier, not a browser-issued 30-minute visit token. Session reports reconstruct inactivity-based visits from timestamps. Read the definition before joining raw data by session_id.
Frequently asked questions
Is session_id a 30-minute browser session?
No. It currently carries the daily server-derived ID. Visit metrics reconstruct inactivity-based sessions from event timestamps.
Why can duration be zero?
With only one recorded event, there is no later event to measure elapsed time.
Does every custom event create an overview session?
No. The reconstructed sequence must contain a pageview to count as an overview session.
Start with a clear measurement model.
Install the SDK, then explore traffic and product activity with the same definitions.