Consumer App Unit Economics: 15 Metrics Every App Startup Must Track (2026)

Consumer App: 15 Metrics Every App Startup Must Track
Unit Economics
AS
Ankit Sarawagi · Founder, CFOmatrix · June 17, 2026 · 13 min read · Updated June 2026

Consumer apps and gaming products live and die on engagement loops. Unlike SaaS, there is no subscription contract locking a user in. Every day a user chooses to open your app or not is a vote on whether your product is worth their time. Unit economics for consumer apps are built around that reality: measuring how deeply users engage, how many stay after install, how many convert to paying, and what it costs to acquire users who actually stick. This guide covers the 15 metrics that define a healthy consumer app business, from first-day retention to virality to ROAS, with formulas and Indian market benchmarks for each one.

Key Takeaways

  • D1 Retention is the single most predictive signal for long-term app health; fix onboarding before scaling acquisition
  • DAU/MAU above 20% indicates a healthy engagement habit; above 40% is exceptional for most app categories
  • Freemium apps typically convert 2 to 5% of users to paying; monetization depends on a large retained user base
  • K-factor above 1.0 creates self-sustaining growth where the app acquires more than one new user per existing user
  • ROAS of 150%+ within 180 days is the minimum threshold for a paid user acquisition channel to be viable
  • LTV for ad-monetized apps is directly tied to D30 retention; retaining users longer compounds ad revenue per install
D1 Retention
The single most predictive metric for long-term app health. If users do not return on Day 1, they almost never return.
2-5%
Conversion to paid rate for freemium apps. Monetization depends on a large user base with a small percentage paying.
K > 1.0
The viral growth threshold where the app acquires more than one new user per existing user, creating self-sustaining growth.

Why Consumer App Unit Economics Are Different

In a SaaS or subscription business, revenue is contractual. A user who signed up is expected to pay until they cancel. In consumer apps, especially freemium ones, the majority of users never pay anything. Revenue depends entirely on whether you can build an engagement loop strong enough that users keep coming back, and whether a small subset of those retained users can be converted to payers.

This creates a fundamentally different economic structure. Your cost base grows with installs. Your revenue grows only with retained and paying users. The gap between those two curves is where most consumer app businesses fail. An app that acquires 100,000 users a month but retains only 5% by Day 30 is essentially rebuilding its entire user base every month, at full acquisition cost, just to stand still.

The other critical difference is the role of virality. In SaaS, growth is mostly driven by sales and marketing. In consumer apps, the best businesses grow partly through the users they already have. K-factor, referral mechanics, and social sharing loops are not just nice features. For a capital-efficient consumer app, they are the difference between a sustainable business and an expensive user acquisition treadmill.

CFO Lens: The right order of operations for a consumer app is: fix retention first, then fix monetization, then scale acquisition. Pouring paid spend into an app with broken D1 retention is one of the most common and expensive mistakes in the Indian consumer app market.

Engagement Metrics

Engagement metrics tell you the depth and frequency of how users interact with your app. They are the foundation for predicting retention, monetization potential, and long-term LTV before those numbers fully mature in your cohort data.

DAU/MAU Ratio

The DAU/MAU ratio measures the proportion of your monthly active users who use the app on any given day. It is the clearest proxy for habit formation. A high DAU/MAU ratio means users have built the app into their daily routine. A low ratio means users open the app occasionally but have not made it a habit, which makes them far easier to churn.

DAU/MAU Ratio = Daily Active Users / Monthly Active Users x 100
Benchmark: 20%+ is good for most consumer apps. 40%+ is excellent and indicates strong daily habit formation. Context matters: a daily fantasy sports app or chat app should target 40%+, while a travel or occasion-based utility app with 10 to 15% DAU/MAU may still be healthy given its use case.
Common Mistake: Comparing your DAU/MAU against apps in completely different use-case categories. A bill payment app used twice a month by design is not comparable to a gaming app meant for daily sessions. Always benchmark against products with the same intended usage frequency.

Session Length

Session length is the average time a user spends in the app per session. It is a direct measure of engagement depth: are users doing something meaningful once they open the app, or are they bouncing out within seconds? For ad-monetized apps, session length is directly tied to impressions and revenue. For gaming apps, longer sessions often correlate with higher in-app purchase probability.

Session Length = Total Time Spent in App / Total Number of Sessions
Benchmark: Gaming apps typically target 8 to 15 minutes per session. Social and content apps vary from 5 to 20 minutes depending on feed depth. Utility apps may have short but high-intent sessions of 1 to 3 minutes, which is still healthy if task completion rates are high.
Common Mistake: Optimizing session length in isolation without tracking task completion or in-session actions. A user who spends 20 minutes in the app but never completes a core action is not necessarily engaged. Long session length can also indicate confusion or a poor UX if users are spending time searching for features rather than using them.

Sessions per DAU

Sessions per DAU measures how many times each daily active user opens the app within a single day. Multiple sessions per day are the hallmark of habitual use. A user who opens a gaming app four times a day has built a genuine habit loop. A user who opens it once is more casual and at higher risk of churning when a competing app grabs their attention.

Sessions per DAU = Total Sessions in a Day / Daily Active Users
Benchmark: 2+ sessions per DAU is a strong signal for gaming and social apps. For utility apps, even 1.2 to 1.5 sessions per DAU can be acceptable if each session has high intent. A falling sessions-per-DAU trend over time is an early warning signal that user engagement is weakening before it shows up in your retention curves.
Common Mistake: Counting background app refreshes or push-notification opens as sessions. If your analytics tracks a session start every time the app comes to foreground, you may be inflating sessions-per-DAU with ghost interactions. Define a session as a meaningful user-initiated engagement of at least 30 seconds.

Retention Metrics

Retention is the most critical section of consumer app unit economics. It is where the business model is won or lost. No level of paid acquisition, no viral loop, and no monetization strategy can compensate for a product that does not bring users back. Every other metric in this guide is downstream of retention.

D1 Retention Rate

D1 Retention measures the percentage of users who return to the app on Day 1 after their install. It is the single most important early signal of whether your onboarding experience is delivering perceived value fast enough. If a user does not come back the day after installing, the probability they ever return drops sharply. D1 is a measure of first impression and the speed of your value delivery.

D1 Retention Rate = Users Who Returned on Day 1 / Total Users Who Installed on Day 0 x 100
Benchmark: 25 to 40% is considered good for Indian consumer apps. Gaming apps with strong first-session reward loops can reach 35 to 45%. Below 20% is a signal that the onboarding flow is not working and should be prioritized before any additional spend on user acquisition.
Common Mistake: Scaling paid user acquisition before diagnosing low D1 retention. If your D1 is 15%, every rupee of UA spend is building on a broken foundation. Each cohort largely disappears in 24 hours, making it structurally impossible to build a retained user base regardless of how much you spend.

D7 Retention Rate

D7 Retention measures the percentage of users from a Day 0 install cohort who return on exactly Day 7. It is the most widely tracked retention milestone in the industry because it captures whether users made it through the first week. Users who reach Day 7 have typically formed some attachment to the product. D7 is a stronger signal of medium-term retention than D1, and a much better predictor of monetization probability.

D7 Retention Rate = Users from Day 0 Cohort Who Returned on Day 7 / Total Day 0 Cohort Size x 100
Benchmark: 10 to 20% is the typical range for consumer apps. Gaming apps can target 15 to 25%. Below 10% at Day 7 means the engagement loop is not strong enough to pull users back across the natural drop-off points in the first week, such as Days 2 to 4 when novelty fades.
Common Mistake: Measuring D7 retention as any user who opened the app within 7 days rather than exactly on Day 7. Classic retention is cohort-based and point-in-time. Measuring it on a rolling window will always look better but does not tell you whether your D7 loop is actually working.

D30 Retention Rate

D30 Retention is the gold standard for consumer app health. It tells you what fraction of users who installed the app are still active a month later. Users who survive to Day 30 are your most valuable cohort: they have the highest probability of converting to paying users, the highest lifetime ad impressions, and the lowest marginal cost of continued retention. D30 is also the most direct input into your LTV calculation.

D30 Retention Rate = Users from Day 0 Cohort Who Returned on Day 30 / Total Day 0 Cohort Size x 100
Benchmark: 5 to 10% is typical for consumer apps. Gaming apps with strong progression mechanics and daily reward systems can reach 12 to 20%. A D30 above 15% is exceptional and signals a product with genuine long-term engagement loops that competitors will find difficult to replicate.
Common Mistake: Treating D30 as an isolated metric without tracking the full D1, D7, D30 curve together. The shape of the retention curve matters as much as the endpoint. A steep drop between D1 and D7 followed by stabilization tells a different story about your product than a gradual decline that never stabilizes.

Churn Rate

Monthly churn rate measures the percentage of active users in a given month who did not return the following month. For consumer apps, churn is typically measured at the monthly active user level. High monthly churn means the business has a leaky bucket problem: no matter how many new users are acquired, the existing base keeps draining away, compounding the cost of maintaining any meaningful user base.

Monthly Churn Rate = Users Who Did Not Return This Month / Active Users Last Month x 100
Benchmark: Monthly churn below 10% is considered healthy for consumer apps. Below 5% is strong. Monthly churn above 20% means the app is losing a fifth of its active user base every month, which at a typical acquisition cost makes sustainable growth extremely expensive without a strong viral loop to offset it.
Common Mistake: Not separating churn by user cohort and acquisition channel. Users acquired through incentivized install campaigns often churn at 60 to 80% within 30 days. Blending these with organically acquired users masks the true retention quality of your core audience and leads to incorrect LTV calculations.

Revenue Metrics

Consumer apps typically monetize through three mechanisms: in-app purchases (IAP), subscriptions, and advertising. Most apps use a combination, and the revenue metrics differ slightly depending on the primary model. The four metrics below apply across all monetization types and are the core of any consumer app financial model.

ARPU — Average Revenue Per User

ARPU is the total revenue generated in a period divided by the total monthly active users in that period. It is a blended metric that averages paying and non-paying users together. For freemium apps where 95 to 98% of users pay nothing, ARPU is naturally a small number, but it is the right number to use when calculating LTV and comparing against user acquisition cost.

ARPU = Total Revenue in Period / Total Monthly Active Users in Period
CFO Tip: Track ARPU separately for each monetization stream: IAP-ARPU, subscription-ARPU, and ad-ARPU. Blending them makes it harder to understand which revenue lever is working and which is not. For ad-monetized apps, also track ARPU by country since ad eCPMs in India are significantly lower than in Tier 1 markets.
Common Mistake: Calculating ARPU using total registered users instead of monthly active users. Dividing revenue by a large base of inactive or dormant users makes your ARPU look artificially low. ARPU should always be calculated against active users in the same period.

ARPPU — Average Revenue Per Paying User

ARPPU focuses only on the users who actually made a purchase or paid for a subscription in a given period. It strips away the non-paying majority and reveals the true monetization strength of your paying segment. For gaming apps with in-app purchases, ARPPU reflects how much your payers are willing to spend per month, which is a direct input into whale strategy and IAP pricing decisions.

ARPPU = Total Revenue in Period / Number of Paying Users in Period
CFO Tip: In a typical Indian gaming app, the top 5% of paying users (whales) often account for 50 to 60% of IAP revenue. Track ARPPU segmented by payer tier: dolphins (occasional small spenders), regular payers, and whales. Each segment needs a different retention and upsell strategy.
Common Mistake: Focusing solely on ARPPU while ignoring what percentage of users pay. An ARPPU of Rs. 500 is meaningless if only 0.1% of users pay. The combination of ARPPU and conversion to paid rate together tells you the health of your monetization engine, not either metric in isolation.

Conversion to Paid Rate

Conversion to paid rate is the percentage of your active user base that makes at least one purchase or starts a paid subscription in a given period. It is the bridge between your engagement metrics and your revenue metrics. Even a modest improvement in conversion rate, from 2% to 3%, represents a 50% increase in paying users without acquiring a single new install.

Conversion to Paid Rate = Paying Users / Total Active Users x 100
Benchmark: 2 to 5% is typical for freemium consumer apps. Gaming apps with strong IAP loops and limited free content can reach 5 to 10%. Apps behind a hard paywall, where users see the payment screen before accessing core features, should target 20% or higher since the conversion decision is made at the point of highest intent.
Common Mistake: Measuring conversion to paid against total registered users rather than monthly active users. A user who installed six months ago and never returned is not a conversion opportunity. Measure conversion against active users who have had a genuine opportunity to be exposed to your monetization triggers in the current period.

LTV — Customer Lifetime Value

LTV for a consumer app is the total revenue you can expect from an average user over their entire lifetime with the app. The simplest version uses ARPU and churn rate. For more accurate modelling, cohort-based LTV tracks actual revenue generated by a cohort of users over their observed lifetime, which accounts for the natural shape of how app revenue declines over time after install.

LTV (Simple) = ARPU / Monthly Churn Rate
CFO Tip: For ad-monetized apps, LTV has a direct relationship with D30 retention. Every percentage point improvement in D30 retention means users stay in the monetizable base longer, compounding ad impressions and IAP exposure. Model LTV at D30, D60, and D90 cohort levels to understand where the revenue curve flattens.
Common Mistake: Using a 12-month or 24-month LTV projection for a consumer app where most users churn within 60 to 90 days. Projecting LTV based on unrealistically long retention curves will make your LTV:UA Cost ratio look attractive on paper while masking the reality that most users are not being retained long enough to generate that revenue.

Acquisition Metrics

Acquisition metrics tell you whether the cost of bringing in new users is justified by the revenue they generate. For consumer apps, this is more complex than SaaS because the majority of users do not pay, the ones who do pay are a subset of a subset, and organic and viral channels can dramatically change the blended cost of an install.

UA Cost — User Acquisition Cost

User Acquisition Cost (UA Cost) is the total paid media spend divided by the number of installs generated. It is the consumer app equivalent of CAC in SaaS. Unlike SaaS where you acquire a paying customer, in a freemium app you are acquiring an install, most of which will not convert to revenue. UA Cost must always be evaluated against LTV: a Rs. 40 install is cheap if the user LTV is Rs. 200, and expensive if the LTV is Rs. 30.

UA Cost = Total Paid UA Spend / Number of Installs from Paid Channels
Benchmark: India-market UA costs vary by category. Casual gaming: Rs. 20 to 50 per install. Mid-core gaming: Rs. 40 to 100 per install. Utility and fintech apps: Rs. 80 to 200 per install. Social and content apps: Rs. 30 to 80 per install. These ranges shift significantly by channel and audience targeting.
Common Mistake: Optimizing UA campaigns for lowest cost per install without tracking quality metrics like D1 retention, conversion to paid, or Day 7 session count by cohort. The cheapest installs are often from the lowest-quality user segments, producing short-lived engagement that destroys LTV while making the acquisition dashboard look good.

ROAS — Return on Ad Spend

ROAS measures how much revenue is generated for every rupee spent on a paid user acquisition channel. For consumer apps with a mix of monetization streams, ROAS is calculated by measuring the cumulative revenue from a paid cohort over a defined time window (typically 30, 90, or 180 days) against the spend that acquired them. A ROAS of 150% at 180 days means every Rs. 100 spent returned Rs. 150 in revenue over six months.

ROAS = Revenue from Paid Channel Cohort / Paid Channel Spend x 100
Benchmark: A minimum ROAS of 100% at Day 180 means you have broken even. 150%+ at 180 days is a good minimum threshold for a viable paid channel. Strong consumer apps target 200%+ ROAS at 180 days on their best-performing channels. Always track ROAS at multiple time windows: D7, D30, D90, D180 to understand the revenue recovery curve.
Common Mistake: Measuring ROAS only on direct IAP revenue while ignoring ad revenue generated from the same users. For ad-monetized apps, a user who never makes an in-app purchase can still generate significant ad revenue over 90 to 180 days. Attribution of ad revenue to a paid cohort is harder but essential for accurate ROAS calculation.

K-factor / Virality Coefficient

K-factor measures the number of new users each existing user generates through referrals, sharing, or invites. A K-factor of 0.5 means each user brings in half a new user on average. A K-factor above 1.0 means the app generates more than one new user per existing user, creating a self-sustaining viral growth loop where the install base grows without a proportional increase in paid spend. K-factor is the single most powerful lever for reducing blended UA Cost over time.

K-factor = Average Invites Sent per Active User x Invite Conversion Rate
Benchmark: K-factor of 0.1 to 0.3 is typical for most consumer apps. 0.3 to 0.5 is good and meaningfully reduces blended UA cost. Above 0.7 is strong. Above 1.0 indicates genuine viral growth. Most consumer apps never reach K-factor above 1.0; the ones that do typically have social mechanics deeply embedded in the core product loop, not bolted on as an afterthought.
Common Mistake: Counting passive social shares or generic content shares as invite events in the K-factor calculation. K-factor should only track referral actions that have a plausible conversion path to new installs: referral links clicked, invite codes redeemed, or app store installs attributed to a sharing event. Passive shares rarely convert at measurable rates.

Product Quality Metrics

Product quality metrics sit at the intersection of user experience and business economics. They capture signals about whether the product is working well enough to support the retention and monetization numbers above. Two metrics in particular have direct financial consequences that are often underestimated.

Install-to-D1 Retention Rate (Onboarding Quality)

D1 retention is fundamentally a measure of onboarding quality. It answers the question: did the first session deliver enough value that the user wanted to come back tomorrow? Onboarding failure is the most common cause of low D1 retention, and it is almost always a product problem, not a traffic quality problem. Users need to reach what product teams call the “aha moment” within their first session, the moment they understand and feel the core value the app offers.

D1 Retention = Day 1 Returners / Day 0 Installs x 100
CFO Tip: Run A/B tests on onboarding flows before any other experiment. The financial leverage of improving D1 retention from 20% to 30% is larger than almost any monetization improvement because it compounds across every cohort you acquire. Every subsequent retention and revenue metric improves when D1 improves.
Common Mistake: Attributing low D1 retention to traffic quality rather than diagnosing the onboarding flow. While poor-quality install sources do produce lower-retention cohorts, if your D1 retention is below 20% across all channels and audiences, the onboarding experience is the primary culprit and needs to be fixed first.

App Store Rating

Your app store rating on Google Play and the Apple App Store is not just a vanity metric. It is a direct input into organic install volume. Google Play’s ranking algorithm uses rating, review volume, and engagement metrics to determine how prominently your app appears in search and Browse results. A 3.8-star app competes for organic installs at a structural disadvantage against a 4.3-star competitor even if the underlying product is comparable.

App Store Rating = Weighted Average of All Active Star Ratings on the Platform
Benchmark: Target 4.0+ as a floor for meaningful organic visibility. 4.3+ is strong and puts you in the top tier for most categories on Google Play India. Below 3.8, organic install volume suffers measurably and paid UA efficiency also declines because some ad networks factor store rating into quality scores.
Common Mistake: Prompting all users for a rating regardless of their experience, which floods the app with negative reviews from churned users. Build in-app rating prompts that trigger only after a positive in-session event: level completion, successful task, or achievement unlock. This improves your average rating while catching negative feedback privately before it reaches the store.

Benchmarks for Indian Consumer Apps and Gaming

These benchmarks reflect Indian market norms for consumer apps and mobile gaming at different growth stages. Apps targeting global audiences with higher ad eCPMs or premium IAP markets may see different thresholds; these numbers are calibrated for Indian-first products.

MetricEarly StageGrowth StageMature
D1 Retention20%+ minimum25-35% target35-45%+
D7 Retention8%+ minimum12-18% target18-25%+
D30 Retention4%+ minimum6-10% target10-20%+
DAU/MAU Ratio10%+ minimum20-30% target30-45%+
Conversion to Paid1%+ minimum2-4% target4-8%+ (gaming)
Monthly ChurnBelow 25%Below 15%Below 10%
K-factor0.1+0.3-0.5 target0.5-1.0+
ROAS at D180100%+ break-even150%+ target200%+ strong
App Store Rating3.8+ minimum4.0+ target4.3+ strong

“In consumer apps, retention is not a product metric and a business metric. It is the same metric. Every rupee of LTV, every ROAS percentage point, every viral loop depends entirely on how many users come back. Fix the retention curve first and everything else gets easier.”

Ankit Sarawagi, CFOmatrix

Need help building a unit economics model for your consumer app?

CFOmatrix helps app founders set up the right metrics framework and financial model before their investor conversations.

Talk to CFOmatrix

Frequently Asked Questions

What D1 retention rate is considered good for an Indian consumer app?

A D1 retention rate of 25 to 40 percent is considered good for Indian consumer apps. Gaming apps with strong first-session reward loops and immediate feedback mechanics can target the upper end of this range. Below 20% on Day 1 is a signal that the first session is not delivering enough value quickly enough, and the onboarding flow needs to be redesigned as a priority before scaling any user acquisition spend.

How is ARPU different from ARPPU for a freemium app?

ARPU (Average Revenue Per User) is total revenue divided by all monthly active users, including the large majority who pay nothing. ARPPU (Average Revenue Per Paying User) is total revenue divided by only the users who made a purchase. In a typical freemium app where 2 to 5 percent of users pay, ARPPU is 20 to 50 times higher than ARPU. ARPU tells you the overall monetization health of your entire user base and is the right input for LTV calculations. ARPPU tells you how well you are extracting value from the segment that is willing to spend.

What conversion to paid rate should a freemium app target?

A conversion to paid rate of 2 to 5 percent is the typical benchmark for freemium consumer apps. Gaming apps with strong in-app purchase mechanics and limited free progression can reach 5 to 10 percent. Apps behind a hard paywall where users face the payment decision upfront should target 20 percent or higher. If your freemium app is below 1 percent conversion, the issue is usually weak monetization triggers, a poor premium value proposition, or an audience that was never likely to pay for the category.

How do you calculate LTV for a consumer app that earns through ads?

For ad-monetized apps, LTV is calculated as ARPU divided by monthly churn rate, where ARPU includes both ad revenue and any in-app purchase revenue blended across all active users. Example: if your app generates Rs. 8 per monthly active user from ads and the monthly churn rate is 15 percent, the LTV is approximately Rs. 53. For ad-heavy apps, improving D30 retention has a compounding effect on LTV because retaining users longer directly increases the number of ad impressions and sessions you can monetize over the user’s lifetime.

What K-factor indicates viral growth for a consumer app?

A K-factor above 1.0 indicates genuine viral growth, where each existing user generates more than one new user on average, creating a self-sustaining acquisition loop. Most consumer apps have a K-factor between 0.1 and 0.5. A K-factor of 0.3 to 0.5 is considered good and meaningfully reduces your blended user acquisition cost over time. K-factor above 1.0 is rare and typically seen in social-first apps where sharing is deeply embedded in the core product experience rather than added as a growth hack.

Unit Economics Every Startup Must Track: The Complete CFO Guide Edtech Unit Economics: Metrics Every Education Startup Must Track SaaS Unit Economics: 18 Metrics Every Startup Must Track in 2026
AS

Ankit Sarawagi

Founder, CFOmatrix | Finance Strategy & Equity Compliance

CFOmatrix is a knowledge platform focused on how finance actually works inside growing companies. Every insight is shaped by real operating experience across startups and growth-stage companies, including cross-border setups.

What do you think?

Leave a Reply

Your email address will not be published. Required fields are marked *

Insights

More Related Articles

Common Finance-Function Mistakes That Cost Growth-Stage Startups (2026)

Company Policy Templates (India): 41 Free, Editable Downloads

Code of Conduct: What to Include and a Free Template (India)