For SaaS teams
A signup number tells you almost nothing. The useful questions are where the flow loses people, whether last month's cohort is still here, and which first action separates the two.
Start freeYour funnel is spread across four screens
Landing page in one tool, signup events in another, activation in a spreadsheet. By the time you have joined them, the week is over.
Retention is a number somebody calculates by hand
Usually once a quarter, usually differently each time, usually just before a board meeting.
Nobody notices when tracking breaks
A property gets renamed in a refactor, a report quietly goes flat, and it is discovered a month later by somebody who thought the product was failing.
Funnels that name the step and the people
Drop-off is reported in people as well as percentages, and conversion is always measured from the first step, so the rate cannot be flattered by starting the funnel late.
A cohort grid that does not flatter itself
Retention by day, week or month, with periods that have not happened yet left blank rather than shown as zero. It needs a durable subject to count, which is the piece that is still missing: see below.
A tracking plan that fails loudly
Declare the events and property types you expect. A violation is flagged and stored, never dropped, and it appears in the debugger with the exact mismatch.
Segments on your own properties
properties.plan==pro or num.seats>=5 filters every screen in the product, not just one report.
The Customers and Revenue screens are built, and the identity that fills them is not. identify() reaches the event as a property, not as the user field those screens and the user-based cohort grid read, and the authenticated server endpoint that would set it properly is specified and unshipped. So today you get traffic, funnels, segments, the debugger and CSV export of all of it. If per-user retention or MRR beside behaviour is the thing you are buying, wait for that endpoint or use something else for now. Experiments are designed and not built either.
It is on the changelog with everything else we have not done. A roadmap item described as a feature is how software gets bought and then resented.
Two minutes to install, no card, and it runs alongside whatever you use today.
Start free