When a total looks wrong, use it to sample a few real visits. A session here is not one live-chat conversation. How a session is cut (30 minutes idle and 24 hours maximum by default) is in Sessions.
ConsoleBehaviorSessionsWhat the report shows
By default the page shows sessions by visitor: each visitor's sessions form one group, and visitors are sorted by their latest activity. A group shows the session count, total time, total pages, and the latest location and device, with a timeline of sessions underneath, newest first, and the gap between consecutive visits. Each group lists the latest 3 sessions; Show more reveals the rest, and you can expand or collapse all groups at once. If a visitor logged in during the period, their sessions are grouped under that user, including sessions from other devices or browsers. Such groups are marked Logged in with a device count.
Switch to By session for the flat list: visitor, place, device, page count, event count, error count, source, entry, exit, start time, and duration, sorted by most recent activity so sessions still in progress come first. That list can be exported. The page remembers the view you picked last.
Filters sit in one row: the search box takes a visitor code or ID, a logged-in user ID, or an entry or exit page path, and you can filter by new or returning, device, source, and location; these work like filters on other reports. Less common filters are under More filters, whose button shows how many are on: Chatted keeps visitors who had a live chat conversation in the period, Logged-in users keeps sessions after login, and Has errors keeps sessions with front-end errors. You can also require a minimum number of pageviews, events, and duration, so one-page glances drop out, plus a minimum number of sessions in the by-visitor view. All filters live in the URL, so they survive a refresh and a shared link shows the same result. In the by-visitor view, a visitor appears if any one of their sessions matches, and the group lists only the matching sessions.
Open a row for that visit: entry, exit, pages, and events. New and returning are marked on the session. If a replay URL exists, Open replay appears. The URL comes from the session replay link template in project settings, or from a session_url property sent on an event.
How to use it
Jumps from the errors page or a visitor profile open the matching row. From the summary you can open that visitor. See Visitors. To compare a whole period by channel type, use Sources, not a manual sum of these rows.
Limits
Strict privacy rotates the anonymous salt daily, so the same person cannot be tied across days. The page says session data is only meaningful within the day, and in the by-visitor view visits on different days form different groups. Without a login, visitors are recognized by network and browser, so the same person on another device, browser, or network counts as a different visitor. Each group in the by-visitor view lists at most the latest 50 sessions; see the visitor profile for the rest. A server event with no session id does not appear here. Viewers can open the list; they cannot change settings.
FAQ
Which day does a visit count for if it started last night and ran past midnight? The lists show sessions with any activity in the selected period, so that session appears for both yesterday and today. Viewed for today, it is marked Carried over next to the start time, and its page count and duration cover the whole session. Overview, trend, and other totals still count a session once, on the day it started, so for today the list can hold a few more rows than the overview's session count.
Why is duration often zero? Duration is the gap between the last event in the session and the start. One pageview, with no later event and no leave heartbeat, has duration 0.
Are these visitors the same people as the people list? No. This list is anonymous visitor ids. People who have logged in and have a profile are in People & user lookup.