Data Explorer V2 (beta)
Data Explorer V2 is a data analysis tool that you can use to make customized visual representations of your data without SQL queries. You can use Data Explorer V2 to create customized reports to suit your specific analytics needs. For example, you can use these reports to analyze custom events and monitor how your game activity, key metrics, and events change over time.
Data Explorer V2 returns a maximum of 1000 rows in a report. If you need to use queries that return more than 1000 rows, you can use Data access.
To access Data Explorer V2 from the Unity Cloud Dashboard while it’s in beta, select Analytics > Data Explorer > Try New Experience.
You also have the option to select New Experience when you create a new report.
Visualization
To view your Data Explorer reports in the Cloud dashboard, select Analytics > Data Explorer. This page shows all of your existing reports. To view or edit a report, select the report name. You can also create a new report from this page.
The Data Explorer uses graphs to provide data visualization. You can toggle your data representation between the following types of chart:
- Line
- Column
- Stacked Column
- Area
- Pie
- Bar
- Stacked Bar
A Data Explorer report also contains a summarization table of your queried data. Each column shows the measures you select, grouped by the dimensions you select. The table consists of a static row of data with information related to the aggregation filter that you select from the dropdown: either Total, Average, or Median.
Measures (y-axis)
You can use Data Explorer V2 to query your game data based on the following measures in the y-axis:
You can use the following types of filters to further filter your measures:
Metrics
The following tables show all of the metrics that you can use to query your game data:
Active users
| Metric Name | Description |
|---|---|
| DAU | Daily Active Users: the number of unique players that started a session on each calendar day. |
| WAU | Weekly Active Users: the number of unique players that started a session in the previous 7 days from any given calendar day. |
| MAU | Monthly Active Users: the number of unique players that started a session in the previous 30 days from any given calendar day. |
| DAU per MAU | Daily Active Users per Monthly Active Users: the percentage of monthly active users who played on a particular day. This is known as your sticky factor, and a high “sticky factor” means that players continue to engage with your application over time. |
| New Users | The count of your daily users who were new on a given day. |
| New vs Returning users | The percentage of your daily users who were new on a given day. |
Retention
| Metric Name | Description |
|---|---|
| D1 Retention | The percentage of users who returned to your game one day after playing for the first time. |
| D7 Retention | The percentage of users who returned to your game seven days after playing for the first time. |
| D30 Retention | The percentage of users who returned to your game thirty days after playing for the first time. |
Revenue
| Metric Name | Description |
|---|---|
| Payers | The count of daily active users who spent money on a given day. |
| ARPPU | Average Revenue Per Paying User. This metric includes revenue from both transaction and ad impression events where available. |
| APRDAU | Average Revenue Per Daily Active User. This metric includes revenue from both transaction and ad impression events where available. |
| Total Revenue | The sum of all revenue from IAP and Unity Ads if configured. |
| IAP Revenue | In App Purchase Revenue: the sum of all verified IAP transactions. |
| Total Transactions | The count of all transactions. |
| Revenue per Transaction | The sum of all transaction amounts divided by the number of transactions. |
Sessions
| Metric Name | Description |
|---|---|
| Average Session Length | The amount of time that passed between when the user starts the app and when the user takes an action to exit the app. |
| Number of Sessions | The count of sessions played on a given day. |
| Sessions per User | The average number of sessions per user playing on a given day. |
| Total Play Time | The cumulative playing time of all people playing on a given day. |
| Play Time per User | The average playing time of users playing on a given day. |
Events
You can also query your game data based on your game events. The events available consist of both standard and custom events used in your game. In addition, you can use event parameters sent with an event to filter an event measure.
To group by event measures, you can select Event parameters as a dimension.
| Standard event name | Description |
|---|---|
| newPlayer | Sends when a new player installs the app on their device. |
| gameStarted | Sends at the start of a new session. A new session starts when the user first launches an app. |
| gameEnded | Sends when a player exits the game. |
| gameRunning | Sends periodically when the app is running to detect session activity. |
| clientDevice | Records the first time a user launches an app and when device information changes. |
| ddnaForgetMe | Records when a player opt outs of data collection via the privacy plugin. |
| transaction | Sends when a player makes an in-app purchase and tracks the purchase amount. Transaction validation is done via the Unity IAP. |
| adImpression | Can be sent manually when a player has seen an ad within the game. |
| sdkStart | Sends when the SDK initialises. |
| notificationOpened | Sends when a Push Notification is opened or a notification was received while the game is in front. |
| notificationServices | Records the player’s push notification tokens. |
| outOfGameSend | Sends when a Push Notification is sent to a player. |
| userAssignment | Automatically assigns a player to a campaign for reporting. |
Dimension filters
You can apply dimension filters to the game data based on predefined metrics or events.
The following table shows the dimension filters available:
| Dimension Filter | Description |
|---|---|
| Platform | Country that the player last sent an event from. |
| Country | Platform that the player last sent an event from. |
| Client Version | SDK version that the player last sent an event from. |
| Acquisition Channel | Channel that the player was acquired from. |
| Event Parameter | Event parameter value required for Event Measure. |
Aggregate filters
You can use aggregate filter options to further modify your game data. By default, the report aggregates the game data by the Sum of the event or metric data.
Note: You can’t perform aggregation on parameter values.
| Aggregate filter | Description |
|---|---|
| Sum (Default) | Sum of events for all users. |
| Average | Average of event count across all users. |
| Max | Maximum number of events sent by given user. |
| Mix | Minimum number of events sent by given user. |
| Median | Median number of events sent by given user. |
| Unique Users | Sum of events for all unique users. |
Dimensions (x-axis)
Dimensions are different properties, based on either time or user properties, that you can use to group your data.
You can use the following dimensions on the c-axis of your chart:
Time dimensions
| Dimension name | Description |
|---|---|
| Day (Default) | Calendar date grouped by day. |
| Month | Calendar date grouped by month. |
| Year | Calendar date grouped by year. |
| Player Start Date | The date that a player first sent an event. |
| Days Since Player Started | Days since a player first sent an event. |
User Properties dimensions
| Dimension name | Description |
|---|---|
| Country | Country that the player last sent an event from. |
| Platform | Platform that the player last sent an event from. |
| Client Version | SDK version that the player last sent an event from. |
| Acquisition Channel | Channel that the player was acquired from. |
| Event Parameter | Event parameter value required for Event Measure. |
Note: To use the Event Parameter dimension, you need to have an event measure. If you select multiple event measures, you can select an event parameter from any of them.
Example reports
Analyze new users by country
The goal of the report in this example is to understand the distribution of new users across different countries to identify regions with high growth potential and optimize user acquisition strategies accordingly.
This report uses the following configuration:
- Chart visualization: Stacked bar chart
- Measure (y-axis): New Users.
- Dimension (x-axis): Country.
Steps
- In the Measures section, select Add Metric > New Users.
- In the Dimension section, select Add Dimension > Country.
- On the top right of the chart, select Stacked Bar from the dropdown.
- On the top left of the chart, select the data range you want to analyze from the dropdown.
To hide items from your chart visualization, select the item in the legend.
Chart visualization
Analyze vegetables harvested in the last 30 days
The goal of the report in this example is to analyze the distribution of harvested vegetables in a farming game over the last 30 days in order to understand recent player preferences and optimize in-game features accordingly.
This report uses the following configuration:
- Chart visualization: Pie chart.
- Measure (y-axis): vegetableHarvested event.
- Dimension (x-axis): vegetableName event parameter.
Steps
- In the Measures section, select Add Event > vegetableHarvested.
- To filter out any parameter values, you can select Add filter.
- In the Dimensions section, select Event Parameter from the Dimension dropdown.
- Select vegetableName from the Event Parameter dropdown.
- On the top right of the chart, select Stacked Bar from the dropdown.
- On the top left of the chart, select the Last 30 Days date range.
Chart visualization
Analyze harvested vegetables since install, rather than by calendar date
The goal of the report in this example is to analyze the distribution of harvested vegetables in a farming game by the number of days since the player started, in order to understand player behaviors and optimize in-game features accordingly.
- Chart visualization: Stacked Bar chart.
- Measure (y-axis): vegetablePlanted event.
- Dimension (x-axis): Days Since Player Started and the vegetableName event parameter.
Steps
- In the Measures section, select Add Event > vegetablePlanted.
- To filter out any parameter values, you can select Add filter.
- In the Dimensions section, select Days Since Player Started from the Dimension dropdown.
- Select Add Dimension to add another dimension.
- Select Event Parameter from the second Dimension dropdown and select vegetableName from the Event Parameter dropdown.
- On the top right of the chart, select Stacked Bar from the dropdown.
Chart visualization
