PcoWSkbVqDnWTu_dm2ix

Analytics Dashboard

Analytics Dashboard

15 min

This document outlines a high level tutorial for how developers will be able to view KPIs (Key Performance Indicators) around retention and engagement.

Setup

Due to system capacity limit, only experiences with at least 600 DAUs and 600 hours of playtime in the past 7 days will be enrolled for the dashboard. Once your experience becomes eligible, you will need to follow these steps in order to officially enroll it for viewing the developer dashboards.

  1. The experience owner will need to navigate to the experience overview page on the Creator Dashboard and agree to Roblox’s Terms of Use.

Experience owners can activate analytics at any point by clicking the button shown in the top right corner labeled Activate Analytics. If you decline the Terms of Use, you may need to refresh the page to see the button again.

Once the Terms of Use are agreed to, the Activate Analytics button will disappear and experience owners and editors can access the charts shown in the Analytics tab (you may need to refresh the page). Note all the metrics are updated daily, so you will see metrics on your dashboard the day after activation.

  1. At this point, experience owners and editors both have access to the KPI charts shown under Overview, Engagement, and Retention.

Dashboard Views and Functions

Once you click into a specific experience, you will be shown a top level overview page containing two KPI charts for DAUs and the number of new users respectively.

For each of these chart pages, you will be able to see a date filter at the top of the page as well as information icons explaining what each chart represents as well as how to interpret the summary statistics shown at the top of each chart.

Page Navigation

You can navigate to different pages within the analytics page for your experience by simply clicking on a different page in the navigation menu on the left of the page. You can do this within each of your experiences under Analytics.

It’s important to note that only the Engagement and Retention pages will be available in the current launch, but other pages will be available in the future. Also note that you can still access the old Developer Stats page for monetization metrics in the interim.

In-Page Functionality

Date Filter

For each page, a date filter can be applied to all the charts on the page. This filter will be a date range where the user can select any specific time frame between the first date that data was available and present day. Below is an example of how the date filter looks. You must select start and end dates separately.

Chart Exporting

For each chart, you can export the underlying data which currently includes the timestamps and the exact value of each datapoint per KPI. The resulting CSV file can then be uploaded to a separate platform for further analysis if you so choose to do this.

Benchmarking

For the retention and stickiness KPIs, you will be able to see benchmarks which are updated on a 3-month quarterly basis. The experiences on the platform are divided into 6 tiers based on their overall engagement performance, including Top 250, 251-500, 501-1000, 1001-2000, 2001-4000, and 4001-8000. By the end of each quarter, ranks and tiers will be updated and the average value for each KPI during the quarter is calculated. Benchmark is then based on the median of all the experiences in each tier. Take D30 stickiness in the 501-1000 tier for example. The system will rank and decide the 500 experiences in this tier first, calculate the average D30 stickiness for each of these experiences in this quarter, rank the KPI among these experiences from lowest to highest, and take the median i.e. the value ranked at 250. Note that if your experience is in the top tier, you will see benchmarks for the Top 250 experiences. Every other experience will see benchmarks for the tier above. For example, if an experience is currently ranked 1600, then you will see benchmarks for the tier 501-1000. Also note that if your experience is ranked below 8000, you will see benchmarks for the tier 4001-8000 regardless of your individual experience rank.

You can use this information to decide which KPIs to optimize for and set reasonable goals in order to move to the next tier.

KPI Breakdowns

For the Overview and Engagement pages, a breakdown can be applied to all charts on the page. You will be able to toggle between the following breakdown types using the “View” dropdown: Country, Language, Age Group, Platform, and OS.

Breakdown Description
by Country (top 5) Selecting this option will break down a KPI chart by the top 5 countries (where your experience has the most DAUs) in addition to the Total (default view). "Other" is the aggregate of all other countries where you have users.
Use Case: Understand latest trends across the top 5 countries where your experience is most popular.
by Language (top 5) Selecting this option will break down a KPI chart by the top 5 languages (where your experience has the most DAUs) in addition to the Total (default view). "Other" is the aggregate of all other languages where you have users (chosen by your players during playtime, not every language available by your experience).
Use Case: Understand which languages are most popular across your users to help prioritize localization efforts. You can also see the impacts of adding translation for different languages.
by Age Group Selecting this option will break down a KPI chart by the following age groups: 13 and Under, 13 through Under 18, 18 and Over. "Unknown" refers to users that we do not have age group data for.
Use Case: Understand latest trends across different age groups.
by Platform Selecting this option will break down a KPI chart by the following platforms: Computer, Phone, Tablet, and Console. "Unknown" refers to users that we do not have platform data for. Note that users may be double counted if they played with more than one device.
Use Case: Understand latest trends across different platforms.
by OS Selecting this option will break down a KPI chart by the following OS types: Android, iOS, Xbox one, OSX, and Windows. "Unknown" refers to users that we do not have OS data for. Note that users may be double counted if they played with more than one device.
Use Case: Understand latest trends across different OS types.

Metrics Descriptions

Analytics Overview

Below are some top level metrics that can be used to help analyze performance. Information here can be filtered by date range. Individual chart filters are shown for each KPI chart. All metrics are updated on a 24 hour cadence.

KPI Title Description
DAU The total number of daily active users (DAUs) over a period of time.
Use Case: Understand latest trends in performance and different levels of granularity.
Number of New Users The number of DAUs that are first time players of your experience (over its entire history).
Use Case: Understand user acquisition and performance.

Acquisition and Engagement

Below are some metrics related to acquiring new users and the number of active users you have for your experience. Information here can be filtered by date range. Individual chart filters are shown for each KPI chart. All metrics are updated on a 24 hour cadence.

KPI Title Description
DAU The total number of daily active users (DAUs) over a period of time.
Use Case: Understand latest trends in performance and different levels of granularity.
Number of New Users The number of DAUs that are first time players of your experience (over its entire history).
Use Case: Understand user acquisition and performance.
Number of Player Sessions The number of total plays or visits you receive in a day (DAU). This includes the same user in your experience during different sessions.
Use Case: Understand user engagement trends.
Total Play Time The number of hours players stay in your experience. This is defined based on the number of hours a player stays in a server.
Use Case: Understand user engagement trends.

Retention

Below are some metrics related to retention to help you with understanding your ability to gain new users as well as continue to engage them. Information here can be filtered by date range. Individual chart filters are shown for each KPI chart. All metrics are updated on a 24 hour cadence.

KPI Title Description
D1 Retention Percent of new players that played the experience again within 24 hours after their last session. Note that a new player is defined as a new person that has played for your experience for the very first time.
Use Case: Understand the onboarding experience for new users.
D1 Stickiness Percent of players (both new and existing) who play your experience everyday based on a 24 hour cycle.
Use Case: Understand percentage of players that play your experience every day.
D7 Retention Percent of new players who came back and played your experience within 7 days. Note that a new player is defined as a new person that has played for your experience for the very first time. D7 is also inclusive of D1 players.
Use Case: Understand early user experience.
D7 Stickiness Percent of players (both new and existing) who play your experience everyday based on within 7 days.
Use Case: Understand the percent of all players who play the experience every week. This can also be used to analyze churn rate.
D30 Retention Percent of new players who came back and played your experience within 30 days. Note that a new player is defined as a new person that has played for your experience for the very first time. D30 is also inclusive of D7 and D1 players.
Use Case: Understand how effective it is to convert an early user to a regular player.
D30 Stickiness Percent of players (both new and existing) who play your experience everyday based on within 30 days.
Use Case: Understand the percent of all players who play the experience every month. This can be a good indicator of overall stickiness.

Data Limitations for Metrics

There are three main data limitations to point out with these charts:

  • If there are any gaps in data when processing from the data source, which can happen infrequently for larger datasets, we omit the actual datapoint but interpolate between data from the preceding and subsequent days to show the general trend.

  • D1, D7, and D30 retention and stickiness are measured in number of days, not hours/minutes/seconds. This means that some users may be counted as D1, D7, D30 even if they play an experience just outside the 1, 7, or 30 day window but before the next day. For example, in the case of D1 retention, if a new player ends their first session at 11 a.m. on Day 1 local time, and then starts a new session at 3 p.m. on Day 2 local time, they will still be counted as a D1 retention player since the query keeps track of days, not hours (even though technically 28 hours have passed as opposed to 24 hours).

  • All data is queried on a daily 24 hour basis at the same time every day. This dashboard does not provide any smaller units of time to filter charts by. Additionally, data is updated at 00:00:000 UTC/GMT time and is shown in UTC/GMT on the page.