There is a particular kind of tiredness that comes from running a shop across six dashboards. The orders are in WordPress, the traffic is in Google, the ad spend is in three more places, and the one number you actually wanted — did this month make money — exists in none of them.
This is about pulling that back into one place you own, what is genuinely achievable today, and the one piece that still is not.
What “self-hosted” should mean
The phrase gets used loosely, so it is worth separating three different claims:
Your data stays in your database. Orders, customers, costs and margins live in your own MySQL tables and are not copied to anyone’s servers. For most people this is the one that matters — it is a GDPR position as much as a technical one, because a customer list sent to a third-party analytics product is a transfer you have to account for.
The reporting runs on your server. No external service renders your reports, so there is no second login, no per-seat pricing, and no vendor that can deprecate the view you depend on.
The data is collected by your server. Visitors counted by your own site rather than by Google Analytics. This is the strictest claim and the rarest one, and it is where most tools — including, honestly, most of this category — are still relying on someone else.
The first two are achievable today with a WooCommerce reporting plugin. The third is a different problem.
What WooCommerce already holds, and what it does not
Your WooCommerce database already contains, with no external service involved at all:
- Every order, its line items, totals, taxes and shipping
- Refunds, and when they were issued
- Coupons used, and what they discounted
- Customers, their order history, and whether each order was their first
- Since WooCommerce 8.5, order attribution — the source it believes brought each order in
That is an unusually complete commercial record. Revenue, average order value, refund rates, repeat purchase behaviour, product and category performance, and new-versus-returning revenue can all be reported without a single byte leaving your server.
What it does not hold is anyone who did not buy. WooCommerce has no visitor count, so it has no conversion rate, no traffic sources for non-converting sessions, no device breakdown, no landing page performance. That information requires something watching the front end, and WooCommerce is not watching.
The honest state of the visitor problem
Any plugin that shows you a WooCommerce conversion rate is getting the visitor half from somewhere. Today the options are:
Google Analytics 4. Ubiquitous, free, comprehensive — and the thing people adopting self-hosted analytics are usually trying to get away from. It also means a consent banner in the EU, and sampling on larger sites.
Plausible or Fathom. Privacy-first, lightweight, often cookieless enough to avoid a consent banner. Still a third-party service, still a subscription, but a far smaller transfer of data.
Jetpack Stats. Already present on a great many WordPress sites. Simple numbers, limited breakdowns.
First-party tracking. Your own site records the visit. No third party, no consent banner for analytics, no sampling, and the data is yours — but somebody has to build and maintain it, and doing it well is harder than it looks.
Most WooCommerce reporting plugins read one of the first three. It is worth knowing which, because it determines whether “self-hosted” describes your reports or your data collection — those are very different promises and they are routinely conflated in marketing copy.
What to look for
If keeping things on your own server is the point, the questions worth asking of any plugin:
- Where are the computed figures stored? Daily totals written into your own database can be reported instantly and survive the vendor disappearing. Figures fetched live from an API on every page load are slow, and vanish with the integration.
- Does it send order or customer data anywhere? Ask directly. “Analytics” in a plugin description can mean it reports on your store, or that it reports on you.
- What happens when an integration fails? A well-built tool keeps the last good figure for a day rather than writing a zero over it — otherwise a failed API call becomes a hole in your history that looks like a bad trading day.
- Can you get your data out? CSV on every table, at minimum.
- Does it need a consent banner? If it depends on GA4, yes, in the EU — and that is a conversion cost, not just a compliance one.
Where Vantage sits
Vantage Dashboard reports inside your WordPress admin. Orders, customers, costs and margins are read from your own database and never sent anywhere; the daily totals it computes are written into your own tables, so reports open from local data rather than waiting on an API.
Where it still depends on someone else is visitors. Conversion rate, traffic by channel and the device breakdown are read from GA4, Search Console, Plausible or Jetpack Stats, whichever you connect — and the rows are then stored locally, so a report over last year does not depend on anyone’s retention window.
Collecting visitors directly, without any of those, is a planned feature and the single largest one on the roadmap — visitors, sessions, sources, devices, page performance and search terms, gathered by the plugin rather than fetched from Google. The storage it will write into is already the same per-day structure the current integrations fill, which is deliberate: it replaces the collector rather than the reporting. But it does not exist today, and a page about self-hosted analytics would be worth nothing if it were vague about which half is which.
So: your commercial data is already fully self-hosted. Your visitor data is not yet, in this or in most of what you will find.
The Vantage Dashboard page lists what is in each tier, and the live demo is a real WordPress admin with the reports in it. No signup; it resets every hour.

