Data Explorer V2 (Beta) measures and metrics
For some examples on how to use Data Explorer V2, see the Data Explorer V2 example reports.
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 7 days after playing for the first time. |
| D30 Retention | The percentage of users who returned to your game 30 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 adImpression events where available. |
| APRDAU | Average Revenue Per Daily Active User: this metric includes revenue from both transaction and adImpression 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 | Records when a new player installs the app on their device. |
gameStarted | Records at the start of a new session. A new session starts when the user first launches an app. |
gameEnded | Records when a player exits the game. |
gameRunning | Records 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 requests deletion of their personal data. |
transaction | Records when a player makes an in-app purchase and tracks the purchase amount. Transaction validation is done via the Unity IAP. |
adImpression | Can be recorded manually when a player has seen an ad within the game. See the record an ad impression tutorial. |
sdkStart | Records when the SDK initialises. |
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 | 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. |
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 | Application version that the player last sent an event from. |
| Acquisition Channel | Channel that the player was acquired from. |
| Event Parameter | 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. |