Skip to main content
Growth → Analytics. Built in, nothing to install, no script to paste.

No cookies

Your shop’s traffic analytics don’t set a tracking cookie. No cross-site identifier, and no consent banner needed for them. The trade: you can’t reliably tell a returning visitor from a new one. What you get back is data that survives ad blockers and doesn’t turn your shop into a privacy problem.

The funnel

Measured from what people actually did, not guessed from page views:
1

Visit

Someone lands on your shop.
2

Product view

They open something.
3

Add to cart

They want it.
4

Checkout started

They mean it.
5

Order placed

They paid.
The totals matter far less than the gaps. A shop losing most of its traffic between add-to-cart and checkout has a completely different problem from one losing it between visit and product view.

Reading the drop-offs

Your landing page isn’t connecting, or the traffic arrived expecting something else. Check where it’s coming from.
Price, photos, description, or it’s out of stock. Out-of-stock products still get views, so check that first — it’s the cheapest thing to fix.
Usually the shipping cost, or a shipping destination you don’t cover. An address outside all your zones blocks checkout, which from their side just looks broken. → Shipping
Payment methods. If you only take crypto, this is where almost everyone stops. → Payment methods

Abandoned carts

The cart list is that fourth step, itemised — what was in it, and who to email if you know who they are. Abandoned carts

Getting it out

Available through the API with the analytics:read scope, if you want it in a spreadsheet or a dashboard of your own. Analytics API

Adding Google Analytics or similar

Possible through custom code, which needs your own domain. Bear in mind a third-party tag will usually drag a consent banner along with it, which the built-in analytics don’t.