Engagement metrics for mobile apps: a decision guide

Useful engagement metrics for mobile apps show whether people reach value and return for it. Start with a completed action, a clear time window, and a named group of users. App opens alone cannot tell you whether the product helped.

Define active before counting users

Choose an event that represents useful progress. A learning app might count a completed lesson. A budgeting app might count a reviewed spending plan. These are examples, not universal definitions.

Keep app opens as a separate reach measure. Name your value-based measure explicitly, such as weekly lesson completers. Otherwise, two teams can report different active-user totals using the same label.

Match the window to the job. A weekly planning app does not need daily use to deliver its promise. Record the event, eligible users, window, and exclusions before comparing releases.

Six metrics and the decisions they support

1. First-value completion

Formula: New eligible users who complete the chosen action within seven days, divided by all new eligible users.

Use only users whose full seven-day window has ended. A fall points you toward the path from entry to first value. Break it down by entry source and app version before changing onboarding.

2. Meaningful weekly active users

Formula: Count distinct users who complete the chosen action during a fixed seven-day period.

Compare this with weekly app openers. If opens grow but useful actions stay flat, inspect task completion and audience fit. More traffic can hide a weaker experience.

3. Return after first value

Formula: Activated users who repeat the action in a defined later window, divided by the original activated group.

State the windows precisely. For example, activate during days 0–6 after signup and repeat during days 7–13. This tests whether the first useful experience leads to another. It differs from retention across all new users.

4. Active days per user

Formula: Count each user's distinct days with the useful action during a week. Report the median among that week's active users.

This distinguishes broad, occasional use from frequent use. Keep the active-user count beside it: frequency can rise when occasional users disappear. Do not treat higher frequency as better for every product.

5. Feature adoption

Formula: Eligible users who use a feature during the window, divided by eligible users who saw its entry point.

This exposure-based definition helps assess discovery and relevance. Also report how many eligible users saw the entry point. A high adoption rate among a tiny exposed group can hide poor reach.

6. Task success

Formula: Valid task attempts that reach a successful outcome, divided by all valid task attempts.

Use one attempt identifier so retries do not inflate success. Pair completion with errors and time spent. Longer sessions can mean interest, but they can also mean someone is stuck.

Worked example: two honest return rates

Imagine 100 new users of a weekly planning app. Every user has completed a 14-day observation period. These numbers are illustrative, not client results.

• 60 users save a first plan during days 0–6 after signup.

• 24 of those 60 save another plan during days 7–13.

• No other users save a plan during days 7–13 in this example.

First-value completion is 60 ÷ 100 = 60%. Return among activated users is 24 ÷ 60 = 40%. Return across the full signup group is 24 ÷ 100 = 24%.

Both return rates are correct. They answer different questions. Label the denominator before claiming improvement. A change that attracts fewer suitable users can lower overall return while activated-user return stays steady.

Check the measurement before changing the product

Exclude staff, marked tests, and duplicate events. Keep user identity consistent across devices. Check that failed actions cannot fire the success event. Compare groups with equal observation time and similar acquisition sources.

For each metric, save a short definition: useful action, eligible group, denominator, window, exclusions, and next decision. If you cannot name a decision, reconsider whether the metric belongs in your weekly review.

DAU divided by MAU can describe use frequency, but its meaning depends on your active event and product cadence. Avoid borrowing a universal target.

For wider metric definitions, see Braze's mobile app metrics guide and Sendbird's engagement metrics overview.

Turn the numbers into a diagnosis

Choose one weak step, inspect its user journey, and test a specific cause. For help assessing your app's retention signals, explore Growth Diagnosis.

Discuss your app's engagement signals