The most commonly tracked engagement metrics in tech — and the most commonly misused.

In one quarter, Facebook reported a slight decline in its Daily Active Users. Not a crash. Not a collapse. A slight decline.

Its stock dropped 25% in a single day.

That's the weight these numbers carry. DAU, WAU, and MAU — Daily, Weekly, and Monthly Active Users — are among the most widely tracked metrics in the technology industry. They appear in earnings presentations, pitch decks, board reports, and acquisition conversations. Investors ask for them. Analysts debate them. Products are rebuilt around them.

And yet most startups use these three metrics interchangeably, without understanding what each one actually measures — or which one is appropriate for their specific product and business question.

Used correctly, frequency metrics reveal the underlying health of your user relationships. Used incorrectly, they produce numbers that look informative and mislead every decision made against them.

The Definitions (With Precision)

Before anything else, the precise definitions — because imprecision here is where misalignment starts.

DAU — Daily Active Users: A distinct count of users who were "active" in the past 24 hours, or on a given calendar day. The word "distinct" is critical: a user who opens your app three times in one day counts once, not three times. You're counting users, not sessions or events.

The definition of "active" must be documented explicitly. Any session? A meaningful event? A purchase? A message sent? Whatever you choose, it must be consistent — changing the definition mid-reporting breaks trend comparability in ways that can corrupt months of historical data.

WAU — Weekly Active Users: A distinct count of users active in the past 7 days. Same distinct-count logic: a user active five days out of seven counts once.

MAU — Monthly Active Users: A distinct count of users active in the past 28 days (four complete weeks) or the past 30 days. This distinction matters more than most teams realize. A 28-day MAU and a 30-day MAU for the same product will produce different numbers — not just slightly different, but systematically different in ways that create false spikes and troughs in monthly reporting if you switch between them. Document which one you use and never change it without a documented migration.

The Ratios: Where the Real Insight Lives

The individual metrics — DAU, WAU, MAU — tell you how many users are active on each timescale. The ratios tell you something far more interesting: the relationship between those timescales, which is a direct proxy for how sticky and habitual your product is.

DAU/WAU — Short-Term Engagement

DAU/WAU answers: of users who were active this week, what share was active today?

If 500 users were active this week (WAU = 500) and 50 of them were active today (DAU = 50), your DAU/WAU ratio is 10%. That means the average weekly active user uses your product roughly once a week — a low stickiness signal.

If your DAU/WAU is 70%, the average weekly active user is active 4–5 days out of 7 — extremely high engagement.

This ratio is most meaningful for high-frequency products: social media, messaging apps, casual gaming, news apps. For these products, daily engagement is the expected norm, and DAU/WAU close to 100% (divided by 7, the theoretical maximum for a perfect daily product) is the target.

Watch out for within-week seasonality. On consumer products, DAU can be significantly higher on weekdays than weekends (or vice versa, depending on context). Reporting a single DAU/WAU snapshot on a Tuesday will look different than the same snapshot on a Sunday. Use a rolling average or compare the same day across weeks.

WAU/MAU — Product Consistency

WAU/MAU answers: of users who were active this month, what share was active this week?

If 1,200 users were active this month (MAU = 1,200) and 500 were active this week (WAU = 500), your WAU/MAU is 42%. That means roughly 42% of monthly users engage at a weekly frequency.

This ratio is better suited to moderate-frequency products — tools that users engage with periodically but not necessarily daily. Coinbase is a useful example: crypto portfolio holders check their accounts more often than monthly but not necessarily every day. DAU/WAU for Coinbase would look artificially low because the product isn't designed for daily use. WAU/MAU captures the actual engagement pattern more accurately.

Four Ways to Use These Metrics in Practice

1. Business and Investor Reporting

DAU and MAU are the standard reporting cadence for technology companies at every stage. Investors expect them. Boards track them. Understanding how to present these metrics — with trend lines, regional breakdowns, and definitions made explicit — is a fundamental skill for any operator raising money or presenting to a board.

Facebook's quarterly earnings break down DAU and MAU by region, allowing investors to see where engagement is growing and where it's plateauing. This regional decomposition is exactly the kind of storytelling these metrics enable.

For startups: even if your MAU is three figures, the habit of defining, tracking, and presenting these metrics consistently builds the analytical infrastructure you'll need when the numbers are three orders of magnitude larger.

2. A/B Test Success Metrics

Frequency metrics translate naturally into A/B test success metrics because they can be measured at the user level — which is the unit of analysis in an experiment.

User-level examples:

• "Percent of users in the test group who were active on any given day during the experiment period" (DAU%)

• "Average days active per user in the past 30 days"

• "Percent of users in the test group who were WAU during the experiment period"

These metrics reflect whether a product change drives more consistent, habitual engagement — which is often the ultimate goal of product experimentation beyond simple conversion.

3. Gap Analysis: Converting Engagement Into Revenue

Gap analysis is the practice of quantifying what it would be worth to close the gap between where you are and where you want to be. Applied to frequency metrics, it transforms an abstract engagement goal into a concrete business case.

Here's how the math works. Suppose your product has 503 million monthly active users in a given region, and your current DAU/MAU for that region is 63%. If you could improve DAU/MAU to 66%:

• Incremental DAU = 503M × (66% − 63%) = 503M × 3% ≈ 15 million additional daily active users

• If average revenue per DAU in that region is approximately $0.19 per day, that's roughly $2.85 million in additional daily revenue

• Annualized quarterly: approximately $289 million

This kind of analysis doesn't require billions of users to be useful. The same logic applies to a 10,000-MAU startup trying to decide whether a new notification system is worth engineering investment. Convert the engagement improvement to revenue, and the investment case becomes concrete.

4. Customer Segmentation

Frequency metrics become most powerful when combined with value metrics — average order value, LTV, revenue per session, or whatever measure of user value is most relevant to your business.

Plot your users on a two-axis grid: frequency of visits (X-axis) versus value per visit (Y-axis). Four segments emerge:

• High frequency, high value: VIPs — your best customers; protect and reward them

• High frequency, low value: Browsers — engaged but not converting; potential with the right offer

• Low frequency, high value: Big Spenders — high purchase intent when they show up; win-back campaigns and personalized outreach

• Low frequency, low value: At-Risk — early churn signals; need intervention or reactivation

These segments drive lifecycle marketing, product prioritization, and retention strategy more precisely than any aggregate metric.

Five Common Mistakes

Using the wrong ratio for your product type. DAU/WAU for a product used monthly will always look terrible — not because engagement is poor, but because the metric doesn't match the product's natural rhythm. This generates false alarm and misallocated effort.

Changing the definition of "active" mid-stream. Even a seemingly minor change — adding one more event type to the "active" definition — breaks trend comparability. Every historical data point needs to be recalculated to maintain a consistent series. Document the definition and version-control any changes.

Mixing 28-day and 30-day MAU. If your fiscal calendar uses 28-day months but your MAU reports use 30 days, you'll see artificial fluctuation at the turn of long months. Choose one and enforce it.

Counting sessions instead of users. Active user metrics are distinct user counts, not event or session counts. A user who opens the app five times in one day is one DAU, not five. This sounds obvious until someone's query accidentally joins on session ID rather than user ID.

Ignoring seasonality. DAU is inherently seasonal — weekly seasonality (weekday vs. weekend patterns), monthly seasonality (end-of-month effects), and annual seasonality (holidays, school calendars). Always normalize for expected patterns before attributing a DAU change to a product decision.

Which Metric for Which Situation?

The Right Metric Matches Your Product's Natural Rhythm

There's no universally best frequency metric. The right one is the one that reflects how your best users actually engage with your product — and creates accountability for bringing the rest of the user base toward that ideal.

Start by asking: how often do we expect our best users to use this product? Daily? Weekly? Monthly? Define that as your natural engagement frequency. Then pick the ratio that measures the proportion of your active users who approach that frequency.

That's your engagement health signal. Track it consistently, decompose it by segment, and connect it to revenue. The number that moved a market cap is useful — if you know what you're measuring and why.

The full engagement metrics framework — meaningful events, ratios, gap analysis, and behavioral segmentation — is covered in The Data Strategist course.