Every app has two very different user counts. One is the total number of people who ever installed it or signed up. The other is the number who opened it and did something in a defined window of time. That second group, the active users, is the one that pays the bills, because a dormant install generates no sessions, no ad impressions, and no purchases.

How it works

Active users are always measured over a window, and three windows are standard. DAU, or daily active users, counts the unique people who engaged in a single day. MAU, or monthly active users, counts the unique people over a rolling 30-day period. Weekly active users, or WAU, sits between the two. The ratio of DAU to MAU is a common measure of stickiness, showing what share of your monthly base shows up on an average day.

Active users vs. installed and registered

It helps to separate three states. An installed user has the app on their device but may never open it. A registered user has created an account but may have gone quiet. An active user did something in the measurement window. Install and registration counts look impressive in a pitch, yet they overstate the audience you can actually monetize. If you report revenue against installs instead of active users, every efficiency metric looks worse than it really is, because most of that denominator is dormant.

Why active users matter for monetization

Active users are the denominator for the metrics that describe how well an app earns. ARPDAU, average revenue per daily active user, divides daily revenue by DAU, so a clean active-user count is a prerequisite for reading it correctly. The same logic applies to retention and engagement analysis. Growing the active base, rather than the install base, is what lifts total revenue, because only active users generate sessions where ads can serve and offers can be completed. It is also why teams separate new and returning active users, since a base that looks stable can hide heavy churn masked by a steady stream of fresh installs.

Active users and the offerwall

An offerwall earns on completed offers, so its revenue scales with how many active users open it and finish a task. A large install base does nothing for offerwall earnings if those installs never launch the app. A smaller but highly active base gives more people the chance to discover offers and complete them. This is why publishers who add an offerwall watch active-user counts and session frequency closely: the placement only works when real people are present to engage with it.

Common mistakes to avoid

• Counting installs or registrations as active users, which inflates the audience and distorts every per-user metric.

• Comparing DAU from one app to MAU from another. The windows are different, so the numbers are not comparable.

• Treating all active users as equal. A user who opens the app and closes it is active by definition but worth far less than one who plays a session and completes an offer.