· 8 min read

DAU/MAU Ratio Benchmark: Above 20% Is Good

A good DAU/MAU ratio for a consumer app is above 20%, and the top tenth pass 31%. Benchmarks with sources, what they hide, and how to raise yours in India.

DAU/MAU ratio benchmark: above 20% is good for a consumer app, 31% puts you in the top tenth, and the right target depends on how often people need your app.

Updated October 2026.

A DAU/MAU ratio above 20% is good for a consumer app. At 20%, someone who uses your app in a month comes back on roughly six of its days, and in the largest public dataset I could verify, 20.1% is the line for the top quarter of apps, with the median at 14.1%. Above 31% puts you in the top tenth. Whether your app should aim that high depends on how often people naturally need it, so compare yourself with apps used as often as yours, not with a messaging app.

I'm Raviraj Ramavarapu, founder of Compound Lab, a retention agency for D2C brands and consumer apps. When I ran CleverTap day to day, daily active users was the first number I opened every morning, before funnels or campaigns. These days I sit with app founders who are trying to work out whether their own ratio is a problem. This is how I'd read it.

What is the DAU/MAU ratio?

DAU/MAU compares the people using your app on a typical day with everyone who used it in the last 30 days, as a percentage. It tells you how many days a month your typical user comes back, which is why it's often called stickiness.

The maths is simple. If 20,000 people use your app on an average day and 1,00,000 used it at least once in the last 30 days, your ratio is 20%. Multiply the ratio by 30 and you get a rough count of active days per monthly user, here about six.

DAU/MAU Rough active days per month What it usually means
10% 3 People use you for a task, then leave
20% 6 A regular, more than weekly habit
33% 10 Part of most people's week
50% 15 Every other day, close to a daily habit

Google Analytics 4 calculates this for you. Its user stickiness metrics are named DAU / MAU, DAU / WAU and WAU / MAU, using active users over the last 24 hours, 7 days and 30 days. Check what counts as active before you trust the number. GA4 counts a user as active after an engaged session, which can be just 10 seconds in the app, so a quick open to clear a notification counts the same as a real visit.

What DAU/MAU means in active days per month. At 10% a typical monthly user returns on about 3 days, at 20% about 6 days, at 33% about 10 days and at 50% about 15 days. Benchmarks marked on the scale: median app 14.1%, top quarter 20.1%, top tenth 31%.

What is a good DAU/MAU ratio?

Above 20% is good, above 31% is excellent, and anything near 50% belongs to apps people use almost daily. Those lines come from the few public sources that state their sample.

Source What it measured DAU/MAU
MWM stickiness data, April 2026 Median US iOS app 14.1%
Top 25% of apps 20.1%
Top 10% of apps 31.0%
Top 1% of apps 57.7%
Meta Q4 2023 results Facebook, December 2023: 2.11 billion daily users of 3.07 billion monthly About 69%, my calculation

Two warnings about this table. The MWM figures cover US iPhone apps, not Indian Android apps. And Facebook is the ceiling, not a target. It's one of the most habitual products ever built, and Meta stopped reporting DAU and MAU from 2024, moving to a family-wide daily count instead.

You'll see other numbers quoted. Mixpanel publishes stickiness for Asia-Pacific in 2025, including 23% for ecommerce and 34% for payments. I've kept them out of the table on purpose. Mixpanel's public pages don't say how stickiness is calculated, and the ecommerce post's own figures, 18.0 million daily and 79.9 million weekly users, divide to the same 23%. That looks like daily over weekly users, not monthly. A DAU/WAU number will always look higher than DAU/MAU, so comparing your ratio with it makes you look worse than you are.

Is there a DAU/MAU benchmark for India?

Not a public one I could verify. Indian listed apps report monthly figures rather than a daily-to-monthly ratio, and usually count transactions, not opens. Paytm reports 8 crore monthly transacting users for the quarter to June 2026. Swiggy reports 19.8 million monthly transacting users for food delivery. Neither gives a daily number.

What the Indian data does show is how hard the fight for a daily slot is. Sensor Tower's State of Mobile India 2026 puts time spent in apps in India at 1.23 trillion hours in 2025, up 9% in a year. People here aren't using their phones less. They're giving that time to a few apps they open without thinking, and your ratio measures whether yours is one of them.

So for an Indian app, I use the global tiers as a ceiling check and my own weekly cohorts as the real benchmark. If each new cohort's ratio is higher than the one before, the app is getting stickier, whatever the global median says.

What DAU/MAU should your app aim for?

Aim for the ratio that matches how often people need your app, and measure with the window that fits it. Amplitude's advice is to set your product usage interval first, meaning how often you expect people to naturally come back, and judge engagement against that.

How often people need it Examples Measure with What good looks like
Every day Health tracking, messaging, news, games DAU/MAU Top-quarter territory, above 20%
A few times a week Learning, fitness classes, family planning DAU/MAU and WAU/MAU Steady weekly return, not daily
About weekly Grocery, shopping, food ordering WAU/MAU Most monthly users active in most weeks
A few times a month or less Bills, travel, insurance Monthly retention by cohort Coming back for the next real need

A shopping app at 12% DAU/MAU might be healthy. A habit app at 12% has a problem. At Healthify, the core habit was logging food and water every day, so the daily ratio was the right lens. For a travel app, chasing a daily ratio leads to pointless notifications.

One mix-up to avoid. On a recent founder call, we wrote the goal as active users as a share of installs, from under 10% towards 15%. That's a useful number, but it isn't DAU/MAU. Installs include everyone who ever downloaded the app, including people long gone, while MAU only counts the last 30 days. Keep both, label them clearly, and never compare one with a benchmark for the other.

When does the DAU/MAU ratio mislead you?

When the ratio rises for the wrong reason, or when your app isn't meant to be used daily. The three cases I'd check before celebrating a jump:

  1. Occasional users have left. If people who opened the app twice a month churn, MAU falls and the ratio rises, even though no one used the app more. Always read the ratio next to raw DAU and MAU.
  2. Notifications are inflating opens. Andrew Chen points out in his critique of the metric that notifications tend to grow MAU faster than DAU. A push that brings someone in for 10 seconds also counts as an active day, so measure visits that reach the core action, not app opens.
  3. The product is episodic. The same post notes that apps like Uber and Airbnb look weak on DAU/MAU while being great businesses. If your users only need you a few times a month, a low ratio is expected.

A better view sits behind the ratio. The power user curve, from Li Jin and Andrew Chen at a16z, is a histogram of how many days each user was active in the month. A healthy app shows a bump of people active on most days. A ratio of 20% can hide either a solid group of daily users or a crowd of people who came once, and the curve tells you which.

How do you increase your DAU/MAU ratio?

Give people a reason to come back on the days they'd naturally use the app, then remove what stops them. More notifications rarely move it for long.

  1. Fix the first session. Users who never reach your core action won't build a habit around it. Guide every new user to that action first, as I set out in my guide to app retention in India.
  2. Attach the app to a moment people already have. A morning glass of water, the evening commute, the weekly grocery list. At Healthify the water reminder worked because it fitted a habit people were already trying to keep.
  3. Ask for notification permission when it helps. A reminder only works if people allowed it. Ask at the moment it solves something, covered in when to ask for push notification permission.
  4. Trigger on what didn't happen. A missed log, an unfinished lesson, a task left open. These messages need waits and exits, which is where a CRM starts to earn its fee. I cover the switch in Firebase or a CRM for your app.
  5. Cap frequency and prove the lift. One useful message a day beats three. Keep a holdout group out of each journey, so you know whether the extra active days came from your messages or would have happened anyway.

For message ideas by moment, my push notification examples cover the first week and lapsed users.

How should you track DAU/MAU each week?

Track it by weekly install cohort, on an active definition that means something, alongside the numbers that explain it.

Measure Why it matters
DAU/MAU, active means the core action The real habit, without empty opens
Raw DAU and MAU Shows whether a rising ratio is churn in disguise
DAU/MAU by weekly install cohort Tells you if each new group is stickier than the last
Days active per user in the month The power user curve, to see where users bunch up
WAU/MAU for weekly products The fairer test for apps people don't need daily

The cohort view matters most. A blended ratio mixes loyal users from last year with this week's installs, so a bad new cohort can hide behind old ones. I explain how to read a cohort grid in cohort analysis.

Where I fit

Compound Lab works with D2C brands and consumer apps on everything after the install, from the first session and permissions to journeys, renewals and win-back. If your monthly users are growing but your daily users aren't, book a 30-minute call and we'll look at what your active users actually do and where the habit breaks.

Next postUse One WhatsApp Number for Marketing and Support

Your customers already paid once. Make them pay again.

Book a Consultation