Daily Active Users (DAU)

DAU

Daily Active Users (DAU) is the count of unique users who perform at least one meaningful action in your product within a given calendar day. It is the highest-frequency engagement signal available, capturing whether your product is a daily habit or an occasional destination. What qualifies as "active" must be defined explicitly — a login alone is a weak proxy; a core workflow action is far more meaningful.

formula.sh

DAU = unique users with ≥1 qualifying event on a given day

> Unique users: deduplicated by user ID, not session or device
> Qualifying event: product-defined core action (e.g., sent message, ran report, created item)
> Given day: a UTC calendar day or a rolling 24-hour window — be consistent

example

example.sh

Your project management tool has 3,200 users who created or updated a task on Tuesday.

Count of distinct user_ids with a task_create or task_update event on 2024-03-05

→ DAU = 3,200

why it matters

DAU is the clearest signal of whether your product has become a habit. Habit-forming products — Slack, Linear, Notion — have DAU/MAU ratios above 40%. Consumer apps aim for 20–30%. B2B SaaS tools used for specific weekly workflows naturally cluster around 10–20%. Knowing your expected use frequency lets you set a meaningful DAU target instead of measuring against an irrelevant benchmark.

DAU trends also surface product health problems that lagging metrics like MRR miss entirely. A declining DAU three months before churn spikes gives you a window to intervene. Teams that instrument DAU early build the retention instincts that teams who only watch revenue never develop.

common mistakes

✗Counting any login or page view as "active" — this inflates DAU and masks disengagement

✗Comparing your DAU/MAU ratio to consumer app benchmarks when you run a weekly-workflow B2B tool

✗Tracking DAU in isolation without a denominator — always express it relative to total registered or paid users

pro tips

✓Define your qualifying event in a product spec before you instrument it — changing the definition mid-stream makes trend data useless

✓Plot a 7-day rolling average of DAU to smooth weekday/weekend variance and spot real directional changes

✓Segment DAU by cohort age (week 1 vs. week 8 users) to separate new-user activation noise from true retention signal

the mrrsucks take

Your DAU is so low that your product technically qualifies as a haunted house — people enter once, sense something is wrong, and never return. The good news is your infrastructure costs are negligible.

faq

What is a good DAU/MAU ratio for SaaS?+

For B2B SaaS with daily-use workflows (chat, project management), aim for 40%+. For weekly-workflow tools (reporting, billing), 15–25% is healthy. Anything below 10% in a daily-use product signals a retention problem.

Should I use UTC days or user-local days to calculate DAU?+

UTC days are simpler to implement and consistent across your data pipeline. User-local days are more accurate for habit analysis but add complexity. Pick one and never switch — the trend matters more than perfect precision.

How is DAU different from sessions?+

A single user can generate multiple sessions in a day but counts as 1 DAU. Sessions measure visit frequency; DAU measures user reach. Use sessions for UX analysis and DAU for engagement health.

1,000 active users milestone›

related metrics

./install-the-daemon

$9. 365 roasts. one public endpoint of pure shame.