Time to event: how quickly people act
If people click your main button after 3 minutes, the page may be making them hunt for it.
How long after a visit starts each custom event first fires, as a typical time and a spread.
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
For each custom event name, quietstats measures the time from the first pageview of the visit to the first time the event happened, and shows the quick quarter, the typical (median) time, the slow quarter and the usual number of pages in those visits.
Why it matters
If people click your main button after 3 minutes, the page may be making them hunt for it. Very fast events can point to accidental clicks.
How it works
- Open your dashboard, go to Deep dives (or Reports on a phone) and open Analysis lab.
- Under Conversions, tap Time to event. 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 hidden
- Times are cut at 30 minutes, the end of a visit
- 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
What is the typical time?
The median: half the events happened sooner, half later. It is not thrown off by a few very slow ones.
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 conversionsTime on page
Behaviour and contentRe-read pages and conversion: does going back mean buying?
Goals, events and conversionsEvent order: which events lead to which
Goals, events and conversionsNew vs established landing pages: do fresh pages convert?
Goals, events and conversionsEvents by page: where your custom events happen
Goals, events and conversionsScroll depth and engaged time
Behaviour and content
All goals, events and conversions features → · All features → · Docs: Time to event 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.