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
Core gives you a clear picture of traffic and revenue without asking visitors to accept a cookie banner — when your overall stack matches Qusto's cookieless model (your DPO can confirm that for your store).
Out of the box you can see where visitors come from — including AI assistants and search — and how that activity connects to revenue. Because Qusto is open-core, the privacy architecture is something you or your team can inspect in the code, not just take on trust. If you prefer not to run infrastructure yourself, managed hosting is available when you are ready.
When Growth becomes worth it
Many operators hit a familiar wall: traffic looks fine, ad spend keeps flowing, but the link between channel and order stays fuzzy — especially once consent banners thin out what cookie-based tools can see. Growth is designed for that moment.
Three areas tend to matter most:
- Cart-abandonment visibility — see where checkout thins out, step by step. This is measurement and insight, not automated recovery emails.
- Repeat-buyer context — understand which channels bring customers who return, not just one-time visitors.
- 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 Recovery on Growth+ |
| Which countries or regions drive revenue? | Revenue → Revenue by Market on Growth+ |
| Do we still need a cookie banner for analytics? | That depends on your full stack — your DPO can walk through it in the privacy 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.