DAU, MAU and stickiness: when the reason between them says something and when it deceives

The ratio between daily and monthly users has become one of those numbers that people quote without checking whether it makes sense for the product itself. Thirty percent of stickiness becomes a board goal, a pitch comparison, a reason for celebration or panic. The problem is that this metric measures a very specific thing, habit frequency, and not every product should have a daily habit to be successful.

Before chasing a number, it's worth understanding what it actually describes. DAU is the count of active users in a day. MAU is the count of active users for the month. Stickiness is the ratio between the two, and what it tries to capture is how many of your monthly users show up on a typical day. Read like this, it's less about base size and more about intensity of use.

What the DAU over MAU ratio really says

When you divide one-day users by monthly users and multiply by one hundred, you get an estimate of how often the average user comes back. If stickiness is fifty percent, the typical user shows up on about half the days of the month. If it's ten percent, it appears in about three days. The metric translates frequency into a single number that is comparable over time.

This is the correct and useful reading: the reason is a thermometer of habit. Products that enter people's daily routine, communication tools, teamwork tools, personal productivity tools, exhibit high stickiness because the user has a reason to open them every day. The metric rises when the product becomes part of the workflow and falls when it becomes something that the person remembers exists from time to time.

What makes stickiness valuable is that it is difficult to apply makeup. You can inflate BAD with an acquisition campaign that brings people who come in once and disappear. But this same campaign destroys stickiness, because it fills the denominator with users who don't return. The reason tends to expose the quality of engagement behind the gross growth, and therefore it is worth monitoring it together, never in isolation.

Why it is a sign of habit, not general health

The trap begins when treating stickiness as synonymous with business health. They are different things. Stickiness measures usage habit. Health measures whether the customer stays, expands and pays what it cost. There are modest stickiness products that are excellent businesses, and high stickiness products that bleed money. Reason says only one thing, and giving it a broader meaning is where the error lies.

Think of a product that the user opens every day but that retains poorly and never expands revenue. Stickiness is beautiful and business is fragile. Now think about a tool that the company uses once a month to close the payroll, with an annual contract and very high renewal. Stickiness is very low and the business is solid. The number alone would classify the first as healthy and the second as sick. Both judgments would be wrong.

That's why stickiness belongs to the product and engagement domain, not the revenue domain. It talks to activation and adoption, helps to understand whether usage is deepening or cooling down, and anticipates retention movements. But the decision about the health of the business is made by crossing this signal with revenue retention and unit economics, never with the engagement ratio as the sole arbiter.

When stickiness actually makes sense

Stickiness is a great guiding metric for products whose value proposition depends on frequent use. If your product only delivers on its promise when the user comes back again and again, a messaging tool, an operational dashboard, an app that replaces an old habit with a new one, then the daily to monthly ratio is almost a direct measure of success. The more people come back, the more value they extract, and the metric accurately reflects this.

In these cases, stickiness works as an early alarm. It drops before churn appears, because the user first reduces frequency and only then cancels. An attentive team notices the deceleration of the habit weeks or months before the client formalizes the exit, and gains time to act while the relationship still exists. As an early sign of retention risk, few product metrics are as sensitive.

It also helps you compare cohorts and measure the effect of product changes. Launched a feature that was supposed to increase usage frequency? The stickiness of the cohort exposed to it, compared to the previous ones, tells us whether it worked. The number becomes an instrument of experimentation, closely linked to the adoption of features, and then it pays off a lot, because you use it to answer a concrete question about behavior.

When it cheats and what to measure instead

For products that are sporadically used by nature, stickiness not only loses their usefulness but also leads to wrong decisions. Tax return software, annual planning platform, hiring tool used when there is an open position, invoice issuance system that the small business opens a few times a month. In all cases, rare use is healthy behavior, not a symptom of a problem. Charging high stickiness for these products is charging the customer to use something they don't need every day.

Those who pursue daily reason in these cases tend to pollute the product. Add notifications to force open, create artificial engagement features, transform a tool that should be efficient and discreet into something that demands attention. The user is no longer satisfied, they are more irritated, and the metric that increased did not correspond to any real gain in value. Optimizing the wrong number is costly in experience.

The solution is to change the measurement window to one that matches the natural rhythm of the product. If usage is weekly, measure weekly activity over monthly. If it's monthly or quarterly, ditch the stickiness and look at other things: the rate at which the user completes the work they hired the product for, the recurrence of use per relevant cycle, the revenue retention over the periods. What matters is not the daily frequency, it is whether the customer does what they need when they need it, and returns in the next cycle.

How a CTO should read these numbers

The discipline that separates those who use these metrics well from those who are fooled by them is deciding, before measuring, what frequency of use means success for your specific product. This decision comes from the nature of what you sell, not from the benchmark of some company whose product may have nothing to do with yours. Defining the ideal frequency is a product strategy choice, and the metric is only useful after this choice is clear.

Once the target frequency is defined, stickiness, or the equivalent ratio in the right window, becomes an honest instrument. You monitor it along with acquisition, so as not to be mistaken with gross growth, and along with retention, to understand whether the habit supports retention. These three signs read together tell a story that none of them tells alone, and this story is that of the real engagement of the base, linked to what I showed about user activation at the start of the journey.