Skip to main content

Events

Every report is built from three event types: Events from a backend and from revenue providers use the same envelope. Each event has a message_id. Reports remove duplicates by project and message_id, so a retry does not count twice.

Visitors

A visitor is one anonymous_id. The Web SDK creates it as a random UUID and stores it in a first-party cookie, with localStorage and memory as fallbacks. The ID lasts across days in the same browser, so a returning visitor counts once. The ID is never derived from IP address or user agent. A cleared cookie, a private window or a second device creates a new anonymous_id.

Sessions

The SDK keeps a client session_id. A new session starts after 30 minutes without events. A session does not split at UTC midnight; it counts on the day of its first event. An event without a session ID (for example a server event) joins the active session of the same visitor. If there is none, a gap of more than 30 minutes starts a new session.
  • Bounce rate is the share of sessions with one page view.
  • Session duration is the average active time per session.

Users and traits

A user is an explicit user_id that you send with identify(userId, traits). Use a stable ID from your own app. Email is an optional trait, not the identity key. Traits are scalar key and value pairs (string, number, boolean or null). A later identify call updates only the keys it sends. A null value clears a key. You can also edit traits on the user’s profile page. Each event that carries both an anonymous_id and a user_id links that browser to the user. Reports that follow people (retention, funnels, lifecycle, profiles and attribution) use this order:
  1. The explicit user_id on the event.
  2. Else the one user that the anonymous_id links to.
  3. Else the anonymous_id.
So activity from before login joins the user’s history. If several users signed in on one shared browser, its anonymous events stay unassigned. They are not given to the last user.

Bots

The collector labels known bots and crawlers with the device bot. The rows are kept, but every report excludes them by default. Set the filter Device: bot to see only bot traffic.

Dates

Report date ranges use UTC days. The date range and filters select which events and people appear in a report.