1. What an EU Shopify operator actually needs
You need to know what sells, where buyers come from, and where the checkout drops off, without operating a ClickHouse cluster. You also need a count of the orders with no channel — because the visit declined, a script was blocked, or an AI agent placed the order without loading a page. On Shopify, a channel figure says what share of orders it covers.
2. Short answer
If you run a Shopify store in the EU and want store-native measurement with no tracking cookies, look at tools built around revenue and checkout, not only pageviews. Qusto is designed for exactly that job. On Shopify, a channel is named when the shopper says yes. General privacy tools (Plausible, Fathom) are strong on lightweight traffic; Rybbit is broad and self-host-friendly; Vantevo is store-native at a similar entry price; heavy product analytics (PostHog, Amplitude) is overkill for most SMB stores. Ask us about consent in your market.
3. Comparison
| Qusto | Plausible | Rybbit | Fathom | Vantevo | |
|---|---|---|---|---|---|
| Cookieless by default | ✅ | ✅ | ✅ | ✅ | ✅ |
| Shopify revenue and order context | ✅ Built in (order feed + tag, reconciled) | Partial — revenue goals | Partial — Shopify integration | — | Partial (claimed; docs partial) |
| Product → cart → checkout funnels | ✅ The store journey | Generic funnels | Funnels | — | Partial |
| Orders you can't trace to a channel (order-record reconciliation) | ✅ Data Monitor, every plan | Not documented | Not documented | Not documented | Not documented |
| EU data residency by default | ✅ Frankfurt | ✅ EU (US optional) | Self-host / hosted | EU option | ✅ |
| Open-source core | ✅ AGPL Community Edition | ✅ Community Edition | ✅ | — | — |
| Managed option | ✅ | ✅ | Hosted offered; self-host focus | ✅ | ✅ |
Where Plausible wins: brand recognition, a large content library, simple sites.
Where Rybbit wins: feature breadth when self-hosted; see Qusto vs Rybbit.
Where Fathom wins: simplicity for content and marketing sites.
Where Vantevo sits: store-native positioning at an entry price in the same band as Qusto Core, but no open-core path and documentation that is still partly in beta.
Where Qusto fits: the EU Shopify operator who wants privacy and store depth without stitching tools — and who wants the one number none of the general tools give you.
4. The number only store-native reconciliation gives you
Qusto reads your store's order feed server-side and matches each order to a browser session where one exists. The orders with no matching session — declined consent, blocked scripts, or an agent-placed purchase that never loaded a page — are counted, with their value, as orders you can't trace to a channel. It is your own order record, not an estimate, so you can check it. For a pre-install estimate, the consent-tax calculator shows the modelled range; the real number appears in Data Monitor once orders flow.
5. Setup reality
Qusto installs with a tag and the Shopify order feed; Qusto sets no tracking cookies; whether analytics needs consent depends on your market and stack (confirm with your DPO — the DPO guide is written for that conversation). Setup is measured in minutes, not weeks, and Qusto runs happily alongside GA4 while you compare.