Weekly Active Users (WAU)

What are Weekly Active Users?

Weekly Active Users (WAU) measures how many distinct users engage with your application during any seven-day period. "Active" means the user took at least one meaningful action — logging in, completing a task, or using a core feature. WAU counts each user once regardless of how many times they interact that week.

A user can be paying or non-paying (for example, someone on a free trial). Identity is typically tracked by username, email address, or user ID.

Why WAU matters

WAU is a leading indicator of product health. Users who engage regularly are extracting value from the product; users who go quiet are at risk of churning.

Tracking WAU over time reveals patterns that point-in-time metrics miss:

• Declining WAU can signal that users are not finding enough ongoing value — often weeks before a cancellation shows up in revenue data.
• Rising WAU following a feature release confirms that the new functionality is driving real engagement, not just curiosity.
• Stable WAU with rising total users suggests new users are not activating, which points to an onboarding problem rather than a product problem.

WAU vs. DAU and MAU

WAU sits between Daily Active Users (DAU) and Monthly Active Users (MAU) on the engagement frequency spectrum. The right metric depends on how often users are expected to engage with the product.

For products with a natural weekly cadence — team collaboration tools, project management software, or analytics dashboards — WAU is often the most meaningful engagement signal. DAU would set an unrealistically high bar; MAU would obscure week-to-week fluctuations that matter.

Users vs. accounts

For most SaaS applications, users are a subset of accounts. A single company account may have five, fifty, or hundreds of individual users.

Tracking WAU at the user level reveals how deeply a product is embedded in day-to-day workflows across an organization. An account where only one of ten licensed users is active each week is at higher churn risk than an account where eight of ten are active — even if both accounts show the same account-level activity.

Tracking both WAU (users) and weekly active accounts gives a fuller picture of engagement breadth and depth.

What counts as "active"

The definition of an active user is one of the most consequential decisions in measuring WAU. A loose definition — such as any login — can inflate the number and mask disengagement. A tight definition — such as completing a core workflow — gives a more honest signal but requires deliberate instrumentation.

Best practice is to define "active" around the actions that correlate with retention and value delivery in your product. For a project management tool, that might be creating or updating a task. For an analytics platform, it might be viewing or sharing a report.

Document the definition and apply it consistently. Changing the definition mid-stream makes trend analysis unreliable.

Common pitfalls

Counting sessions instead of users. If the same user opens the app seven times in a week, that is one WAU, not seven. Ensure deduplication is built into your tracking.

Ignoring the denominator. Raw WAU growth looks positive, but if your total user base is growing faster than WAU, engagement is actually declining. Always track WAU as a proportion of total users or a relevant cohort.

Conflating activity with value. A user who logs in and immediately logs out is technically "active." Pair WAU with depth-of-engagement metrics — such as features used or tasks completed — to distinguish meaningful activity from superficial visits.