Guide · 8 min read
Google Play Ranking Algorithm 2026: How DAU/MAU and Retention Now Drive Your Visibility
Google Play now ranks apps on engagement, not just downloads. In 2025, Google added DAU/MAU ratio and User Loss Rate to its Android Vitals ranking signals — the same dashboard that tracks crashes and ANR rates. An 8% DAU/MAU ratio is the published minimum threshold: fall below it and your listing can carry a visible warning and lose eligibility for key discovery surfaces. Install campaigns that drive low-quality downloads now actively hurt your ranking, not just fail to help.
DAU/MAU ratio: 8% is the floor Google published, 20% is the actual target
An 8% DAU/MAU ratio is Google Play's published minimum for full search and browse visibility. If your app falls below it — meaning fewer than 8 in 100 users who have your app installed open it on a typical day — Google may add a warning to your store listing and remove you from certain recommendation and browse surfaces. The threshold is measured over a rolling 28-day window, and Google requires at least 24 days of qualifying data before the metric is assessed.
The 8% floor is a floor, not a goal. A 20% DAU/MAU ratio is what Google describes as "strong engagement," and top apps in habit-forming categories — messaging, habit tracking, weather, language learning — routinely reach 40–60%. A utility used occasionally, like a document scanner or travel itinerary tool, will naturally hover at 10–15%, which still clears the threshold. The number to watch is your trend over the last 90 days, not the absolute value.
One important nuance: Google applies this metric only when your app has enough active users to produce a statistically meaningful reading over the 24-day minimum. Brand-new apps with fewer than a few hundred monthly actives are unlikely to trigger the threshold check in practice — but as soon as your install volume grows to the point where Android Vitals has data to report, DAU/MAU becomes a live ranking input.
User Loss Rate: the metric Google tracks but won't put a number on
User Loss Rate is Google's term for the ratio of uninstalls to active installs — users who removed your app from all of their devices compared to users with it installed on at least one. Google adds it to Android Vitals alongside DAU/MAU ratio, crash rates, and ANR rates. But unlike DAU/MAU, Google has not published a specific failure threshold. Apps with high User Loss Rate see ranking suppression in practice even when their DAU/MAU ratio clears 8%.
The most damaging version is early uninstalls: users who delete your app within the first 72 hours after install. An early uninstall is the clearest quality signal Google can read — it means your listing set an expectation your app failed to meet in the first session. This usually traces back to a feature shown prominently in screenshots that users can't find quickly inside the actual app. A solid onboarding flow that surfaces your core value within the first 60 seconds of use is the most reliable lever for reducing early-uninstall rate.
User Loss Rate is also category-sensitive. An app in a competitive category where users install several similar tools and delete the weakest performs worse than an app in a niche category where there's less comparison shopping. This doesn't mean targeting less competitive categories is always the right move — but it does mean that category placement and keyword targeting affect not just your install quality but your downstream retention signal.
Why high-volume install campaigns now carry real ranking downside
Install velocity still contributes to keyword ranking — particularly for new apps establishing relevance in a search cluster. But its relative weight has dropped, and its capacity to actively harm your ranking has increased. The mechanism is straightforward: an install from a low-intent user who never opens the app drags on your DAU/MAU ratio. An install from a user who uninstalls within three days is a double hit — it lowers DAU/MAU and raises User Loss Rate simultaneously.
Incentivized install campaigns and broad reward-network placements are the highest-risk type under the new ranking model. These campaigns optimize for install volume, not user intent, and the install cohorts they produce typically show 70–90% uninstall rates within the first week. Under the older install-weighted algorithm, a burst of volume could create lasting keyword rank improvements that offset the low-quality cohort. Under the engagement-weighted algorithm, the burst provides a short ranking lift followed by sustained drag from the retention quality signal.
The same logic applies to over-broad keyword targeting. Ranking for a high-volume search term that brings in users looking for something your app isn't produces installs from users who churn immediately. Narrowing keyword scope to attract fewer but higher-intent installs is now an explicit ranking strategy, not just a conversion optimization. A related culprit is category misfiling: if your App Store category selection targets a bucket that attracts users expecting a different kind of tool, the downstream retention damage registers as a ranking penalty before you notice it in installs.
What actually moves DAU/MAU: the four product levers that matter
DAU/MAU is a product metric before it's an ASO metric. The underlying variable is whether your app gives users a reason to open it every day — and most apps don't, by design or accident. Apps that naturally sustain 20%+ DAU/MAU share one structural property: their core value compounds with daily use. Language learning, habit tracking, news reading, and messaging all become more useful — or more costly to skip — the more consistently users engage. Apps without a daily value proposition plateau at 5–10% and require active engagement mechanics to push higher.
The four fastest levers for an app currently below 15% DAU/MAU: Home screen widgets that let users take an action or read key data without opening the full app — Android counts a widget interaction as an active session for DAU purposes. Contextual push notifications triggered by user behavior rather than a time-of-day timer — notifications sent after a user has completed a core action on at least two separate days see double the open rates of day-1 onboarding pushes. A day-2 hook designed into the first session — ending session one with something meaningful left incomplete pulls users back at the highest rate. Streak mechanics for apps where consistent daily use has intrinsic value, since they raise the psychological cost of breaking a streak.
One thing these levers share: they work on users who already found value in the app. If users open the app once and see no reason to return, adding push notifications to the problem produces only dismissals and opt-outs. Fix the first-session value clarity first, then layer engagement mechanics on top of an already-engaged cohort.
Finding your data: where DAU/MAU and User Loss Rate live in Play Console
DAU/MAU ratio and User Loss Rate appear in Android Vitals → Core Value. The Core Value dashboard shows each metric with threshold bands — green, yellow, and red zones — the same visual treatment Google uses for crash rates and ANR rates. If you're in the yellow band, a warning is approaching; if you're in red, a warning may already be visible on your listing. Check this dashboard before any major keyword change or creative update, since the metrics lag real-world behavior by roughly 30 days.
The retention curve — a different but related view — lives in Users & Events → Retention. It shows what percentage of an install cohort is still active at day 1, day 7, day 14, and day 30. Day-30 retention above 10% is the marker where Play Store ranking tends to stay stable under normal conditions. Below 5%, suppression effects become visible over a 60-day lag — meaning you'll see ranking drops roughly two months after the retention problem emerged, not immediately. Monitoring the retention curve on every release is more useful than reacting to ranking drops after they appear.
New in 2026: Play Console surfaces a composite "user engagement score" on the app dashboard home, combining DAU/MAU, retention curve slope, and crash-free sessions. Google now includes this score in developer digest emails — if yours has declined between two digest emails, the ranking effect is usually 4–6 weeks behind. Acting on the email immediately gives you a buffer before visibility drops. For broader context on how Google is restructuring Play Store quality signals in 2026, including the parallel billing and distribution changes, see the Google Play billing flexibility guide.
ASO-side adjustments when your listing is making the retention problem worse
If your DAU/MAU is below 8%, the ranking fix is a product fix. But ASO can reduce the mismatch between what your listing promises and what your app delivers — and closing that gap directly reduces the early-uninstall signal that drives User Loss Rate. The simplest diagnostic: open your first two screenshots and then open your app on a cold install. Does screen one of the app match what screenshot one sells? If there's a gap of more than one tap to reach the featured function, your listing is creating retention debt from the first second.
The second adjustment is keyword scope. If your current Play Store metadata ranks you for broad search terms that bring in off-target users, the solution is narrower targeting — deliberately reducing impressions in exchange for better intent. Fewer installs from higher-intent users produce a better DAU/MAU ratio than high installs from a broad audience that churns. This feels counterintuitive, but under the current ranking model it's not: the engagement signal compounds positively once you're consistently above 8%, whereas the volume signal is outweighed by the quality penalty.
When you update your listing to align with your retained-user profile, update your visual assets to match. The Play Store feature graphic is often the first visual element a potential user sees in browse and search result cards — if it showcases a feature that churned users expected but never found, it compounds the acquisition-retention mismatch. Rebuild the graphic to show what your day-30 retained users say is the reason they kept the app. Use the correct Play Store screenshot dimensions when you rebuild assets — the size requirements differ from the App Store.
The ranking shift in one sentence
Google Play in 2026 rewards apps that users keep using. Install volume was always a proxy for quality; DAU/MAU and User Loss Rate are quality measured directly. A tight, high-retention product with a focused use case now outranks a broadly-marketed app with better awareness but lower day-30 retention — and the ranking advantage compounds as the engagement signal accumulates over time.
If your DAU/MAU is already above 20%, the algorithm is working in your favor and the main lever is acquisition. If it's below 8%, no amount of ASO optimization moves your visibility until the product retention issue is addressed. Fix the onboarding flow, add a daily hook, and close the gap between what your screenshots promise and what your first session delivers. Then rebuild your Play Store listing assets with the updated story in the editor below.
Rebuild your Play Store listing →
Frequently asked questions
what is the minimum dau/mau ratio for google play ranking
Google Play requires a DAU/MAU ratio greater than 8%, measured over a rolling 28-day window with at least 24 days of qualifying data. Apps below this threshold may receive a visible warning on their store listing and lose eligibility for certain discovery surfaces, including recommendation placements and some browse categories. A ratio above 20% is considered strong; top apps in daily-use categories regularly reach 40–60%.
does google play still rank apps by number of installs
Yes, install velocity is still a ranking factor — particularly for keyword relevance on new apps. But since 2025 it is weighted alongside retention metrics (DAU/MAU ratio, User Loss Rate) rather than as the dominant signal. High-volume install campaigns that produce low-intent users now carry ranking downside because each low-intent uninstall depresses DAU/MAU and raises User Loss Rate, and the retention damage outlasts the short-term install boost.
what is user loss rate on google play
User Loss Rate is the ratio of users who uninstalled your app from all of their devices compared to users who have it installed on at least one active device. Google tracks it in Android Vitals alongside DAU/MAU and crash metrics. A high User Loss Rate — especially in the first 72 hours after install — signals that your listing set an expectation the first session didn't meet, and it suppresses Play Store rankings over time.
where do i find my dau/mau ratio in play console
Go to Android Vitals → Core Value in Play Console. The Core Value dashboard shows DAU/MAU ratio and User Loss Rate with threshold bands indicating whether you are in the "needs improvement," "approaching threshold," or "good" zone. For the day-by-day retention curve, go to Users & Events → Retention to see day-1, day-7, day-14, and day-30 cohort retention percentages.
how do i improve dau/mau ratio for my android app
The four highest-impact moves: add a home screen widget that delivers daily value without requiring the full app to open; implement contextual push notifications triggered by user behavior (not a fixed time-of-day timer); design your first session to leave a meaningful open loop that pulls users back on day 2; and audit whether your keyword targeting and screenshots are attracting users who are actually a fit for your app. DAU/MAU is a product metric — listing improvements help only after the core daily-use habit is designed into the app itself.