Your conversions, readable without opening five dashboards
Insights reads your own events, not the ones a platform is willing to hand back. Revenue net of tax and as charged, funnel, best sellers, most-viewed pages with the country they came from, and what your visitors searched for on your site.
And one thing no advertising dashboard will give you: the quality of your measurement itself, consent, identifiers, what each destination actually accepted, and the periods when nothing went out at all.
Five platforms, five truths, and none of them yours
You send the same conversion to Meta, Google Ads, GA4 and the rest. Each counts it its own way, in its own attribution window, and leaves you to arbitrate.
Figures that never reconcile
Reconciling four dashboards is a spreadsheet exercise you redo every month and nobody enjoys. And the result is still an estimate.
No view of what actually left
An expired key, a miswired consent, a destination refusing: none of that shows in advertising reports. They show what they received, never what they did not.
Net of tax, nowhere to be found
Platforms optimise on what the customer paid, and rightly so. But your books read net of tax, and that figure exists nowhere in their interfaces.
Net of tax, beside what was charged
Both, because both are true and serve different purposes: platforms optimise on what was taken, you read your books net of tax.
Revenue, on both bases
What was charged and the amount net of tax, per currency: never added together. Adding euros to Swedish crowns produces a figure nobody would ever catch.
Orders and average basket
Counted from the orders your shop actually validated, not from a thank-you page the customer may never have loaded.
Conversion rate
Event volumes, and the page says so explicitly: comparing them to a GA4 user count is comparing two different units.
Comparison with the previous period
Shown only when it means something. Comparing a complete period with a partial one always produces a fall, and it is not one.
What sells, what is read, what is searched for
Three questions a merchant actually asks, and can ask no advertising platform.
Best sellers
Views, adds to cart, purchases and quantities per product. The same product from one end of the funnel to the other, so you see where it drops off.
Most-viewed pages, filterable by country
The country comes from the visitor's connection, resolved at ingestion and never stored beside the address that produced it. The page says how many visits could be placed, rather than implying the split covers everything.
Searches run on your site
What your visitors typed into your own search box, not their Google queries, which nobody sees. A term with no result is a customer telling you what they came for and did not find.
A funnel that fits your site
A shop sees its checkout funnel. A site without a cart sees its own: page views, content read, contacts, leads, sign-ups, registrations. Decided on the window, not by a setting.
The quality of your measurement, measured
Four indicators a browser tag cannot produce, because it does not know what escaped it.
Consent coverage
How much of your traffic went out with consent granted, day by day. A fall here always precedes a fall in attributed conversions, by several days.
Identifier coverage
How many events carried enough to tie the conversion to a person. That is what decides match quality at the destination, and therefore the ROAS you will read.
What destinations accepted
Each platform's answer, event by event, with the exact reason for a refusal. An expired key shows up the same day, not at the monthly review.
The quiet periods
The moments when nothing went out. It is the costliest anomaly and the quietest: an empty dashboard reads like a bad week, never like an outage.
A score that announces what it does not yet know
Insights gives a signal health score out of 100. It is built to be checkable, not to flatter.
Every component says whether it is measured or estimated
Until a site has enough history, the component declares itself estimated and takes a neutral value. A measured 87 and an estimated 87 are not the same statement, and are not displayed the same way.
No verdict while there is nothing to judge
When most of the score is still estimated, the console writes “not enough data to rate yet” instead of a judgement, and shows no day-over-day comparison, which would be noise.
A small site is not a broken site
Steadiness is only scored above a volume where it means something. Below it, day-to-day variation measures the size of the site, not the quality of the tracking.
A missing value stays missing
The amount net of tax appears only if your shop declared it. We do not infer it from an assumed rate: a total says nothing about how much of it was tax.
Simple to install, with no cost added on top
A design decision, not a sales promise: there is nothing to host, and nothing to unlock tier by tier.
A module, like any other
The connector installs like any other extension of your shop. Nothing to host: no container to rent, no server to maintain, no subdomain to configure.
Every destination, on every plan
Including the free one. Plans differ only by the number of sites and events, no destination is reserved for a tier, which is nonetheless the norm.
Starting costs nothing
The free plan covers one site and 10,000 events a month, with no card. Nothing breaks if you go over the quota.
Frequently asked questions
Will your figures match Meta's or GA4's?
No, and no honest tool will promise otherwise. Each platform applies its own attribution window and its own modelling. Insights counts what your shop actually recorded: the one figure you are the source of.
Why show both net of tax and the amount charged?
Because both are true and serve different purposes. Platforms optimise on what the customer paid; your books read net of tax. The net figure appears only if your shop declared it: we do not infer it from an assumed rate.
What does an “estimated” score mean?
That the component does not yet have enough history to be measured, and takes a neutral value meanwhile. The console says so plainly and shows no verdict while most of the score is estimated: a measured 87 and an estimated 87 are not the same statement.
How long is my data kept?
Depending on your plan, and the console says so. Daily aggregates are kept longer than the event detail: a counter per day weighs nothing, an event log does.
The logical next step
Know what feeds these figures, where they go, and how to read them elsewhere.
What we measure
The 28 events behind these tables, and what a site without a shop sees.
Read API and MCP server
The same figures in your scripts, your dashboards or an assistant.
The seven destinations
What the console shows of each one's answer, refusals and reasons included.
PrestaShop module
The connector that sends the events read here.
WooCommerce plugin
The connector for WordPress and WooCommerce.
The free plan
One site, 10,000 events a month, no card.
Open the console and look at your own figures
Insights is included from the free plan. No commitment, no card.