What App Metrics Do Investors Really Care About?

Founders pitching for investment will often open with their download numbers. It feels like the natural place to start: the app exists, people are finding it, the graph goes up and to the right. But a growing number of investors have stopped treating downloads as meaningful signal, and the founders who understand why are the ones who come into those rooms better prepared.

The graph going up and to the right on downloads tells you nothing about whether anyone stayed.

The shift is straightforward. Downloads tell you how good your marketing is. Retention, activation, and engagement tell you whether the product actually works. Investors who have backed a few apps that looked healthy on acquisition and then quietly collapsed on everything else have learned to ask different questions. Those questions now have a shape, and understanding that shape before you build your pitch deck is worth a great deal.

At We Are Affective, we work with product teams at various stages of development, and the conversations we have about metrics tend to surface the same gaps. Teams track what is easy to track. They optimise for what their dashboard shows by default. So the purpose of this piece is to map the metrics that investors actually interrogate, explain why each one matters, and connect them to the design and behavioural decisions that drive them.

Why Download Counts Mislead Everyone in the Room

Download numbers are visible, satisfying, and easy to communicate. They feel like growth. The problem is that they measure the top of the funnel only, and the top of the funnel is mostly a reflection of your marketing budget and your app store optimisation, not your product.

What we have seen consistently is that teams watch their download numbers rising and read that as a sign the product is healthy. The retention numbers tell a different story. Around 77% of daily active users stop using an app within the first three days of installation, according to Business of Apps. That figure sits alongside a download chart that often shows steady growth across the same period. Both things are true simultaneously, which is why downloads mislead: they do not contradict the churn, they just hide it.

Simon Lee, who leads product strategy at WAA, puts it plainly: you can watch your download numbers grow and feel reassured while a significant proportion of users are leaving at day three, day five, and day seven without saying a word. The acquisition side looks fine. The retention side is failing. And because teams rarely track both with equal rigour, they do not see the gap until an investor asks for the cohort data.

The corrective is not to stop tracking downloads but to stop treating them as a proxy for product health. They belong at the top of a dashboard alongside the metrics that tell you what happened after the install, not in place of them.

Retention Curves: The Metric That Shows Whether People Stay

A retention curve plots the percentage of users who return to an app on each day after first install. Day one, day three, day seven, day thirty. The shape of that curve tells you more about product health than almost any other single view.

Day-one retention across mobile apps sits at roughly 25%, according to Adjust benchmarks. That is the baseline. A product performing at the average is already losing three quarters of its users before the second day. What investors want to see is a curve that flattens rather than continuing to fall steeply, because a curve that flattens indicates a retained core who have found real value.

On the water tracking app we developed at WAA, we observed a retention pattern that closely mirrored published figures for top personal finance apps, where around 71% of daily active users are lost between day one and day thirty. We had been reading user silence as approval. The retention data showed something different. That experience shaped how we now approach tracking from early in a build, not as an afterthought once the product is live.

A day-one retention rate below 50% should be treated as a warning sign. The goal is to push that number as high as possible and then maintain it through to day thirty and beyond, particularly for any team spending money on paid acquisition. Spending to bring users in while losing them at the curve makes the economics unworkable, and investors know how to spot that.

Activation Rates: Measuring Whether Users Reach the Point That Matters

Activation is the moment a new user first experiences the core value of a product. For a recipe app it might be saving a first recipe. For a fitness tracker it might be completing a first workout log. The specific moment varies by product, but the principle is consistent: there is a threshold that, once crossed, dramatically changes the likelihood that a user will return.

Activation is the moment a user first feels the product is worth coming back to.

Amplitude's 2025 Product Benchmark Report, covering over 2,600 companies, found that 69% of products with strong early activation were also strong three-month retention performers. That correlation is the reason investors ask about activation rates directly. A high activation rate is a leading indicator of the retention curve holding up.

The practical implication for product teams is that activation needs to be defined before it can be measured. Apps routinely track page views and session starts without ever instrumenting the specific action that signals a user has reached value. That is a measurement gap that tends to surface awkwardly in an investor conversation.

Define your activation event before you build. It should be the single action that most strongly predicts whether a user returns within seven days. Then instrument for it from day one so you have real data, not estimates, when someone asks.

Session Depth: What Engagement Actually Looks Like

Session depth refers to how far into a product a user travels within a single session: how many screens they visit, how many actions they take, how long they spend in different parts of the experience. It gives a more textured picture of engagement than session length alone.

Session length is easy to misread. A long session is not automatically a sign of value. A user who is confused, lost, or stuck will also produce a long session. A user held in the product by gamification mechanics that have nothing to do with core value will produce a long session. The question Simon Lee consistently raises is whether session length is high because users are genuinely resonating with the product, or because it is confusing them or retaining them through designed compulsion. Those look identical in the raw number.

Session depth adds texture to that question. A user moving fluidly through multiple features and completing distinct tasks is behaving differently from a user circling the same two screens repeatedly. Behavioural patterns like dwell time, speed of movement, and task completion sequences are indicators of underlying emotional states and of whether a user is finding their way or losing it.

Track where users stop, not just where they go. A screen that consistently ends sessions is more useful diagnostic information than an average session length figure, because it points to a specific design problem rather than a general one.

Daily and Monthly Active Users: The Ratio That Reveals Real Health

Daily active users and monthly active users are individually among the most commonly cited metrics in an investor deck. Separately, they are close to what Simon Lee describes as vanity metrics: they tell you the size of your audience, but not much about how that audience is behaving.

The ratio between them is different. Dividing DAU by MAU gives you a stickiness score, sometimes called the DAU/MAU ratio, that describes how often your monthly users are actually returning within a given month. A product with 100,000 monthly active users but only 5,000 daily active users has a ratio of 5%. A product with the same monthly figure but 40,000 daily active users has a ratio of 40%. These are very different products, and the ratio surfaces that in a way neither figure does alone.

• A DAU/MAU ratio above 20% is generally considered a sign of meaningful daily habit formation.
• Social and messaging products tend to sit above 50%, which reflects their daily utility.
• Utility apps and tools often sit lower, which is expected if weekly use is the natural cadence.

The ratio needs to be interpreted against the intended use pattern of the product. An app designed for weekly check-ins should not be compared against a messaging tool. But within its category, the DAU/MAU ratio gives investors a quick read on whether users are finding the product genuinely useful at the frequency the team claims.

Churn Rate and Silent Abandonment

Churn rate measures the percentage of users who stop using a product within a given period. For mobile apps, this tends to be measured at day one, day seven, day thirty, and day ninety. Around 71% of app users churn within three months of downloading an app, according to MoEngage. That figure makes early retention the defining challenge for almost every consumer app.

What makes mobile churn particularly difficult to manage is that it is mostly silent. Around 25% of apps are used only once and then never opened again. Those users do not submit a complaint, raise a support ticket, or explain why they left. They simply close the app and do not return. The absence of negative feedback is not a signal that everything is fine. As Simon Lee puts it, the opposite tends to be true in mobile: no news is not good news.

Between funding rounds on one project we worked on, we made the decision to implement much better tracking of user retention and to proactively ask users how things were going rather than waiting for them to volunteer that information. The retention data we gathered contradicted the assumption that silence meant satisfaction. Getting ahead of that was the point: relying on users to raise problems before you look for them is a way of finding out too late.

Set up automated prompts that ask users for feedback at specific points in their journey, at day three, day seven, and day thirty. Most users who are about to churn will not tell you unprompted, but a well-timed question catches a portion of them before they leave.

The Design and Emotional Factors Behind Drop-Off Data

Drop-off data from analytics shows you where users leave. It does not tell you why. Understanding the why requires connecting the behavioural data to the design decisions that shaped the experience at those points.

Abandonment in the first few seconds is typically driven by technical performance: slow loading, crashes, sluggish interactions. Within the first sixty to one hundred and twenty seconds, the causes shift to onboarding friction: forced registration before a user has seen any value, too many screens, invasive permissions requested without context, no clear demonstration of what the product actually does. These are design decisions, and they produce measurable drop-off at predictable points in the funnel.

Design-related abandonment is a larger problem than many product teams expect. The research supports the observation that poor design and poor emotional connection account for a very significant share of user drop-off, sitting not far below technical failures as a cause. A product that loads quickly but feels cold, confusing, or misaligned with what the user expected will still lose people at scale.

Dwell time data, feedback at specific screens, and patterns in how users share or recommend the product all contribute to understanding the emotional experience behind the numbers. Behavioural analytics and sentiment tracking together give a more complete picture than either provides alone, because the metric tells you what happened and the qualitative signal tells you how it felt.

Why These Metrics Require Instrumentation Decisions Before the Build

The metrics that investors ask about cannot all be measured after the fact. Some of them require instrumentation decisions that need to be made during the build, not retrofitted once the product is live.

Activation rate, for example, requires a defined activation event and tracking code placed at that specific moment in the user journey. If the event was never defined and never instrumented, there is no data to report. Session depth requires event tracking at multiple points within the experience, not just session start and session end. Behavioural signals like dwell time on specific screens require analytics configured to capture that granularity.

1. Define your activation event before development starts and instrument it from the first build.
2. Set up cohort tracking from day one so day-seven and day-thirty retention figures have real data behind them, not projections.
3. Configure event tracking for the specific actions that matter, rather than relying on default analytics that capture sessions and page views only.
4. Build in a feedback mechanism at key drop-off points so qualitative signal accompanies the quantitative data.

Teams that arrive at an investor conversation with six months of properly instrumented cohort data are in a fundamentally different position from teams that have download numbers and session averages, and that difference begins with a sound app planning and strategy process made before a line of code is written. The difference is almost entirely a product of decisions made during the build, not after it.

What Investors Are Actually Looking For

Investors are looking for evidence that a product has found a group of users who genuinely need it and return to it at a predictable rate. The metrics above are the instruments for demonstrating that.

The most compelling investor conversation is one where a team can show a retention curve that flattens, a defined activation event with a high completion rate, a DAU/MAU ratio consistent with the intended use pattern, and a churn rate with a clear explanation of what is driving it and what is being done about it. Those four things together describe a product that understands itself.

What investors are less interested in is a large number with no behavioural story behind it. Downloads without retention data, session length without session depth, monthly active users without a DAU/MAU ratio: each of these is a partial answer to a question the investor is about to ask in full.

Conclusion

The metrics that investors care about are the metrics that reveal whether a product is genuinely working for its users. Retention curves, activation rates, session depth, churn rate, and the DAU/MAU ratio together describe whether people are finding real value, coming back at a meaningful frequency, and staying long enough to justify the cost of acquiring them.

Downloads are not irrelevant, but they sit at the beginning of the story rather than the middle of it. The teams that come into investor conversations with a clear account of what happens after the install are the ones who have thought about their product the way an investor needs to think about it: as a system that must earn continued use, not just an initial one.

Getting there requires decisions made early: defining activation events before development starts, instrumenting for the right behavioural signals from the first build, and tracking retention in cohorts from the moment real users arrive. None of that is complicated. It is mostly a matter of deciding that those numbers matter before the product is live rather than after.

If you are building a product and want to think through how your metrics architecture maps to what investors will ask, let's talk about your product strategy.

Frequently Asked Questions