Event trends: every custom event, week by week
Events are easy to set up and easy to forget.
See every custom event week by week, per 100 visits, with a plain label saying whether the change is real or could be noise.
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 counts each custom event name (clicks, downloads, outbound links, form sends and your own qs() events) per week, works out events per 100 visits, and compares the second half of the range with the first using a simple count test. Each event gets a small weekly chart and a “Clear change”, “Probably real” or “Could be noise” label.
Why it matters
Events are easy to set up and easy to forget. One screen that shows them all moving week by week tells you which buttons and downloads are gaining or losing interest.
How it works
- Open your dashboard, go to Deep dives (or Reports on a phone) and open Analysis lab.
- Under Conversions, tap Event trends. 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
- Events seen fewer than 5 times are left out
- Event properties are not split out here; use Custom events for that
- 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
Which events are included?
Every custom event name: data-qs-event clicks, qs() calls, outbound links, downloads, form sends and video plays.
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 conversionsOutbound links and file downloads
Goals, events and conversionsTrend charts, headline cards and any date range
See your trafficOrder value trends: orders, revenue and average order by week
Goals, events and conversionsTargets and pacing: monthly targets with a projection
Goals, events and conversionsConversion by visit depth: does a second page matter?
Goals, events and conversionsConversion timing: the weekdays and hours that convert best
Goals, events and conversionsContent trends: fading and growing pages
Behaviour and content
All goals, events and conversions features → · All features → · Docs: Event trends 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.