Required Datapoints
- WAU (Weekly Active Users): Unique users interacting with your product during a 7-day period.
- MAU (Monthly Active Users): Unique users interacting with your product during a 30-day period.
The **WAU/MAU Ratio **compares the number of Weekly Active Users (WAU) to Monthly Active Users (MAU). It represents the percentage of users who engage with your product weekly out of those who are active within a month.
WAU/MAU Ratio is a key indicator of product stickiness and habitual usage, reflecting how many monthly users return on a weekly basis.
The relevance and interpretation of this metric shift depending on the model or product:
A higher ratio means your product is becoming part of a weekly routine, while a lower one may flag engagement drop-off or limited utility.
By segmenting by feature usage, role, or region, you uncover how behavior varies—and where to reinforce habits.
WAU/MAU Ratio informs:
These are the main factors that directly impact the metric. Understanding these lets you know what levers you can pull to improve the outcome
Actionable ideas to optimize this KPI, from fast, low-effort wins to strategic initiatives that drive measurable impact.
Activities commonly tied to improving or operationalizing this KPI.
| Activity | Description |
|---|---|
| Retention Strategies | Retention Strategies involves systematic initiatives and processes aimed at maximizing customer lifetime value by proactively engaging and supporting existing users. It helps teams translate strategy into repeatable execution. Relevant KPIs include Customer Churn Rate and Customer Lifetime Value. |
| Habit Formation Campaigns | Habit Formation Campaigns are structured initiatives designed to encourage and reinforce consistent user engagement with key product features or workflows. It coordinates execution across touchpoints so teams can move users or accounts toward the target outcome. Relevant KPIs include WAU/MAU Ratio. |
A task management app tracks WAU and MAU in March:
This KPI is associated with the following stages in the AAARRR (Pirate Metrics) funnel:
This KPI is classified as a leading Indicator. It signals likely future performance and is used to predict outcomes before they fully materialize.
This role is directly accountable for the KPI and is expected to drive progress and decisions around it.
These roles contribute directly to performance and typically partner on execution, reporting, or optimization.
These leading indicators influence or contextualize this KPI and help create a multi-signal early warning system, improving confidence and enabling better root-cause analysis.
These lagging indicators support the recalibration of this KPI, helping to inform strategy and improve future forecasting.
How this KPI is structured in Cube.js, including its key measures, dimensions, and calculation logic for consistent reporting.
cube('UserActivity', { sql: `SELECT * FROM user_activity`,
measures: { weeklyActiveUsers: { sql: `user_id`, type: 'countDistinct', title: 'Weekly Active Users', description: 'Unique users interacting with the product during a 7-day period.' }, monthlyActiveUsers: { sql: `user_id`, type: 'countDistinct', title: 'Monthly Active Users', description: 'Unique users interacting with the product during a 30-day period.' }, wauMauRatio: { sql: `100.0 * ${weeklyActiveUsers} / NULLIF(${monthlyActiveUsers}, 0)`, type: 'number', title: 'WAU/MAU Ratio', description: 'Percentage of users who engage weekly out of those active within a month.' } },
dimensions: { id: { sql: `id`, type: 'number', primaryKey: true }, userId: { sql: `user_id`, type: 'string', title: 'User ID' }, activityDate: { sql: `activity_date`, type: 'time', title: 'Activity Date' } }});Note: This is a reference implementation and should be used as a starting point. You’ll need to adapt it to match your own data model and schema