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”There are two ways in:
- Overview › Sessions worth watching picks a few recent visits for you, each with the reason it stood out.
- Audience › Sessions lists every session, newest first. Each row shows the outcome (Purchased, Reached checkout, Added to cart, Browsed or Bounced), where the visitor came from, the cube they entered on and the one they left on, their active time, and the key actions they took.
To find a particular kind of visit, use the filter buttons above the list: Purchased, Reached checkout, Added to cart, Searched and others, with less common actions under More actions. You can also narrow the list to sessions that started on one cube (from Entry points), or by source or country with the analytics filters.
Reading a session
Section titled “Reading a session”The top of the page sums up the visit: its outcome, whether this was a new or returning visitor, the device and country, and the active time, cubes, content views and key actions. It also shows the cube they entered on, the cube they left on, and when they answered the consent prompt.
The Journey below it is the visit in order. Each cube visit shows when it started, how long it held attention and how far into the cube they got. The slides follow in the order they were seen, with time spent on each, and every action (added to cart, searched, answered a survey, opened a link) appears under the slide it happened on. Going back to an earlier slide shows as its own step. A longer gap shows as a pause.
Cubes the visitor swiped past without opening are grouped into one line, such as “Swiped past 6 cubes”. Turn on Show swiped-past cubes to list them one by one. The automatic events recorded as the storefront loads are hidden; turn on Show system events to see them.
Read the journey as a story. 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.
The Visitor panel lists the same person’s other sessions with their outcomes. Previous visit and Next visit step through them, so you can see how someone got to a purchase over several visits.
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.