Analytics

A page-based store sees page loads. It knows someone arrived at a product, and it knows whether they bought. What happened in between is mostly guesswork.

A Rubikc storefront is one continuous surface. The whole visit happens there — every card someone swiped past, how far into a product they went, where they turned back, what they ignored. That is a different quality of information, and it is the reason analytics is worth your time here even if you have never looked at analytics before.

What Rubikc records

Broadly, four things:

• Who arrived, and where from.
• What they saw — which cubes, in what order, how deep into each one.
• What they did — swipes, taps, add to cart, survey answers.
• What happened at the end — checkout, or not.

Because it is all one session on one surface, these join up. You can start from “revenue fell this week” and end at “people stop on the third card of our best seller” without changing tools.

What it does not record

Checkout is Shopify's

When someone checks out, they move into Shopify’s checkout. Rubikc sees that checkout started and that a purchase completed, but not what happened inside it. If you need to analyse checkout abandonment specifically, that is a Shopify question.

Bot and crawler traffic is identified and kept out of the other views, so your numbers reflect people. You can look at it separately if you want to.

Where to start

Reading your analyticsThe Overview screen, and what its numbers actually mean.

The analytics viewsTwelve views in five groups. What each one answers.

Session detailFollow one customer through a whole visit.

Acting on what you findTurning an observation into a change to your Space.