The 'are they actually in the product' half of the health picture. It reads the usage pulse and answers, per account: sessions and active minutes and people, last seen, week-over-week trend, active seconds per module including the ones at zero, when in the week they work, who specifically uses it, and what device.
Also called: are they using it · who logs in · which features get used · active time · adoption
- 1Sessions and events are read for the last 30 days and summarised.
- 2Module heat lists every module including untouched ones, so the gaps are visible rather than absent.
- 3The heat map plots page views by weekday and hour.
- 4The per-person breakdown shows sessions, minutes, last seen, top module and device.
- 5A batch version computes every account in one pass for the overview table.
Built as the measurement half of the retention thesis — health could not be scored on configuration alone, so the module answers 'sessions + active minutes + distinct people… module heat (active seconds per module — most and least used)'. Listing zero-use modules is the point: the least-used module is as informative as the most-used one.
- Login counts said nothing about depth of use.
- Unused modules were invisible because they generated no rows.
- Nobody could see which specific people were using the product.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →