Activity

One session, rendered in order, with the moments the person struggled marked against the events that caused them.

The session list on a user's page tells you where each session started. Activity tells you what happened after that: everything the person did, in order, with the moments they struggled marked.

Open it from the Activity link at the end of any session row. The page has its own address, so you can paste one session to a teammate.

What's on the page

The header: who the session belonged to, the session id, the entry page, and how many events it holds.
Page groups: events are grouped by route. Coming back to a route later shows as its own group, because coming back is itself worth seeing.
Event rows: each row is something the person did. A clicked element is named by its readable label ("Clicked Continue"), never by a hash.
Elapsed time: every row shows the time since the session started, and page two keeps counting from the session start rather than restarting at zero.
ARCY's own moments, in the same list: the widget opening, a question asked, a flow suggested, a flow started and how it ended. They carry a marked icon so you can tell them apart at a glance, and they stay in the order they happened rather than sitting in a column of their own. That is what makes a session read as one story: got stuck on Continue, opened ARCY, asked about the date field, ran the flow, finished.

Struggle marks

Three behaviors are marked on the event that caused them:

Repeated clicks: the same element clicked three times inside a second.
Came back to this page: the same route reached three times inside a minute, with other pages in between.
Longer here than usual: time on that route well above the route's own typical time.

Nothing here is stored. The marks are worked out when you open the page, so a changed threshold changes what you see about last month's sessions too.

All three are worked out from what the person did in your product, and never from ARCY's own events. That is what keeps a session that used the widget comparable to one that did not.

An empty Activity page

An empty page says which of three things produced it, because they mean different things:

Telemetry is off for this environment. Nothing was collected. Turn it on in the environment settings and new sessions start recording.
This environment asks for consent, and this person may not have given it. The answer is given in the visitor's own browser and never reaches us, so the page says this is the likely explanation rather than claiming to know.
Collection is on and the session sent nothing. This is the one case where an empty page is a fact about the person: they opened the page and left.

Sessions with no signed-in user

A visitor who never reached your identify() call still gets a full session. It renders exactly like any other, named by its visitor id instead of a user id. Nothing on the page needs a signed-in user.

Long sessions

A very long session shows from the beginning and is cut off at the end. The page says so, because a cut-off list that looks complete leads to a wrong conclusion.