Sessions
Every visit, with its length, pages, events and source.
- Duration, pages and events per session
- Source and device on every one
- Open any session in full
Features·Behaviour
When the totals don’t explain something, look at one person. You see every session and event they had, in order.
What it does
Read the same events as sessions, raw events or one person’s history.
Every visit, with its length, pages, events and source.
The raw event list. Use it to check what is being sent.
Each person has one timeline, anonymous or identified. Identifying someone joins their earlier history, except on cookieless projects.
How it works
01
Sessions and events arrive from the snippet; identifying a person is one extra call when you know who they are.
02
Go from the totals to a list of sessions to one visitor. Each level filters the next.
03
Everything that person did, in order, across every visit and every device you know about.
Read next
FAQ
What people ask before they switch it on.
No. Anonymous visitors get a stable identity and a full history. Identifying someone adds a name to a story you were already collecting.
On a cookieless project it matters more: an anonymous visitor there lasts a day, so identifying people early is what gives you a history worth reading.
It follows them. The anonymous history from before they identified themselves is joined to the person, so you can see the whole path including the part before they had an account.
The exception is a cookieless project. There, each day gets its own anonymous id and nothing links them, so a person is joined up only from the identify() call onwards.
Yes, once the person is identified on both. Their activity then lands on one timeline.
No. Profiles show the event and session history. Session replay is its own feature on the Growth plan: a recorded session gets a Watch replay button that plays the visit itself.
Free up to 100k events a month · no credit card