Visits lists the visits that started in the dashboard’s date range, newest first. Open one to see where it came from, what it did, and how long it stayed on each page. There is no limit on how old a visit can be.
A visit ends after 30 minutes without activity, and lasts 24 hours at most. Bots are left out.
The list
The numbers above the list describe the range and any filters on it:
| Number | What it means |
|---|---|
| Visits | Visits that started in the range. |
| Engaged | The share of visits with two or more page views, 10 seconds of activity, or an event. |
| Pages per visit | How many pages a visit viewed on average. |
| Active time | Average time a visit spent interacting with the page. |
Each row shows the visit’s country, device and source, how long it lasted, when it was last seen and how many pages it viewed. Online means the visitor is on your site now. A visit seen in the last 24 hours says how long ago, and an older one gives the date.
Engaged above the list keeps only engaged visits, which clears out the visits that opened one page and left within seconds. The filters are the dashboard’s, like every other report, so you can list the visits from one source, or the visits that saw /pricing or sent signup. A filtered list covers up to 366 days.
One visit
Selecting a row opens the visit: when it started, how long it lasted, how much of that was active, the page it landed on and the page it left from, and its campaign if it had one. Below that are its pages and events in order.
The time next to a page is how long that page stayed up, until the next page or the end of the visit. It is elapsed time, so a page left open in a background tab counts. Nothing shows when no signal arrived after a last page loaded, because the time is unknown. Now marks the page an online visitor is on.
The address of an open visit is a link to it, for a teammate with access to the site. Feedback sent during a visit links to it too.
Names and people
The names, such as Calm Falcon, are made up from the visit’s id. Different visits can share a name, and a name tells you nothing about who visited.
Each visit stands alone. The hash that tells visitors apart changes every UTC day, so invisit cannot show one anonymous person’s earlier visits.
Who can see visits
Anyone in the workspace can read Visits, including viewers. It never appears on a public dashboard.
Through the API and MCP
The REST API has visit-log for the list, with the same filters and engaged=true, and visits/{visit_id} for one visit. The MCP server has list_visits.