Change breakdown: more visits, or more per visit?
A rise in pageviews from more visits is a marketing win; a rise from deeper visits is a content win.
How much of a change in pageviews came from more visits and how much from more pages per visit, and the same for conversions with a goal.
Why quietstats: you get this without cookies, a consent banner or storing IP addresses, in every plan including Free.
In every plan, including Free. Reports, sharing and alerts.
📘 Step-by-step guide, with screenshots and diagrams →
Start free, no cardSee live demo
- No cookies or consent banner
- No IP addresses stored
- Groups under 5 visitors hidden
- 845-byte script
- Free plan, no card


What it is
quietstats compares this range with the one before. Pageviews are visits × pages per visit, and conversions are visits × conversion rate, so each change splits into two parts using logarithms. A table shows before, now, change and each part’s share.
Why it matters
A rise in pageviews from more visits is a marketing win; a rise from deeper visits is a content win. Knowing which tells you what is working.
How it works
- Open your dashboard, go to Deep dives (or Reports on a phone) and open Analysis lab.
- Under Tools, tap Change breakdown. You can also search for it on the All reports screen.
- Pick a date range (and any options at the top), read the “How to read this” notes, and download any table as CSV.
Privacy: what is and isn’t collected
Collected
- Nothing new: it reads the pageviews, events, goals or daily totals you already have
Never collected
- Anything about a single visitor
- Links between days: visitor ids still reset at midnight
- Cookies, localStorage or anything else stored on the visitor’s device
- IP addresses or user agents (used in memory, then discarded)
- Anything that links a visitor across days (the visitor ID resets daily)
Rows and limits
- Needs 5 or more visits in both periods
- Pick a goal to add conversion rows
- Up to 92 days and 200,000 pageviews per screen
- Read from the database only when you open it, then kept for 10 minutes
“Rows” are database rows written, which is what our hosting is billed on. Reads are not rows written. Methodology →
Questions
Why can a share be over 100%?
When the two parts pull in opposite directions, one part can be bigger than the whole change.
Does it store anything new?
No. It is worked out from the pageviews and events you already have when you open the screen, and only the totals are kept for 10 minutes.
Related features
See your trafficWhy did this change?
See your trafficCompare any two date ranges
See your trafficMix effect: did the audience change, or behaviour?
Reports, sharing and alertsMetric correlation: which daily numbers move together
Reports, sharing and alertsPage vs page: two landing pages side by side
Reports, sharing and alertsCopy Toolkit lists to another site
Reports, sharing and alertsHour-by-hour change: which hours gained or lost
See your traffic
All reports, sharing and alerts features → · All features → · Docs: Change breakdown guide → · Compare features with other tools →
Guides on this topic
Set it up
Nothing to set up: it works with the standard one-line script.
<script data-host="https://quietstats.co.uk" data-dnt="true" src="https://quietstats.co.uk/js/script.js" id="YOUR_SITE_ID" async defer></script>Try it on your own site
Free during launch: one site and 5,000 pageviews a month, no card needed. After launch, paid plans start at £5 a month.