2 April 2026
Why DAU misleads subscription apps
A daily-active line is a polite number. Subscription products are not polite. They have trials, grace periods, and people who open the app only to cancel.
DAU treats a user who opened the app to manage billing the same as a user who finished a workout, read three articles, or sent a payment. For a social product that might be defensible. For a subscription, it hides the only question finance is allowed to ask: are paying customers still receiving the thing they pay for, on a cadence that matches the billing clock?
We have sat with teams who celebrated a DAU spike the week a payment outage forced everyone into the help screen. The chart was green. The reviews were not.
Counts we prefer in the Atlas
Weekly actives among currently billed accounts. Completions of the core object (workout finished, article read past the fold, transfer succeeded) among that same group. Trial starts that have not yet converted, kept on a separate line so they cannot inflate habit. Billing-retry opens, which are a support metric wearing product clothing.
None of these is glamorous. All of them survive a board question. DAU can stay on an engineering health panel if you like — crashes and launch time belong somewhere — but it should not be the sentence that opens the weekly.
The instrumentation catch
You cannot draw “currently billed” without a trustworthy subscription state. Store callbacks lag. Grace periods exist. A user can look billed in the app and lapsed in finance. The Cohort Atlas spends a week on that seam because a prettier chart will not close it.
If your DAU is the only number the exec team can recite, write to us. We will not scold you for using it; we will ask what it is currently hiding.