What this guide covers
Qusto is built around the buying journey: product views, add-to-cart, checkout, and revenue as the default view — not custom events you wire up and hope survive the next theme update. This guide walks through what that means in practice, tier by tier, and where to look when a specific question comes up.
If you are evaluating privacy implications or need language for your privacy policy, start with the guide for DPOs and privacy leads. If you are ready to go live, the install guide or Shopify app is the faster path.
Starting with Core
Plain traffic counts, no tracking cookies, and your store's order totals once the store is connected. Ask us about consent in your market.
Open source so you can trust it. Managed so you don't have to run it. On Shopify, a channel is named when the shopper says yes. An AI-referral tie needs a yes.
When Growth becomes worth it
Every order your store takes, a channel on Shopify when the shopper says yes, and a clear count of the orders with no channel. The count covers web-storefront orders. POS, draft, subscription, and marketplace orders are not in it.
Three areas tend to matter most:
- Cart-abandonment visibility — see where checkout thins out, step by step.
- Repeat-buyer context — on Shopify, which channels bring customers who return, when the shopper says yes.
- Revenue by geography — on Growth and above, connect markets to revenue and cart drop-off, not only visitor counts on a map.
Finding answers in the dashboard
Every store asks slightly different questions. These are the ones we hear most often:
| If you are wondering… | Start here |
|---|---|
| Which channels actually lead to orders? | Overview → sources, then the Revenue page |
| Where does checkout lose people? | Funnels; cart-abandonment visibility on Growth+ |
| Which countries or regions drive revenue? | Revenue → Revenue by Market on Growth+ |
| Does analytics need a yes in my market? | Ask us about consent in your market. In Germany, traffic counts wait for a yes. See the DPO guide. |
Running Qusto alongside what you already have
You do not need to rip out Google Analytics or another incumbent tool on day one. Many stores add Qusto in parallel, compare what each tool shows for a few weeks, and only then decide whether to promote it to first-class analytics. That low-risk path is often the easiest way to get buy-in from a team that is cautious about touching production tracking before a busy season.