Product usage analytics
Last updated 2026-06-19
Definition
Product usage analytics shows which features your own end-users actually use, how many distinct people use them, and how often. You drop a lightweight Quri Tag into your app, and Quri rolls events up into a top-features view on the Usage screen. Every user reference is hashed at the edge, so no raw email or login is ever stored.
How to do this in Quri
- Install the Quri Tag in your product and call trackFeature when a user uses a feature.
- Open /app/usage to read your top features ranked by distinct users and event count.
- Check the freshness line at the top to see how recent the rollup is.
- Upgrade to the Scale plan if the screen shows the upgrade prompt instead of your data.
Frequently asked
- Does Quri store my end-users’ personal data?
- No. The user reference you send is hashed at the edge before anything is stored, so Quri never keeps a raw email, login, or visitor id. Distinct-user counts still work because they count distinct hashes, not people you can re-identify.
- What about consent and data retention?
- Each event carries a consent flag, and events without consent are not attributed to a user. Stored rows carry a retention stamp and expire automatically once your window passes, so old usage data does not linger.
- Why is my Usage screen empty or locked?
- Empty means the Tag is not installed yet or no events have arrived; install it and send a trackFeature call. Locked means your plan does not include this surface — it unlocks on the Scale plan, and no end-user data is read until then.