Journal · 12 March 2026

When DAU lies, read the weekly pulse

Daily active users is a courteous metric. It applauds almost any intervention that wakes a sleeping phone: a push, a badge, a weather widget that happens to open the app. In App Analytics rooms across the United Kingdom I have watched DAU rise on a Tuesday and become a strategy by Thursday. The weekly pulse — unique people who did a meaningful task in seven days — is ruder, and therefore more useful.

A pulse is not WAU with a nicer name. WAU still counts a glance. A pulse asks for a completed job: a saved article, a paid scan, a workout logged, a ticket viewed to the end. If you cannot name that job, you are not ready to plot a line.

How DAU gets flattered

Notification permission is the usual accomplice. A campaign that wins more opt-ins will lift DAU even when the underlying habit is flat. So will a session definition that restarts on every cold start. So will a “home_viewed” event that fires when a widget refreshes in the background. None of this is fraud. It is a stack doing what it was told, while the slide title says “engagement.”

In Cohort Signal Lab we ask students to plot DAU and pulse on the same axes for ninety days. The typical pattern is a noisy daily line hugging a campaign calendar, and a weekly pulse that barely notices. That gap is the real finding. It is also politically awkward, which is why it belongs in the memo rather than in a buried appendix.

Choosing the job

Pick a job a sceptic in finance would recognise as use. “Opened” will not survive that test. “Completed first successful transfer” will. For a media app we have used “finished 70% of a piece longer than four minutes,” because skimming a headline is not why the product exists. For a museum audio guide, “started stop three” beat “opened tour,” which had been firing on prefetch.

Once the job is named, instrument it with a versioned event and stop celebrating DAU in the same sentence. You may still report the daily count to the store listing team. Just do not let it set the product agenda.

A slower ritual

The weekly pulse wants a ritual, not a dashboard tile that blinks. On Monday morning, export the previous ISO week, annotate any release or outage, and write two sentences: what moved, and what you refuse to conclude. That is the whole meeting. If you need a studio to practise the lattice around this number, the Cohort Signal Lab syllabus spends week two on it.

DAU will remain on every vendor homepage. Let it. The craft is knowing when it is clapping for a notification, and when someone actually came back to do the work.