--- title: What metrics should you track for mobile app benchmarking? description: Download counts and DAU figures mislead. Learn which mobile app metrics truly matter for benchmarking, from retention rates to behavioural signals. image: https://weareaffective.com/hubfs/learning-centre-images/what-metrics-should-you-track-for-mobile-app-benchmarking.webp --- [Skip to content](https://weareaffective.com/learning-centre/what-metrics-should-you-track-for-mobile-app-benchmarking#main-content) [![we\_are\_affective\_logo\_200](https://weareaffective.com/hs-fs/hubfs/we_are_affective_logo_200.png?width=175&height=48&name=we_are_affective_logo_200.png "we_are_affective_logo_200")](https://weareaffective.com) - [Home](https://weareaffective.com) - About Us - [Our Story](https://weareaffective.com/about) - [How We Work](https://weareaffective.com/how-we-work) - Our Services - [App Planning & Strategy](https://weareaffective.com/app-planning-strategy) - [App Design](https://weareaffective.com/app-design-agency) - [App UX Design](https://weareaffective.com/app-ux-design) - [App UI Design](https://weareaffective.com/app-ui-design) - [App Technical Architecture](https://weareaffective.com/app-architecture) - [Existing App Audits](https://weareaffective.com/app-audit) - [Case Studies](https://weareaffective.com/case-studies) - [Pricing](https://weareaffective.com/pricing) - [Learning Centre](https://weareaffective.com/learning-centre) - [Get Started](https://weareaffective.com/get-started) Expert Guide Series # What metrics should you track for mobile app benchmarking? Table of Contents About a quarter of mobile apps are abandoned after a single use, according to [Localytics](https://uplandsoftware.com/localytics/resources/blog/25-of-users-abandon-apps-after-one-use/). The people who built those apps almost certainly knew their download numbers. They probably tracked daily active users. What they were not tracking was whether any of those users actually came back, found value, and stayed. That gap between acquisition data and retention data is where most mobile products quietly fall apart, and it is the gap that [a good benchmarking framework is designed to close](https://weareaffective.com/app-audit). > Download numbers can grow while retention quietly collapses, producing a false picture of product health. Benchmarking sounds like a measurement exercise. In practice it is a clarity exercise. The question is whether the right people are using the product in the right way, and whether the numbers you are watching are telling you something real or something flattering. Too many product reviews are built on figures that look healthy in a deck and say almost nothing about what is actually happening inside the app. This article sets out the metrics worth tracking, the benchmarks worth using, and the behavioural signals that sit beneath the headline numbers. We have drawn on our own work across lifestyle apps, including a water tracking product and an art-based auction game, to show what these patterns look like in practice and what they cost when they go unaddressed. ## Why download and DAU counts flatter to deceive Download numbers and daily active user counts are the two figures that appear most often in product reviews, investor updates, and team meetings. They are also among the least useful for understanding whether an app is genuinely working. Downloads measure acquisition, not engagement. DAU counts measure presence, not value. A user who opens an app for thirty seconds and closes it again contributes to the daily active user figure just as much as one who spends twenty minutes completing a meaningful task. Session length has the same problem. It looks like a proxy for engagement but it cannot tell you why a user stayed. We have said this clearly in previous work: is [session length up because users are getting real value](https://weareaffective.com/learning-centre/how-to-read-a-user-session-recording-for-emotional-signal-rather-than-task-compl) from the product, or because it is confusing, or because the product has been gamified to keep them inside it? The figure alone cannot answer that question. Without the context, session length is noise dressed as signal. The same applies to monthly active users. A user who logs in once a month to check something and leaves immediately counts the same as a daily power user. That aggregation hides the distribution completely. What teams end up with is a set of numbers that feel like progress and behave like vanity metrics, rewarding attention without earning it. Benchmarking against these figures does not improve products. It just reinforces the illusion that things are going well. ## The retention metrics that actually matter Retention is the metric that separates products users want from products users tolerate. Day-one retention tells you whether the first experience was strong enough to bring someone back. Day-seven retention tells you whether the product has built enough habit to survive a week. Day-thirty retention tells you whether users have incorporated the product into their lives in a way that sticks. These three numbers, tracked together, give a far more honest picture of product health than any acquisition figure. The benchmarks vary significantly by category, which matters for how you interpret your own numbers. But the direction of travel is consistent: apps routinely lose the majority of their users fast. On average, 77% of daily active users are gone within the first three days of download, according to [Andrew Chen](https://andrewchen.com/new-data-shows-why-losing-80-of-your-mobile-users-is-normal-and-that-the-best-apps-do-much-better/). Even strong products see a 40 to 50% drop after three days. The gap between 77% and 40% is the space where [good onboarding, clear value communication, and thoughtful early experience design](https://weareaffective.com/learning-centre/5-things-that-make-the-difference-between-so-so-apps-and-stellar-apps-what-your-) do their work. Track day-one, day-seven, and day-thirty retention as three separate figures. Do not average them. Each one diagnoses a different problem in the user journey. Day-one retention below 50% is a warning. It does not necessarily mean the product is broken, but it means the first experience is not doing enough to earn a return visit. For teams spending money on user acquisition, that shortfall has a direct financial cost: [every pound spent bringing a user in is wasted](https://weareaffective.com/learning-centre/what-changes-about-retention-economics-between-a-15-and-a-40-repeat-rate-in-life) if they leave before seeing any value. ## Design that understands *your* users We build app experiences around real user behaviour, not assumptions. Research, psychology-driven design and technical specs that turn users into loyal advocates. [See how we work](https://weareaffective.com/how-we-work) [Get started](https://weareaffective.com/get-started) No commitment ## Early drop-off: what the first three days reveal The first three days of a user's relationship with an app are disproportionately revealing. What happens in that window shapes whether the user builds a habit or quietly disappears. On a water tracking app we developed, we observed exactly the pattern the finance app data describes: a significant drop-off between day one and day thirty, occurring despite the absence of any obvious complaints or negative feedback. The silence felt like approval. The retention data told a different story. This is the trap that Simon describes clearly: it is easy to assume no news is good news, but with mobile apps the opposite is true. Users do not write in to say they have stopped caring. They simply close the app and do not return. By the time that shows up in aggregate data, the window for intervention has usually passed. > Users rarely explain why they leave. Retention data is the only thing that tells you they have gone at all. The first three days reveal specific things. A sharp drop between install and day one usually points to onboarding: the [first experience did not communicate value quickly enough](https://weareaffective.com/learning-centre/what-the-first-thirty-seconds-of-a-hospitality-app-teach-us-about-the-three-laye). A drop between day one and day three often points to habit triggers: there was nothing pulling the user back in. A slower decline into day seven suggests the product has some grip but has not yet become a routine. Each shape has a different fix, which is why the three-day window deserves granular attention rather than a single retention rate rolled up across the period. Map your day-zero to day-three drop-off against your onboarding flow. If users leave before completing setup, the first experience is the problem. If they complete it and still leave, the value proposition is the problem. ## Benchmarking retention against your category, not the average Cross-category averages are useful for orientation but dangerous for diagnosis. A 30-day retention rate of 39% would be strong for a fitness app and unremarkable for an e-commerce product. According to [Statista](https://www.statista.com/statistics/384224/monthly-app-launches-churn/), retail and e-commerce apps achieve 39% retention at day thirty, the highest of any category. A wellness or lifestyle app sitting at 39% is performing like an average retail product in a completely different market. The comparison you want is against direct competitors in the same category, at the same stage, with a similar business model. That requires access to category-specific benchmarking data, which is harder to find and less often published. But the effort is worth it. Benchmarking a mental health app against the average app is close to meaningless when that category has some of the lowest retention rates of any product type. The category context changes what the number means. | Category | Day-30 Retention | Day-90 Retention | | --- | --- | --- | | Retail and e-commerce | 39% | 22% | | Travel and lifestyle | Not stated | 23% (highest at 90 days) | | Personal finance (top 10) | 38% | Not stated | | Mental health | ~3% | Not stated | Stage matters as much as category. An early-stage app with a small marketing budget should not be benchmarking itself against a category leader with years of data and a large acquisition team. The relevant comparison is with products at a similar level of maturity, not the ones that have already solved the retention problem you are currently trying to diagnose. ## Behavioural signals buried beneath your headline numbers Headline retention and DAU figures tell you what happened. Behavioural signals tell you why. These signals require more granular data than the average team collects by default, but they are the difference between knowing a problem exists and knowing where in the experience it lives. The specific patterns worth tracking are time on screen, instances of a user entering a screen and returning to it repeatedly, and scrolling behaviour, particularly repeated up-and-down movement through content-heavy or legal pages. A user who spends forty-five seconds on a terms screen, scrolls down, scrolls back up, and scrolls down again is telling you something. That behaviour signals either confusion about what they are agreeing to or a lack of trust in the product presenting it. Neither is neutral. Both are fixable if you can see them. Set up event tracking for screen re-entries and repeated scroll patterns, not just page views. A user who visits a screen three times in a session is experiencing friction that a single-visit count will never capture. Dwell time and movement speed through the product also carry information. A user moving quickly is either confident or skipping. A user moving slowly is either engaged or lost. The distinction matters and it shows up in the surrounding context: [what they do after the slow section, whether they complete the task](https://weareaffective.com/learning-centre/what-a-development-team-actually-needs-to-know-about-the-user-before-sprint-one) or abandon it, whether they return. These are all trackable. Teams rarely track them because the dashboard defaults to session length and page views, which are easier to collect and easier to misread. ## When content supply drives churn, not the product itself One of the more counterintuitive retention problems is where the product itself is working but the content feeding it has run dry. The user experience is sound. The onboarding is clear. The [habit loop is well designed](https://weareaffective.com/learning-centre/why-product-owners-should-write-the-users-second-session-before-the-first-one). But there is simply not enough fresh material to sustain ongoing engagement, and so users drift away from a product they actually like. We saw this directly on a project we ran for an art-based auction game with real-money prizes. Early retention sat in the mid-sixties to low seventies, which was strong. As the supply of available games declined over time, usage became sporadic rather than consistent, and retention fell to around 30 to 35%. We flagged this clearly. The client's response was to prioritise new feature development rather than addressing the content supply problem. The features did not stop the decline because they were solving the wrong problem. When retention eventually reached that low point, the team refocused on what the core user journey actually needed: enough games available to make regular play worthwhile. Once the content supply improved, retention recovered to the mid-sixties to low seventies. It took time to rebuild, because users who had drifted away do not return automatically when the underlying problem is fixed. The trust erodes during the gap and rebuilding it requires sustained effort, not just a product update. The lesson is that benchmarking retention without understanding what is driving it produces incomplete diagnoses. A content-driven product needs to track content availability alongside engagement metrics. Without that, a fall in retention looks like a product problem when the actual cause is operational. ## Engagement quality versus engagement volume Volume metrics count events: sessions opened, screens visited, minutes spent. Quality metrics ask whether those events represent genuine value. The distinction matters because a product can score well on volume while performing poorly on quality, and the volume numbers will make it look like things are going well. Consider the difference between a user who opens an app daily to complete a specific task and a user who opens it daily because a push notification pulls them in, spends two minutes looking at content they do not act on, and leaves. Both contribute equally to the daily active user count. One is building a habit around genuine value. The other is responding to a stimulus and finding nothing worth staying for. Volume metrics cannot tell those apart. The signals that get closer to quality include task completion rates, feature adoption depth, and return-visit patterns tied to specific actions rather than general opens. A user who returns on day three because they completed a task on day two and found it useful is a different user from one who returns because a notification arrived. Separating those patterns requires more deliberate instrumentation, but the payoff is a clearer picture of [which parts of the product are earning engagement](https://weareaffective.com/learning-centre/why-do-some-apps-feel-like-they-were-made-just-for-you) and which are borrowing it from notification pressure. - Task completion rate per session - Feature adoption rate over the first seven days - Return visits triggered by in-product moments versus push notifications - Session depth: how many meaningful actions per visit - Notification opt-out rate over the first thirty days ## How to build a benchmarking framework worth trusting [A benchmarking framework is only as useful as the questions](https://weareaffective.com/learning-centre/how-much-should-i-actually-spend-on-strategy-before-i-start-building) it is designed to answer. The most common mistake is building a dashboard that answers "what are our numbers?" when the useful question is "are our numbers telling us the truth?" Those are different exercises and they produce different outputs. #### Start with the right comparisons Set your benchmarks against category-matched competitors at a similar stage of maturity. Use your own historical data as a baseline wherever you have it. A product that was retaining 60% on day one six months ago and is now retaining 48% has a story to investigate regardless of how that compares to the category average. Your own trend line is often more useful than an external benchmark. #### Build the framework in layers Layer one covers acquisition and basic retention: downloads, day-one, day-seven, day-thirty. Layer two covers behavioural signals: screen re-entry rates, dwell time on friction points, task completion. Layer three covers quality signals: which features drive return visits, what actions correlate with thirty-day retention, where users disengage in the session flow. Each layer adds resolution. Teams that operate only at layer one routinely wonder why the data feels inconclusive. Run the removal test on engagement mechanics periodically. Turn off a feature or reduce a notification cadence for a subset of users and observe what happens. If engagement holds, the mechanic was adding noise rather than value. If it drops meaningfully, the mechanic was earning its place. This is the clearest way to distinguish genuine engagement from manufactured presence, and it is one of the most informative experiments a product team can run with no external data required at all. ## Conclusion The metrics teams track by default are the ones that are easiest to collect and most comfortable to report. Downloads go up, DAU looks stable, session length holds, and the product appears healthy. What those numbers rarely reveal is whether users are finding genuine value, whether retention is quietly sliding, or whether engagement is being sustained by mechanics that obscure a deeper problem. Good benchmarking replaces comfortable numbers with useful ones. It means tracking retention at day one, day seven, and day thirty as separate signals rather than a blended average. It means comparing your numbers against your category, not the global average. It means instrumenting for behavioural signals, not just volume events, and building the habit of asking what a metric is actually measuring before deciding whether it is good news. We learned this most clearly on the auction game project, where retention data told a story that surface-level engagement metrics were masking entirely. Content supply was the problem, feature development was the proposed solution, and the retention numbers were the only thing that eventually made the actual cause impossible to ignore. That gap between what the data showed and what the team wanted to believe is the gap that a properly constructed benchmarking framework is designed to close. The framework is disciplined. It asks whether the numbers you are watching are measuring the thing you care about, and whether the comparisons you are making are honest ones. If the answer to either question is no, the metrics need to change before the product strategy can improve. [Let's talk about your app's retention metrics](https://weareaffective.com/get-started) and build a framework that gives you an accurate picture of what is actually happening. ## Frequently Asked Questions Why are download numbers and daily active users unreliable for measuring app performance? Downloads only measure acquisition, not whether users find genuine value in the product. A daily active user who opens an app for thirty seconds and closes it again counts the same as someone who spends twenty minutes completing a meaningful task, which makes the figure deeply misleading. What is mobile app benchmarking and why does it matter? Benchmarking is the process of measuring your app's performance against meaningful metrics and industry standards to understand whether it is genuinely working. It is less a measurement exercise and more a clarity exercise, designed to close the gap between flattering acquisition data and the harder truth of how users actually behave. Which retention metrics should product teams focus on? Day-one, day-seven, and day-thirty retention are the three most important figures to track together. They tell you whether the first experience was strong enough to bring users back, whether a habit has formed, and whether the product has become a meaningful part of someone's routine. Why can session length be a misleading metric? Session length cannot tell you why a user stayed in the app, only that they did. A long session might reflect genuine value, but it could equally reflect a confusing interface or gamification mechanics designed to keep users inside the product rather than help them. What is the difference between acquisition data and retention data? Acquisition data, such as download counts, tells you how many people found and installed your app. Retention data tells you how many of those people came back, found value, and stayed, which is the far more important question for understanding long-term product health. How can monthly active user counts give a false picture of an app's health? Monthly active users aggregate very different types of behaviour into a single figure. A user who logs in briefly once a month counts exactly the same as a daily power user, which completely hides the distribution of engagement and can make a struggling product appear healthier than it is. Do retention benchmarks differ depending on the type of app? Yes, benchmarks vary significantly by app category, which means you need to interpret your retention figures in the context of your specific market. Comparing your numbers against the wrong category benchmark can lead teams to draw the wrong conclusions about whether performance is acceptable. What happens when product teams focus too heavily on vanity metrics? Teams end up with numbers that feel like progress but say very little about what is actually happening inside the app. Benchmarking against vanity metrics does not improve products. It reinforces the illusion that things are going well while the real problems go unaddressed. ## Related Articles [![We Are Affective](https://weareaffective.com/hubfs/we_are_affective_logo_mark.svg)](https://weareaffective.com) 20-22 Wenlock Road London, N1 7GU United Kingdom +44 20 4572 8062 [hello@weareaffective.com](mailto:hello@weareaffective.com) Services [App planning & strategy](https://weareaffective.com/app-planning-strategy) [App design](https://weareaffective.com/app-design-agency) [App UX design](https://weareaffective.com/app-ux-design) [App UI design](https://weareaffective.com/app-ui-design) [App technical architecture](https://weareaffective.com/app-architecture) [Existing app audits](https://weareaffective.com/app-audit) Legal [Privacy policy](https://app.termly.io/policy-viewer/policy.html?policyUUID=b8fa9921-7518-4fb5-8ddd-9dc7f5977ed2) [Terms](https://app.termly.io/policy-viewer/policy.html?policyUUID=8b6a6ad5-91bd-4176-a5f7-6d36b0398f70) Case studies [TravAI](https://weareaffective.com/case-studies/travai) [Meditech](https://weareaffective.com/case-studies/harley) [WorkingWeight](https://weareaffective.com/case-studies/workingweight) [SkinSync](https://weareaffective.com/case-studies/skinsync) [Three Lochs](https://weareaffective.com/case-studies/three-lochs) [Drift](https://weareaffective.com/case-studies/drift) About us [Our Story](https://weareaffective.com/about) [How We Work](https://weareaffective.com/how-we-work) Guides [Creating an app](https://weareaffective.com/how-to-create-an-app) [Building an MVP](https://weareaffective.com/building-an-mvp) [Cost and budgeting](https://weareaffective.com/app-development-cost) [App technology](https://weareaffective.com/app-development) [Planning and strategy](https://weareaffective.com/app-planning-strategy) [User research](https://weareaffective.com/app-user-research) [Onboarding design](https://weareaffective.com/app-onboarding-design) [User psychology](https://weareaffective.com/user-psychology-app-design) [Launch and growth](https://weareaffective.com/app-launch-growth) Copyright © 2026, weareaffective.com. All rights reserved.