Metrics
GameAnalytics offers a list of predefined metrics for specific features.
On the Explore Tool many of the available metrics are simply shortcuts that populate the query building UI. Many additional metrics are possible once you start building queries manually.
Some metrics are marked Unique as these require specific calculations beyond what is manually configurable. They perform multiple calculations internally and therefore often have some limitations in terms of filtering and other options when selected.
The following is a list of metrics available in the Explore Tool feature.
info
GameAnalytics calculate metrics within UTC dates/hours. When mentioning daily metrics below (like DAU or Retention) the reporting is therefore based on UTC definition of days.
Engagement
| Name | Description | Event category |
|---|---|---|
| DAU | Daily Active Users. The unique user count reported per day. | All |
| DAU (New Vs. Returning) | Ratio of new users (observed for the first time) versus returning users (observed previously) reported daily. | All |
| DAU (split by Acquisition Campaign) | Daily Active Users. The unique user count per day split by the acquisition campaign. | All |
| DAU (split by Acquisition Publisher) | Daily Active Users. The unique user count per day split by the acquisition publisher. | All |
| DAU vs. MAU | Percentage of monthly active users (last 30 days) who engaged with your product today. Reported daily. | All |
| MAU (calendar) | Monthly Active Users. The unique user count reported per calendar month. | All |
| MAU (rolling 30 days) | Monthly Active Users (last 30 days). The unique user count last 30 days reported per day (rolling). | All |
| New Users | Count of unique users observed for the first time (events sent) reported per day. | All |
| New Users (split by Acquisition Campaign) | Count of unique users observed for the first time (events sent) reported per day and split by the acquisition campaign. | All |
| New Users (split by Acquisition Publisher) | Count of unique users observed for the first time (events sent) reported per day and split by the acquisition publisher. | All |
| New Users grouped by Country | Count of unique users observed for the first time (events sent) during the period selected reported per country. | All |
| Retention | Retention reports the daily percent of users who installed on a specific day and then returned N days later. Retention is reported as DayN where N is the number of days after install the user was observed. Day7 on a specific day is reporting the percentage of users who installed on that day who returned 7 days later. Multiple lines will display by default for D1,D2,D3,D4,D5,D6,D7,D14. These can be changed to show other days from D1-D90. The calculation uses strict retention > a user is considered returning if they revisit on the exact specified day N and it does not consider activity on previous days. Selecting only a single DayN will allow a split to be defined (for example D1 split by country). | All |
| Returning Users | Count of unique users who were previously observed in the past (events sent) reported per day. | All |
| Returning Users grouped by Country | Count of unique users who were previously observed in the past (events sent) during the period selected reported per country. | All |
| Returning Users split by Days since install | Count of unique users who were previously observed in the past (events sent) during the period selected reported by the day since install (count of days since install). | All |
| Users grouped by New and Returning | Count of unique users reported by new (first observation) or returning (seen before). | All |
| WAU (calendar) | Weekly Active Users. The unique user count reported per calendar week. | All |
| WAU (rolling 7 days) | Weekly Active Users (last 7 days). The unique user count last 7 days reported per day (rolling). | All |
| iOS Users (group by consent status) | Count of unique users sending iOS ATT consent-status reported by each possible status (authorized, denied, notDetermined, restricted). This tracking is done be default in the GameAnalytics SDK's supporting iOS platform. | All |
| iOS Users Consent Authorized | Count of unique users sending iOS ATT consent-status equal to authorized reported per day. ATT tracking is enabled by default in the GameAnalytics SDK's supporting the iOS platform. | All |
Business (IAP)
| Name | Description | Event category |
|---|---|---|
| ARPDAU (IAP) (legacy) | Average revenue (IAP) per daily active users. The IAP revenue sum divided by all daily active user count. Always reported daily. (legacy > replaced by ARPU). | Business |
| ARPPU | Average revenue (IAP) per paying active user. The IAP revenue sum divided by active users who paid at least once in the period. | Business |
| ARPU | Average revenue (IAP) per active user. The IAP revenue sum divided by all daily active user count. This is a more flexible version of the ARPDAU metric. | Business |
| Conversion rate | Percentage of daily active users who made a purchase reported per day. | Business |
| Converted users | Count of unique users who converted to paying since install (sent at least one business event). | Business |
| Converting users | Count of unique users who converted to paying in the current period observed (sent their first business event). | Business |
| Cumulative Revenue per User | Cumulative Revenue per User is reporting on a specific day the amount of IAP revenue per user on DayN where N is the number of days since install (first time observed). Day7 on a specific day report the average IAP revenue per user for the users who installed 7 days ago. Multiple lines will display and by default it's 1,2,3,4,5,6,7,14. These can be changed to show other days from D1-D90. Selecting only a single DayN will allow a split to be defined (for example D1 split by country). | Business |
| First transaction count | Count of transactions (IAP) being the first observed for a user (converting) reported daily. | Business |
| First transaction revenue | Sum of revenue from transactions (IAP) being the first observed for a user (converting) reported daily. | Business |
| Paying users | Count of unique users who sent at least one business (IAP) event. | Business |
| Revenue (IAP) | Sum of revenue for IAP transactions (business events). | Business |
| Transaction count | Count of IAP transactions (business events). | Business |
Error
| Name | Description | Event category |
|---|---|---|
| Critical error per session | Mean count of errors per unique sessions having critical severity. | Error |
| Critical error per session by build | Mean count of errors per unique sessions having critical severity reported by build. | Error |
| Critical error per user | Mean count of errors per unique sessions having critical severity. | Error |
| Critical error per user by builds | Mean count of critical errors per unique user sending error events reported by build. | Error |
| Error by type | Count of error events daily reported by severity type (info, debug, warning, error, critical). | Error |
| Error split by type | Count of error events daily split by the severity type (info, debug, warning, error, critical). | Error |
| Error users | Count of unique users who sent at least one error event | Error |
| Error users by type | Count of unique users who sent error events reported by severity type (info, debug, warning, error, critical). | Error |
| Errors by device | Count of error events reported by device-type. | Error |
| Errors per user | Mean amount of errors per unique user sending error events. | Error |
Ads
| Name | Description | Event category |
|---|---|---|
| Ads clicked | Count of ads (ad event) having the ad action equal to clicked. | Ad |
| Ads clicked per session | Mean count of ads (ad event) per session having the ad action equal to clicked. | Ad |
| Ads clicked per user | Mean count of ads (ad event) per session having the ad action equal to clicked. | Ad |
| Ads shown per session | Mean count of ads (ad event) per session (having ad events) with ad action equal to show. | Ad |
| Ads shown per user | Mean count of ads (ad event) per user (sending ad events) with ad action equal to show. | Ad |
| Total Ads display failed | Count of ads (ad event) with ad action equal to failed_show. | Ad |
| Total Ads shown | Count of ads (ad event) with ad action equal to show. | Ad |
Design (custom)
| Name | Description | Event category |
|---|---|---|
| Custom event count per session | Mean count of custom events (design events) per session (having design events). | Design |
| Custom event count per user | Mean count of custom events (design events) per user (sending design events). | Design |
Impression
| Name | Description | Event category |
|---|---|---|
| ILRD Count Per DAU | Count of ad impressions (ILRD) per active user reported daily. [This unique metric is legacy. Use the aggregation "Mean count per active user" instead for more flexibility] | Impression |
| ILRD Count by SDK Vendor | Count of ad impressions (ILRD) reported by SDK vendor (the mediation SDK provider). | Impression |
| ILRD Count by network name | Count of ad impressions (ILRD) reported by network name (ad network used by mediation SDK). | Impression |
| ILRD Revenue | Sum of revenue for ad impressions (ILRD). | Impression |
| ILRD Revenue by ad format | Sum of revenue for ad impressions (ILRD) reported by ad format. | Impression |
| ILRD Revenue by network name | Sum of revenue for ad impressions (ILRD) reported by network name (ad network used by mediation SDK). | Impression |
| ILRD Revenue by placement | Sum of revenue for ad impressions (ILRD) reported by placement. | Impression |
| ILRD Revenue per active user | Mean revenue (ILRD) per active user. The ILRD revenue sum divided by the active user count. | Impression |
| ILRD Revenue per impression | Mean revenue (ILRD) per impression event. | Impression |
| ILRD Revenue per user | Mean revenue (ILRD) per event user. The ILRD revenue sum divided by the count of users sending at least one impression event. | Impression |
| ILRD Revenue split by placement | Sum of revenue for ad impressions (ILRD) split by placement. | Impression |
Progression (levels)
| Name | Description | Event category |
|---|---|---|
| Level attempts started | Count of level attempts (progression event) with status equal to start. | Progression |
| Level attempts failed | Count of level attempts (progression event) with status equal to fail. | Progression |
| Level attempts completed | Count of level attempts (progression event) with status equal to complete. | Progression |
| Win percentage | Win percentage uses the progression event and report the percentage of all finished level attempts (status equal to complete or fail) being successful (status equal to complete). | Progression |
Resource
| Name | Description | Event category |
|---|---|---|
| Flow (sum) of Virtual Currency group by Currency | Flow uses the resource event to report a sum of sourcing currency (positive) and sinking currency (negative) showing the virtual economy balance. Reported by virtual currency used. | Resource |
| Flow (sum) of Virtual Currency split by Currency | Flow uses the resource event to report a sum of sourcing currency (positive) and sinking currency (negative) showing the virtual economy balance. Split by virtual currency used. | Resource |
| Virtual Currency Earn (source) split by Currency | Sum of amount from resource events with flow type equal to source. Split by virtual currency used. | Resource |
| Virtual Currency Spend (sink) split by Currency | Sum of amount from resource events with flow type equal to sink. Split by virtual currency used. | Resource |
Sessions (playtime)
| Name | Description | Event category |
|---|---|---|
| Session Count (started) | Count of sessions (session start event). | Session start |
| Cumulative Playtime per user | Cumulative playtime per user reports the mean total playtime per user since they installed. The metric is reported over days showing multiple lines for each DayN selected (N is the number of days after install). On a specific date the Day7 value will report the total playtime per user since install for users who installed 7 days ago. The default DayN selected is D1,D2,D3,D4,D5,D6,D7,D14. These can be changed to show other days from D1-D90. Selecting only a single DayN will allow a split to be defined (for example D1 split by country). | Session end |
| Playtime per session | Mean playtime (length) per unique session end event. | Session end |
| Playtime per user | Mean playtime (session end length) per unique user sending session end events. | Session end |
| Session Count (ended) | Count of session end events. | Session end |