How to Increase Daily Active Users

TL;DR

Daily Active Users measures how many unique people perform a meaningful action in a product during one day. The word meaningful matters: counting app launches, passive sessions, or background events can make DAU rise without showing that users receive any value.

To increase DAU sustainably:

1. Define an active user around the product’s core value.
2. Help new users reach that value faster.
3. Give users a credible reason to repeat the core action.
4. Personalize the next session rather than showing everyone the same home screen.
5. Use progress, social mechanics, fresh content, and reminders only when they strengthen the product’s natural use case.
6. Measure whether growth comes from new, retained, or reactivated users instead of treating DAU as one undifferentiated number.

There is no universal “good” DAU. A messenger, learning app, banking product, travel service, and tax app have fundamentally different natural usage frequencies.

Introduction

Mobile users are not spending less time in apps. Sensor Tower estimates that people spent 5.3 trillion hours in mobile apps in 2025. The problem for product teams is that this attention is distributed across an increasingly crowded market. Almost 15,000 new subscription apps now launch every month, compared with approximately 2,000 per month three years earlier.

Against that background, downloads and registrations provide an incomplete picture. They show that a product managed to attract attention once. They do not show whether the product became useful enough to earn another session.

Daily Active Users, or DAU, helps answer a more difficult question: How many people found a reason to use the product today? For teams asking how to increase daily active users, the first priority is to understand whether the app gives each daily user a recurring reason to return. 

That makes DAU an important indicator for products expected to support frequent behavior. Deloitte describes growth in daily active users over time as a potential leading signal of platform health. The broader question of how to increase active users cannot be answered through acquisition alone; activation and retention have to improve together.  

However, DAU is useful only when the metric is defined honestly. An app can increase opens through aggressive notifications, mandatory prompts, login requirements, or promotions. It can even count background activity as engagement. None of those changes necessarily means that more users are receiving value. The objective is not to maximize DAU at any cost. It is to increase qualified DAU: the number of unique users who complete an action connected to the product’s value proposition and are willing to return voluntarily.

What is DAU?

Daily Active Users is the number of unique users who perform at least one qualifying activity during a defined day.

A person who opens the app five times should normally count as one DAU, not five. The calculation is the number of unique user IDs that record at least one qualifying active event during a calendar day. The difficult part is deciding what qualifies as active.

When teams report app daily active users, the activity event and identity rules must remain consistent; otherwise, the app DAU total can become misleading. The event should reflect the reason users choose the product. An active-user metric should be based on behavior that demonstrates value rather than casual logins or empty page views. For some apps, one event is sufficient, while for others, a combination is more accurate.

For different products, a meaningful event might be:

Additionally, there is MAU. Monthly Active Users is the number of unique users who meet the product’s activity definition during a monthly measurement window. MAU provides a broader view of audience size: DAU shows daily participation, while MAU shows how many people use the product at least occasionally over the month. Teams exploring how to increase monthly active users should examine whether occasional users reach value often enough to return within the same monthly window. 

How to Calculate DAU

Step 1: Define the qualifying activity

Start by writing a plain-language definition:

A daily active user is a unique user who completes at least one of the following value-related actions during a calendar day.

Then list the qualifying events. For a budgeting app, the list might include:

• reviewing an updated account overview;
• categorizing a transaction;
• changing a budget;
• setting a financial goal;
• paying a bill through the app.

Step 2: Identify a unique user

DAU should count people or accounts, but not sessions. The identifier might be:

• an authenticated account ID;
• a customer ID;
• a stable anonymous ID before registration;
• a carefully reconciled combination of account and device identifiers.

The team needs explicit rules for users who use several devices, reinstall the app, browse anonymously and then register, share an account, or move between the mobile app and website. Otherwise, the same person may be counted twice, or two different people may be merged into one record.

Step 3: Establish the day boundary

Choose the time zone used to determine when one day ends and the next begins. A global product might calculate:

• one company-wide UTC figure;
• local-market DAU;
• both global and market-specific values.

UTC is easier to standardize. Local time may reflect users’ actual daily habits more accurately. What matters is that dashboards, experiment reports, financial reporting, and data documentation use the same rule.

Step 4: Deduplicate qualifying users

For a particular date d:

where that user recorded at least one qualifying event on date (d).

A user who completes ten lessons, places three orders, or opens the app four times still contributes one user to that day’s DAU.

Step 5: Calculate average DAU for longer reporting periods

Companies commonly report average DAU across a week, month, or quarter:

Step 6: Validate the data

Before presenting DAU to leadership, verify that the metric excludes:

• automated background refreshes;
• health checks and monitoring traffic;
• bots and test accounts;
• duplicate users across devices;
• accidental events caused by screen loading;
• internal employees, where appropriate;
• sessions that do not meet the activity threshold.

The metric definition should be versioned. When the definition changes, record the date and, where possible, recalculate historical data. Even large public companies acknowledge that active-user methodologies can change and may not be directly comparable across organizations or reporting periods.

A simple DAU calculation example

Assume that on Monday the app records the following qualifying activity:

Users A, B, C, and E are active. User D is not.

Monday DAU = 4, even though the four active users generated 14 events. Why?

The question how many DAU the app recorded is answered by counting qualifying unique users, not by summing their sessions or events. 

• DAU measures reach among active users.
• Event volume measures frequency or intensity.
• Time spent measures duration.
• Completion rate measures success.
• Retention measures whether users return.

A product can increase event volume without increasing DAU, and increase DAU without improving the depth or quality of use. Product managers should therefore examine these metrics together.

Why Track DAU?

1. To see whether the product earns repeat use

Install and registration metrics describe acquisition, where DAU indicates whether users continue to participate after acquisition.

A rising registration curve can coexist with weak daily usage when recently acquired users replace those who have already disengaged. Keep in mind that increasing daily totals can conceal falling retention when acquisition temporarily fills the gap.

2. To detect changes faster than MAU allows

MAU changes slowly because a person can remain in the monthly total long after their last active day. DAU responds sooner to:

• onboarding changes;
• product releases;
• broken journeys;
• seasonal shifts;
• notification campaigns;
• pricing or paywall changes;
• content launches;
• reliability incidents.

That makes DAU useful for monitoring short-term movement. It should still be read alongside retention and cohort metrics, as a one-day spike may come from a promotion rather than a lasting improvement. Short-lived viral spikes are different from durable growth thanks to continuing supply of valuable content and interactions.

3. To separate audience size from usage frequency

MAU can rise while DAU/MAU falls. This usually means the product is attracting more occasional users without increasing the proportion who return frequently.

The opposite can also happen: MAU remains flat, but DAU/MAU rises because existing users become more active. For teams asking how to increase DAU/MAU, the most reliable path is to raise the share of monthly users who repeatedly complete the core action. 

These cases require different responses:

4. To understand which features support repeat value

Segment DAU by:

• core feature used;
• new versus established user;
• acquisition source;
• subscription status;
• geography;
• operating system;
• app version;
• lifecycle stage;
• frequency cohort;
• experiment group.

This reveals whether a new feature is associated with continued usage or merely produces curiosity after launch.

For example, compare the rates for 7-day active users and 30-day active users who complete a specific action with similar users who do not. The result is not automatically causal — more motivated users may be more likely to adopt the feature — but it provides a stronger hypothesis for experimentation than total feature clicks.

What to Do to Improve DAU

To increase DAU sustainably, it’s important to prioritize recurring value over superficial opens. The methods below are designed to increase daily active users without inflating the metric through low-value activity. 

1. Shorten the path to first value

A user cannot become a retained daily user without first becoming an activated user.

Activation is often the first lever to examine when active-user growth stalls. It’s important to route users toward the most important useful action before asking them to explore settings, invitations, or advanced functionality. Instead of teaching the whole product, help the user complete one valuable action.

For example:

• A finance app can connect one account and produce the first useful overview.
• A retailer can help the user find a relevant product or local offer.
• A fitness app can start a suitable first routine.
• A learning app can place the user at an appropriate level and complete one short lesson.
• A delivery app can show available options for the user’s location before requesting unnecessary profile information.

With the help of InAppStory, a German groceries shopping chain METRO integrated Stories into their app. In-app communication helped the retailer to highlight partner products, share educational content, and engage users in quizzes and polls. This resulted in 52% of app users actively opening Stories, contributing to a 37% lift in conversion rate.

2. Build a repeatable usage loop

Daily use needs a recurring reason. The product should make clear:

1. what has changed since the previous session;
2. what the user can do now;
3. what value the action creates;
4. what progress remains;
5. why returning later will be worthwhile.

A useful core loop can be expressed as:

For example:

• a new lesson followed by visible learning progress;
• a daily financial update followed by an actionable insight;
• new messages followed by a continuing conversation;
• fresh inventory followed by a saved-item or price update;
• a new challenge followed by progress toward a personal goal;
• newly published content followed by personalized recommendations.

3. Show visible progress

Progress gives users evidence that repeated actions are accumulating into something larger. The reward should remain connected to the product’s purpose. A streak for opening the app is weak. But a streak for completing a lesson, recording a workout, saving money, or finishing a meaningful task reinforces the underlying value.

Possible mechanisms include:

• milestones;
• completed steps;
• streaks;
• weekly goals;
• levels;
• progress bars;
• collections;
• personal records;
• summaries of improvement;
• the next recommended action.

A French peer-to-peer home exchange platform, HomeExchange, used Spotify-like recaps in their app in the form of personalized Stories to drive engagement and loyalty — 26,000 users participated in the activity with a 100% Story completion rate.

4. Personalize the next useful action

A generic home screen forces users to search repeatedly for relevance. A personalized screen can continue the job they have already started. Personalization should answer: What is the most useful thing this person could do next?

This might mean:

• continuing an unfinished task;
• showing a recently used feature;
• adapting difficulty;
• highlighting a relevant service after a transaction;
• recommending content related to a previous session;
• surfacing an updated price or status;
• suggesting a goal based on current progress.

5. Use fresh content or changing utility

Static products struggle to create repeat visits unless the underlying task itself recurs. Temporary viral moments tend to fade, while durable social-platform growth is supported by creators producing material continuously.

Freshness can come from:

• new editorial or creator content;
• updated recommendations;
• changing inventory;
• new offers;
• account or order status;
• live events;
• changing prices;
• community activity;
• personalized reports;
• new challenges;
• newly available functionality.

6. Add social value where it naturally fits

Social mechanics can create reasons to return because another person’s action changes the next session. Deloitte includes user storytelling and community formation among factors that can support user growth.

For example:

• shared goals;
• friend challenges;
• collaborative lists;
• reactions and comments;
• group progress;
• rankings among relevant peers;
• creator subscriptions;
• user-generated recommendations;
• accountability partners;
• invitations tied to a completed action.

Conclusion

A sustainable DAU strategy starts with four questions:

1. What action proves that the user received value?
2. How quickly can a new user reach it?
3. Why would the user need or want to repeat it?
4. What prevents the next session from happening?

From there, product teams can improve activation, make progress visible, personalize the next action, introduce features at relevant moments, strengthen social or content loops, and remove unnecessary friction.

However, the metric still needs limits. A higher DAU is not automatically better when the product solves an infrequent problem, when activity is generated through pressure, or when users could complete the same job more efficiently in fewer sessions. Generic benchmarks should therefore be treated skeptically. Product purpose, cohort retention, core-action quality, and business outcomes matter more than an isolated ratio.

The strongest DAU growth does not come from persuading users to open the app one more time. It comes from building a product in which the next visit has a clear purpose.