Product analytics · Autessa Analytics
Feature adoption
Autessa Analytics reports feature adoption for your web app. It rolls every page of the app up into a named feature, so a specific record, file or report counts toward its feature, then shows users, companies, sessions and last use for each feature, a daily trend for the top five, and every milestone by times, people and companies.
The problem it solves
A list of URLs is not a list of features
Product analytics on raw pages produces thousands of rows: one for every record anyone opened. That hides the question that matters: which features do people use? Autessa Analytics maps routes to features by prefix, first match wins, and collapses ids, so the report reads in product language.
What you get
- Routes map to features by prefix (first match wins); the app root is Home and anything unmapped is Other.
- Record ids in URLs are collapsed, so one agent, file or report never becomes its own row.
- Features table: users, companies, sessions and last used, up to 100 features.
- Daily users by feature for the top five features.
- Milestones table: times, people and companies for each milestone event.
How it works
How does feature adoption work?
Routes are normalized
Each pageview’s route pattern has ids collapsed, so /agents/abc123 and /agents/xyz789 are the same route.
Routes become features
An ordered list of route prefixes names each feature, from “App builder” to “Drive” to “Company settings”.
Usage is counted
Users, companies and sessions are counted per feature for the range, with the last time each was used.
Trends are drawn
The five most used features get a daily users line, so a launch or a drop is easy to spot.
Every option
Feature report columns
| Option | What it does |
|---|---|
| Feature | The named feature a route belongs to; Home for the root and Other for unmapped routes. |
| Users | Unique people who viewed any page in the feature. |
| Companies | Distinct companies whose people used it. |
| Sessions | Unique sessions that touched it. |
| Last used | The latest pageview in the feature. |
| Daily users by feature | A line per feature for the top five by total users. |
| Milestones | Each milestone event with times, people and companies. |
Permissions
Who can do what?
| Who | Can |
|---|---|
| Anyone the app is shared with | Open every report, switch the date range, filter and search, and open people and replays in PostHog. |
| App admin | Share the app and its PostHog query tool with teammates, at read or edit level, and decide which tables they can change. |
| App builder | Edit the route-to-feature map in the app’s source to match your own product’s areas. |
Computed for you
Specific prefixes first
Feature mapping is ordered so specific prefixes win over general ones: an app viewer page counts as “Custom apps” before the broader app builder prefix is checked. That keeps similar areas from being merged.
Connected
How it connects to the rest of Autessa Analytics
FAQ
Questions about feature adoption
How does Autessa Analytics define a feature?
By route prefix. Each feature has one or more URL prefixes; the first match wins, record ids are collapsed, the root is Home and anything unmapped is Other.
Will each record show up as its own row?
No. Individual records such as a specific agent, file or report all count as their feature.
Can I see feature adoption over time?
Yes. Daily users by feature charts the top five features across the range.
100% customizable, code and all
Make Autessa Analytics fully your own.
Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.
Start free and make it yours