About Scout
Scout is built on one unfashionable idea: a measurement tool is only worth having if it will tell you when it cannot measure something.
Last updated October 14, 2026
The problem it was built for
A store breaks quietly. A checkout step fails on one browser, a discount has no minimum order value, a theme update moves the add-to-cart button below the fold on a phone. Nothing errors. The dashboard still loads. Revenue is down nine percent and the only honest summary anybody can give is “it’s been a soft month”.
Analytics answers what happened, which is the first of three questions and the easiest. Scout is built for the two after it: why did it probably happen, and what should be done about it.
Revenue per visitor, not conversion rate
Conversion rate alone is gameable and routinely gamed. Put a site-wide discount up and conversion rate rises while you earn less per visitor; remove free shipping below a threshold and it falls while you earn more. A tool whose headline figure moves the wrong way for a good decision will eventually talk somebody into a bad one.
So revenue per visitor decides, conversion rate and order value explain it, and the funnel says which step broke. Five tiers, and only the top one is allowed to call a win.
What it refuses to say
Scout will not attribute a change to a week when something else shipped in it. It will not report a figure it cannot compute from a denominator it actually has. It will not label a guess as a finding, and it will not put a number inside a hypothesis — a guess with a figure in it reads as a measurement.
Each of those costs an answer somebody wanted. They are the reason the answers it does give are worth taking to whoever asked for them.
Why there is no uplift figure anywhere on this site
Every tool in this category leads with one. Scout cannot: nobody knows what a store they have not seen will do, and a percentage invented for a landing page is exactly the kind of number this product exists to stop you acting on. Publishing one would contradict the ledger on the page that sells the ledger.
It reads, and writes nothing
Scout holds no permission that can change a product, an order, a theme, a discount or a customer — and that is enforced in two places in the code rather than promised in a sentence here. The single exception is its own analytics pixel, without which counting visits is impossible.
It also reads less than it could. Customer names, addresses and payment details would make no diagnosis better and every breach worse.
Who makes it
Zinx. Scout is the diagnostic half of a pair — Zinx Signal runs the A/B tests Scout proposes when the fix is a judgement call rather than a bug. They are separate products with separate deployments, and neither can read the other’s data.