Sessions
How Logspot groups a person's activity into sessions — server-side, deterministic, and without an extra session cookie.
A session is a burst of activity by one person. Logspot derives sessions server-side from the events you already send — there's no separate session cookie or client-side timer to manage.
How a Session Is Defined
Events from the same person (their anonymous ID, or user ID once identified) are grouped into a session using a 30-minute inactivity window: a gap of more than 30 minutes starts a new session. A short 5-minute grace at window boundaries keeps continuous browsing from being split mid-flow.
Because the session ID is a deterministic function of the person + the time bucket, the same activity always produces the same session — which means sessions can be re-computed for historical data with no drift, and there's no client state to tamper with.
Where You'll See Sessions
- Per person — each profile has a Sessions list, plus session counts and average session duration in the headline stats.
- Analytics — sessions, average session duration, and bounce rate roll up across your project.
Pageviews & Bounce
A session with a single pageview and no further interaction counts as a bounce. Average session duration measures the time between the first and last event in a session.
Privacy
Sessions add no extra client-side storage — they're computed from event timestamps and the first-party anonymous ID you already have. Nothing about sessions is stored in the visitor's browser.