Session detail
Aggregate numbers tell you something is wrong. Sessions tell you what it looked like.
Because a Rubikc visit happens on one surface, a session is a complete record of what someone did — not a list of pages, but the actual sequence: what they saw, how far they went, where they turned back, and where they stopped.
Opening a session
Section titled “Opening a session”From Audience › Sessions, pick a session and open it. Filter first if you are looking for a particular kind of visit — sessions that converted, sessions from one source, sessions that touched a specific cube.
Reading the timeline
Section titled “Reading the timeline”Read it as a story, in order. The useful questions are:
- Where did they come in? The first cube sets expectations for everything after it.
- What did they skip? A run of cards passed quickly is a card that is not earning its position.
- Where did they slow down? Attention is the signal you cannot get from a page-based store.
- Did they go back? Going back usually means they overshot something they wanted, and that something is worth promoting.
- Where did it end? The last card before someone leaves is the most informative card in the session.
Using it well
Section titled “Using it well”Sessions are most useful when you already have a hypothesis. “Detail retention is poor on this cube” sends you looking for where people stop. Browsing sessions at random is interesting and rarely conclusive.