Measuring the number of active players is vital to the health of your studio’s game. DAU (Daily Active Users) is the number of players that are playing on a daily basis, while MAU (Monthly Active Users) is how many unique players are playing over the month. The MAU can be measured on a 30-day rolling basis or on a calendar basis. The metrics serve as key indicators of player engagement and retention. When conducting marketing campaigns and releasing new features, the MAU can be used as a baseline. Then both metrics can be measured after the campaign or launch is over to see if there’s a sustained positive impact. The DAU and MAU are also important to track for your game’s website and e-commerce/merch store.

How they indicate game health

Healthy games have a good amount of DAU and MAU and have high stickiness, with players returning to enjoy the game or find out what’s new. The metrics can show seasonal trends and trends around holidays. A low amount of daily players can indicate marketing or distribution issues, while a low DAU/MAU ratio can indicate other issues.

Different types of games can have different measures of what a successful DAU/MAU ratio is. Single-player games that are bought once can have a low DAU/MAU ratio. However, that type of game can still have a high player satisfaction rating and can be profitable in terms of number of units sold. Multiplayer games and live ops games need a minimum amount of players in the pool for matches to take place or to populate the game world. For that type of game, the DAU/MAU can indicate whether there needs to be a boost in players with a marketing campaign or by updating or releasing new features. This is where quantitative data can lead to more investigation via qualitative means such as player surveys and reading through player feedback in game reviews.

There are limitations to DAU/MAU metrics. While they reflect on engagement and retention, they are high-level averages that may not correlate with the actual revenue performance or player satisfaction with the game.

Interpreting DAU/MAU ratio for engagement

The DAU and MAU ratio compares how often a player engages with the game in a day versus a month. If there are 10,000 players in a month and there are around 300 players in a day, then the ratio is 300 DAU to 10,000 MAU which is 3%; if there are 5,000 DAU and 25,000 MAU, the ratio is 20%. This ratio is a high-level view of how sticky your game is and how often players return to the game. A ratio of 3% is low, while a ratio of 20% is considered widely to be great and higher ratios of 50% are incredible.

Simple steps to start tracking these metrics

1. Define what an “active” player is: do they need to log in once and play a move in the game or play for at least a few minutes or take some other actions?
2. Track when they hit the milestones to be considered active in a day
3. Build a dashboard that tracks this number over 24 hours and the past 30 days
   1. Create charts to show the DAU and MAU
   2. Create cohorts and filters for player attributes to understand differences in DAU and MAU across the player base

How to create and view DAU/MAU charts

Many analytics dashboards now offer charts of DAU and MAU. However, each product can define an “active” user differently, so it is important to choose an event that represents meaningful activity for your game before comparing tools or interpreting the ratio.

Google Analytics provides a starting point for tracking these metrics. The engagement overview report includes a user activity over time card that shows activity over the past 1, 7, and 30 days. The user stickiness documentation explains how Google Analytics calculates DAU/MAU, DAU/WAU, and WAU/MAU. Google Analytics counts users who engaged with a website while it was in focus or an app while it was in the foreground. For games, it is better to use a meaningful in-game event for your active-player definition instead of assuming that opening the game is sufficient.

Mixpanel can also be used to measure these metrics. Its guide to DAU, WAU, and MAU recommends selecting an event that active users should perform. The Insights documentation explains how to select the event, measure unique users or DAU/WAU/MAU, choose a date range, and view the results as a time-series chart.

PostHog provides a tutorial for calculating the DAU/MAU ratio. It shows how to create an insight with daily active users and monthly active users, divide the series with a formula, and display the result as a percentage. The Trends documentation explains how to select Daily active users, change the date range, group the chart by day or month, and save the insight.

There are also open-source analytics products and services that can be used for these metrics. Countly has a native Active Users view that displays daily, weekly, and monthly active users in a chart or table. Countly defines active users as unique users who initiated at least one session, which may be broader than the definition used for a game.

Matomo is an open-source and self-hostable analytics platform. Where the Custom Reports feature is available, the Custom Reports guide explains how to select dimensions, metrics, filters, and an evolution graph for a custom active-user report. Matomo also documents how to use its Looker Studio connector to create a time-series chart. Use the event or user metric that matches the active-player definition instead of assuming that Matomo’s default visitors metric is DAU or MAU.

Umami is another open-source option. Its Boards documentation explains how to create and view dashboards, and the board design guide documents visitor and custom-event charts. Umami’s documented board components focus on visitor and custom-event charts rather than a native DAU/MAU view. Use a custom event definition and the Umami API to calculate and chart DAU/MAU when the built-in visitor metrics do not match your needs.

Whichever tool you choose, save the definition of “active” with the dashboard. A ratio built from app opens is not directly comparable to one built from completed matches, purchases, or another meaningful player action.