Indicator definition
Indicator List¶
It's a list of indicators and indicator details provided in Indicator Creation. Indicators and their details are defined according to the indicator rules.
- Purchase Count
- The total sum of the quantity field from purchase logs generated through billing.
- Concurrent Users
- The count of unique playerId fields after duplicate removal from logs that record client connection information transmitted every 2 minutes via the SDK.
- Maximum Concurrent Users
- The maximum value of unique playerId fields after duplicate removal from logs that record client connection information transmitted every 2 minutes via the SDK.
- Minimum Concurrent Users
- The minimum value of unique playerId fields after duplicate removal from logs that record client connection information transmitted every 2 minutes via the SDK.
- Average Concurrent Users
- The average value of unique playerId fields after duplicate removal from logs that record client connection information transmitted every 2 minutes via the SDK.
- Login Count
- The total sum of the checkSum field from login logs generated through authentication.
- Daily Cumulative AU
- The count of unique playerId fields after duplicate removal from login logs generated through authentication between 12:00 AM and the specific hour.
- E.g.) The count at 3:00 AM represents the unique playerId count from 12:00 AM to 2:59 AM.
- In-app Revenue
- The total sum of the productPrice * quantity fields from purchase logs generated through billing.
- In-app Refund Count
- The total sum of the quantity field from refunded purchase logs generated through billing.
- In-app Refund Users
- The count of unique playerId fields after duplicate removal from refunded purchase logs generated through billing.
- In-app Refund Amount
- The total sum of the productPrice * quantity fields from refunded purchase logs generated through billing.
- Total Latency
- The total sum of the prevLatency field from logs that record client connection information transmitted every 2 minutes via the SDK.
- Average Latency
- The average of the prevLatency field from logs that record client connection information transmitted every 2 minutes via the SDK.
- Total Play Time
- The total sum of the activeTime field from logs that record client connection information transmitted every 2 minutes via the SDK.
- ARPU
- In-app Revenue / AU
- AU
- The count of unique playerId fields after duplicate removal from login logs generated through authentication.
- did AU
- The count of unique did fields after duplicate removal from login logs generated through authentication.
- did PU
- The count of unique did fields after duplicate removal from purchase logs generated through billing.
- did First Launch after App Install
- The count of unique did fields after duplicate removal from logs generated when the app is first launched and terms are agreed upon following app download.
- did App Update Users
- The count of unique did fields after duplicate removal from logs generated when the app is launched and terms are agreed upon following app update.
- did App Reinstall Users
- The count of unique did fields after duplicate removal from logs generated when the app is first launched and terms are agreed upon following app reinstall.
- did First Launch Count
- The total sum of the checkSum field from logs generated when the app is first launched and terms are agreed upon following app download.
- did In-app Refund Users
- The count of unique did fields after duplicate removal from refunded purchase logs generated through billing.
- NU
- The count of unique playerId fields after duplicate removal from login logs generated through authentication for new users.
- PU
- The count of unique playerId fields after duplicate removal from purchase logs generated through billing.
- sessionID Session Count
- The count of unique sessionId fields after duplicate removal from logs that record client connection information transmitted every 2 minutes via the SDK.
- ARPPU
- In-app Revenue / PU
- PU RATE (%)
- ( PU / AU ) * 100
- Purchase Count / PU
- Purchase Count / PU
- In-app Revenue / Purchase Count
- In-app Revenue / Purchase Count
- Stickiness
- Average AU / AU
- Ad Revenue
- The total sum of the revenueUsd field from ad revenue logs received from ad agencies.
- AD(x), adMob: Logs collected daily based on UTC.
- ADOP, Adiz: Logs collected daily based on KST.
- Total Revenue
- Ad Revenue + In-app Revenue
- NU to AU Ratio (%)
- ( NU / AU ) * 100
Indicator Rules¶
Indicator Naming Rules¶
- Indicator names are abbreviated versions of the indicator details to be displayed in analytics.
- Indicators are provided based on the playerId identifier by default. For other identifiers, the identifier is included in the indicator name.
- E.g.) If the AU indicator is based on playerId → AU
- E.g.) If the AU indicator is based on did → did AU
- If there is a generally accepted English term, it is used as is.
- E.g.) ARPU, Stickiness
- If there are no English terms, the indicator name is displayed in the respective language.
- E.g.) In-app Revenue
- When indicators are derived using a formula, they are displayed using relational notation.
- Common indicator terms are used where applicable.
- E.g.) Ad View Rate (%)
- For indicators calculated through division, the "/" symbol is used. If it's not a division but a percentage ratio, it’s labeled as "Denominator vs Numerator Ratio (%)".
- E.g.) Purchase Count / PU, AU to NU Ratio (%)
- Common indicator terms are used where applicable.
- When counting unique events, excluding the duplicated logs, the terms "event" and "case(s)" are used.
- E.g.) Purchase Cases
- For statistical measures, the specific measure is indicated at the end of the indicator name.
- E.g.) Average Latency
Indicator Details¶
- These are the details of the indicator, including dimensions, data sources, and calculations.
- Dimension: If a specific dimension is required to define the indicator, it is specified.
- E.g.) If the indicator is AU with newUser='Y', it is represented as newUser.
- Data Source: Defines the data aggregation used to process the indicator. You can refer to the log definition page for details about each log and field.
- Calculation: Defines the data source fields and operations used to calculate the indicator.
- Dimension: If a specific dimension is required to define the indicator, it is specified.
- If a new indicator is created through a formula between indicators, it is displayed as a relation.
- E.g.) In-app Revenue / Purchase Cases