Hi developers,
We are excited to announce that the Analytics Dashboard has added three new KPIs to help you make data-driven decisions. What’s more, the automatic enrollment threshold has been lowered from 600 DAUs to 500 DAUs, which means additional thousands of experiences are now eligible to leverage the new dashboard!
New KPIs
There are two new KPIs – MAU and Average Session Time – added for Engagement and one new KPI – Week1 Retention – for Retention.
MAU (Monthly Active User)
-
Definition: Number of unique players who joined the game at least once in the past 30 days.
- Note this metric is based on the rolling 30-day period, not the calendar month, and updated on a daily basis. You can get MAU for each calendar month by looking at data on the first day of each month, e.g. 4/1 for March MAU.
-
How to use: Like DAU, MAU is a common engagement KPI that indicates your experience’s scale and growth trend in a longer period of time. MAU can be maintained or grown by providing regular updates that motivate your players to continue staying in the experiences and addressing any issues that cause players to leave (such as bugs that cause crashes or buggy states). You can also calculate the DAU/MAU ratio by downloading the data. The ratio can be interpreted as the percentage of days in a month that an average player plays your experience or as the percentage of your monthly players that play your experience every day. If your DAU/MAU ratio is high, that means that players are frequently engaging with your experience throughout the month.
Average Session Time
-
Definition: The average time a player stays in your experience per session and is calculated by total playtime divided by the number of sessions on each day.
- Note: If your experience has multiple places and a player teleports among them without leaving your experience, the system will count it as a single session. If a player joins your experience multiple times a day, each visit will be a unique session.
- The session time will be the sum of the time spent in each of the places the player visited, which will give you a full picture of how long your player engaged in one visit.
-
How to use: Average session time measures how long a user plays each time they visit your experience. You can compare it with your expectations based on your game design and genre. Breaking it down by age group, platform, etc. will give you an idea of where to iterate your content. It can be used together with D1 retention as an early indicator of your long-term retention.
W1 (Week 1) Retention
-
Definition: Percentage of new players in Week0 (D0-D6) who also played at any point during Week1 (D7-D13).
-
How to use: W1 Retention is a good metric to track if you are interested in building a more casual experience, i.e. something that players play on and off over time. Similar to D7 retention, a low or declining W1 retention can indicate that there are issues with your first-time player experience or initial progression curve.
Lowered Enrollment Threshold
As mentioned in the past announcement, we will keep scaling our system to enroll more experiences. The previous threshold was a minimum of 600 DAUs and 600 hours total playtime for an experience to be eligible for the new dashboard. Now as long as your experience has at least 500 DAUs and 500 hours total playtime consecutively in the past seven days, it will automatically be eligible.
Note you still need to activate the dashboard to see the metrics. Check out our previous post to learn more.
Usability Improvement
Thanks to the feedback from the community, we have made a number of usability improvements:
- The default date range is 28 days instead of 7 days so that you can see week-over-week trends.
- The date range and breakdown are now persistent across pages so you don’t need to change it again when switching pages.
- The KPI breakdown dropdown is now called “Breakdown by” so it’s easier to understand.
We hope you enjoy this update and leverage the dashboard to bring your experiences to the next level! Please let us know if you have any feedback.
Cheers for better insights,
The Roblox Creator Services Team