Events by page: where your custom events happen
It shows where a button gets pressed most for the views it gets, which pages a download really comes from, and where an event never fires.
Which pages each custom event fires on, per 100 views of that page.
Why quietstats: you get this without cookies, a consent banner or storing IP addresses, in every plan including Free.
In every plan, including Free. Goals, events and conversions.
📘 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 puts each custom event on the page the same visitor was viewing when it fired, and lists page and event pairs with the events, the page’s views and events per 100 views.
Why it matters
It shows where a button gets pressed most for the views it gets, which pages a download really comes from, and where an event never fires.
How it works
- Open your dashboard, go to Deep dives (or Reports on a phone) and open Analysis lab.
- Under Conversions, tap Events by page. 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
- Pairs with fewer than 5 events, or pages with fewer than 5 views, are hidden
- Shows the top 30 pairs
- 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
Is this the same as Events by landing page?
No. That one groups events by the page a visit started on; this uses the page the event actually fired on.
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
Goals, events and conversionsCustom events and conversion rates
Goals, events and conversionsClick map: clicks per link and button on each page
Behaviour and contentEvent order: which events lead to which
Goals, events and conversionsSection conversion: which parts of your site convert
Goals, events and conversionsTime to event: how quickly people act
Goals, events and conversionsGoal mix over time: which goals are growing
Goals, events and conversionsLive visitors and live events
See your traffic
All goals, events and conversions features → · All features → · Docs: Events by page 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.