A feature is a funnel, not an event count.
Each feature is three steps — seen, started, finished — counted in unique people. Tapll shows how many get through each step, where they stop, and how the numbers differ between versions.
The problem. Sound familiar?
- An event that fires a thousand times a day and says nothing about whether anyone finishes.
- A new version where the feature quietly stopped sending its success event.
Where Tapll answers it.
- 01
Three steps
Discovery, adoption and success per feature, with completion and drop-off rates.
- 02
Per version
Adoption per 1,000 sessions of each version, so a release that broke a feature stands out.
- 03
Example sessions
Real sessions behind every number, one click away.
In the docs: Declaring features
Questions.
Do I have to map events by hand?
No. Declare the role in code, or accept a suggestion: Tapll groups events by name and never creates a feature without your approval.
Other questions.
- Who is in my app right now?A live view of the people in your app, the screen each is on, and what just happened.Read more
- Did my last release help or hurt?Each version’s adoption, crash-free rate and the app’s numbers in the days before and after it.Read more
- Which features go with subscribers?Feature adoption next to subscriptions and retention — labelled as correlation, never as cause.Read more
- How does my App Store listing convert?Search impressions to downloads per market, keyword positions, rivals and who sent the downloads.Read more
- Which channels bring paying customers?Stripe and Paddle payments next to the channel and campaign of the visit that made them.Read more
- Can I measure my site without a cookie banner?Strict anonymous by default: nothing stored in the browser. A built-in consent banner when you want identity.Read more
- How does my landing page feed my app?The website and the app in one project, with a platform switcher, and the App Store’s referrers beside the site’s channels.Read more