How to use methodology for deep-dive reports
The methodology page now explains how the newer reports are worked out: deep dives, regions and cities, products, A/B tests, single-page apps, milestones and API feeds.


What it does
Seven new sections on /methodology, added below the existing ones (nothing was removed): the 92-day and 200,000-row limits of deep-dive screens and what a visitor-day is; how regions and opt-in city totals work with small-number suppression under 5; how product steps are matched within a day; the exact A/B test formula and when a winner is called; how hash routes are counted; how milestones are worked out; and how long API feeds are cached.
Why it matters
You should be able to check how every number is made. Cookie-free counting has limits, and they are written down rather than hidden.
How to use it
- Open /methodology.
- Use the list at the top to jump to Deep-dive reports, Regions & cities, Products, A/B tests, Single-page apps, Milestones or API & Sheets feeds.
- Read the limits before comparing numbers with another tool.
How it works
- Open /methodology and pick a section from the list at the top.
- Each section has the rule and its limits, taken from the code.
- Each report links back to its section.
Privacy
- Collected: Nothing new
- Not collected: Anything: this is documentation
- No cookies, and nothing stored on the visitor’s device.
- Reports show totals only: never a visitor list, IP address or single visit.
Limits
- Describes the rules as of 19 November 2026; the page says when it was last updated
Plans
Every plan, including Free. quietstats is free during launch: the Free plan covers 1 site and 5,000 pageviews a month, and no card is needed. See pricing.
Questions
Was anything removed from the methodology?
No. The new sections were added after the existing ones.
Where is the A/B test formula?
In the A/B tests section: /methodology#ab-tests.
Related
Feature page: Methodology for every deep-dive report → What it is, why it matters, privacy and how other tools do it.