Este glosario define las métricas y la terminología utilizadas por el sistema Unity Analytics y la documentación.
El sistema Unity Analytics recopila o calcula las siguientes métricas y las muestra en los informes en las páginas Overview y Data Explorer del Tablero de Control de Analytics.
|
DAU (Daily Active Users) |
The number of different players who started a session on a given day. The Unity Analytics system anchors its days on Coordinated Universal Time (UTC), so the DAU figure counts players between 0:00 UTC and 24:00 UTC, no matter which timezone they are located in. A new session is counted when a player launches your game or brings a suspended game to the foreground after 30 minutes of inactivity. DAU includes both new and returning players. |
| DAU per MAU | (DAU/MAU) The percentage of monthly active users who play on a given day. Also known as Sticky Factor in the analytics and game industries, this metric is often used as one estimate of player engagement. Note that the metric includes both returning and new players. An influx of new players could mask the exit (churn) of existing players. In other words, a steady DAU per MAU metric doesn’t mean high player engagement if players are leaving your game just as fast as they join. Always examine retention metrics as well. |
|
MAU (Monthly Active Users) |
The number of players who started a session within the last 30 days. |
| New Users | Users who played your game for the first time. Unity records a persistent, randomized id value to the PlayerPrefs and uses the id to identify returning players. Note that if the PlayerPrefs file is cleared or deleted, then the player is counted as a new user the next time they launch the game. The PlayerPrefs file is deleted when a player uninstalls and then reinstalls your game (but not when updating). |
| Number of Users | The cumulative number of unique players over the last 90 days. Users who have not played in more than 90 days are removed from the count. |
| Percentage of Population | Your player population as a percentage. Typically only useful when combined with a segment. Calculated as the percentage of the Number of Users metric who are members of a specified segment. |
| Sessions per User | The average number of sessions per person playing on a given day. Also known as Average Number of Sessions per DAU. |
| Total Daily Playing Time | The cumulative playing time of all people playing on a given day. |
| Total Daily Playing Time per Active User | The average playing time of people playing on a given day. |
| Total Sessions Today | The total number of sessions by all people playing on a given day. Also known as Total Sessions. |
Unity Analytics calcula la retención utilizando el método conocido como N-Day Retention. Matemáticamente, N-Day Retention se calcula como el número de personas que juegan exactamente N días después de su primera sesión, dividido por el número de usuarios nuevos hace exactamente N días.
Las métricas estándar de retención calculadas por Unity Analytics incluye:
| Day 1 Retention | The percentage of players who returned to your game one day after playing the first time. |
| Day 7 Retention | The percentage of players who returned to your game seven days after playing the first time. |
| Day 30 Retention | The percentage of players who returned to your game thirty days after playing the first time. |
|
ARPDAU (Average Revenue Per Daily Active User) |
The average revenue per user who played on a given day. Revenue includes money earned from Unity Ads, verified Unity IAP transactions, and verified IAP transactions reported using the Analytics.Transaction() function. |
|
ARPPU (Average revenue Per Paying User) |
Average verified IAP revenue per user who completed a verified IAP transaction. |
| Number of Unverified Transactions | The total number of IAP transactions, whether or not they have been verified. IAP transactions include Unity IAP purchases and purchases reported using the Analytics.Transaction() function. |
| Number of Verified Transactions | IAP transactions that have been verified through the appropriate app store. IAP verification is currently supported by the Apple App Store and the Google Play Store. |
| Total IAP Revenue | The total IAP revenue, including revenue from both verified and unverified transactions. IAP transactions include Unity IAP purchases and purchases reported using the Analytics.Transaction() function. |
| Total Verified Revenue | Revenue from Unity Ads and verified IAP transactions. IAP verification is currently supported by the Apple App Store and the Google Play Store. |
| Unverified IAP Revenue | IAP revenue from sources that do not support verification and from transactions that failed verification. Transactions can fail verification because they are fraudulent or because of missing or malformed information. For example, if you haven’t configured your Google API key on the Analytics Dashboard, attempts to verify Google Play Store transactions will fail. See Receipt Verification. |
| Verified IAP Revenue | Revenue from verified IAP transactions. IAP verification is currently supported by the Apple App Store and the Google Play Store. |
| Verified Paying Users | Players who made verified IAP purchases. IAP verification is currently supported by the Apple App Store and the Google Play Store. |
|
Ad ARPU (Average Revenue Per User) |
Average Unity Ads revenue per player. |
| Ad Revenue | Total Unity Ads revenue. |
| Ad Starts | The number of video ads that started playing. |
| Ads per DAU | The number of ads started per active player on a given day. |
| eCPM | (estimated Cost Per Mille) The estimated revenue for 1000 ad impressions for your app. See What is ECPM. |
Para más información acerca de Ads, mire la Unity Ads Knowledge Base.
Los segmentos son subconjuntos de su base de jugadores, separados por diferenciadores clave, como país, plataforma, nivel de experiencia o patrones de gasto. Los segmentos se usan con las funciones Data Explorer, Funnel Analyzer y Remote Settings.
El servicio de Analytics proporciona un conjunto de segmentos estándar y ofrece la posibilidad de crear sus propios segmentos. Puede ver las reglas que definen los segmentos estándar y crear sus propios segmentos personalizados en la página Analytics Dashboard [Segment Builder]()
El ciclo de vida segmenta a los jugadores grupales por el número de días desde que jugaron por primera vez. El servicio define los siguientes grupos de ciclo de vida:
| 1–3 Days |
| 4–7 Days |
| 8–14 Days |
| 15–30 days |
| 31+ Days |
Nota: Los segmentos del ciclo de vida solo incluyen jugadores en los primeros 90 días de juego. En otras palabras, el segmento 31 + Días incluye a los jugadores que jugaron por primera vez hace más de 30 días y menos de 90 días.
Los segmentos geográficos agrupan jugadores por país. Los jugadores se geolocalizan utilizando técnicas como el análisis de IP. Los segmentos geográficos estándar incluyen los siguientes países:
| Australia |
| Canada |
| China |
| France |
| Germany |
| Japan |
| Russia |
| South Korea |
| Taiwan |
| United Kingdom |
| United States |
| Rest of World |
El segmento Resto del mundo incluye a todos los jugadores de países que no figuran en la lista individual. Tenga en cuenta que puede definir sus propios segmentos personalizados para grupos de jugadores por otros países individuales. (Sin embargo, esos jugadores también están incluidos en el segmento estándar Resto del mundo).
El segmento de monetización agrupa jugadores por qué tanto dinero gastan en compra dentro de la aplicación de su juego.
| Whales | Players who have spent at least $20 in their lifetime. |
| Dolphins | Players who have spent between $5 and $19.99. |
| Minnows | Players who have spent less than $5 in their lifetime. |
| Never Monetized | Players who have never spent real currency. |
| All Spenders | Players who had made any verified or unverified in-app purchases in their lifetime. |
La metáfora Whales, Dolphins, Minnows es una analogía de analítica común basada en la observación de que un pequeño número de usuarios tiene un impacto desproporcionadamente grande en el “ecosistema” monetario de un juego F2P típico.
Los segmentos demográficos agrupan jugadores según los datos demográficos informados por su juego:
| Males | Players reported as male. |
| Females | Players reported as female. |
| Unknown Gender | Players to whom you have assigned Gender.Unknown. (Players whose gender has not been reported at all are not included in this segment.) |
| Age 14 and Under | By default, Unity does not breakout analytics data for players under the age of 14. See COPPA Compliance. |
Unity no rastrea datos demográficos automáticamente. Para usar la segmentación demográfica, debe informar los datos utilizando las funciones Analytics.SetUserGender() y Analytics.SetUserBirthYear()
Mire User Attributes para más información.
La plataforma segmenta a los jugadores del grupo por la plataforma en la que están jugando. El sistema de analítica proporciona dos segmentos de plataforma estándar:
Usuarios Android
Usuarios iOS
Cree segmentos personalizados para obtener una segmentación más fina que la proporcionada por los segmentos estándar, así como para crear segmentos que combinen reglas de diferentes categorías de segmentos.
A diferencia de los segmentos estándar, una vez que un jugador se convierte en miembro de un segmento personalizado, el jugador siempre es miembro.
| Standard and Custom Events | Segment by whether a specific custom event has been dispatched while a user is playing. You can also specify restrictions on parameter values. |
| Sessions | Segment by when and how long a user played. |
| IAP revenue | Segment by IAP activity. |
| Demographics | Segment by reported demographics. |
| Geography | Segment by country. |
| Application version | Segment by application version or bundleid. |
Los nuevos segmentos se aplican solo a los datos nuevos. Los datos existentes no se vuelven a procesar utilizando las nuevas reglas de segmentación.
Mire Segment Builder para más información acerca de definir sus propios segmentos.
Los siguientes términos son utilizados por el Unity Analytics Service:
| Analytics Events | Events dispatched to the Analytics Service by instances of your applications. Analytics events contain the data that is processed and aggregated to provide insights into player behavior. |
| Cohort | A group of players with at least one similar characteristic. You can define and analyze different cohorts of your userbase with segments. |
| Core Events | Core events are the basic events dispatched by the Unity Analytics code in your game. These events, and the analytics based on them, become available simply by turning on Unity Analytics for a project. Core events include: app running, app start, and device info. |
| Standard Events | Standard events are application-specific events that you dispatch in response to important player actions or milestones. Standard events have standardized names and defined parameter lists. |
| Custom Events | Custom events are freeform events that you can dispatch when an appropriate standard event is not available. Custom events can have any name and up to ten parameters. Use standard events in preference to custom events where possible. |
| Funnel | A funnel is a linear sequence of standard or custom events that you expect a player to complete in order. Analysis of funnels can reveal those steps in the sequence where players encounter friction or problems. For example, a funnel based on level completion events would reveal whether larger than expected numbers of players stopped playing at specific levels. See Funnel Analyzer. |
| Heatmaps | Heatmaps are a spatial visualization of analytics data. The heatmap visualization displays markers for special analytics events overlaid on your scene in the Unity Editor.Heatmaps requires access to Raw Data Export, a pro-subscription feature. See Heatmaps. |
| Remote Settings | Remote settings are game variables that you can set remotely on your Analytics Dashboard. See Remote Settings. |
| Aggregated Data | As events are received by the Analytics Service, the data is processed and aggregated. The aggregated data is the basis of most of the Dashboard reports and visualizations. |
| Raw Data | The individual Analytics events sent by your application. Developers with Unity Pro subscriptions can download this data using Raw Data Export for analysis in external tools or other purposes. |
| Segment | Segments are subsets of your player base, split apart by key differentiators. Viewing metrics and events by segment can reveal differences in-game behavior between different groups. |
| Session | A single play or usage period. A new session is counted when a player launches your game or brings a suspended game to the foreground after 30 minutes of inactivity. |
Los siguientes términos en general son útiles para entender:
| Active Users | Players who recently played your game. Unity Analytics defines an active player as someone who has played within the last 90 calendar days. |
| Churn | The rate at which users are leaving your game during a specified period. Your user churn is important in estimating the lifetime value of your users. Mathematically, churn is the complement of retention (in other words: Churn + Retention = 100%). |
|
COPPA (Children’s Online Privacy Protection Act) |
COPPA is a US law that applies to apps that collect personal information and are targeted to children under the age of 14. See COPPA FAQ and COPPA Compliance |
| Conversion Rate | The percentage of users who complete an action or sequence of actions. For example, the conversion rate from one step of a funnel to the next is the percentage of players who make it through both steps, while the conversion rate of the funnel as a whole is the percentage of players starting the funnel who complete the entire sequence. The term conversion is also used in other contexts, such as starting and then completing a purchase, or watching an ad and then clicking on a link in the ad. |
|
CTR (Click Through Rate) |
The percentage of players who click a link in an ad displayed in your game. |
| Engagement | Engagement is a broad measure of how players enjoy, or are otherwise invested, in your game. Impossible to measure directly, the following metrics are frequently used to estimate engagement: Retention, DAU, MAU, DAU/MAU, number of sessions, and session length. |
| F2P | (Free to Play) A business model that offers users free access to a fully functional game and a significant portion of app content. Monetization strategies for these titles generally include microtransactions that allow users to access premium features and virtual goods. |
| Fill Rate | The rate at which ads are available when you request one. |
| IAP | (In-app Purchase) Revenue from “micro-transactions” within a game. |
| Impressions | The number of times ads are seen in your game. An impression is counted even if the ad is not completed. |
| LTV | (Lifetime Value) The estimated value of an average player over their lifetime with your application or game. |
| Sticky Factor | An estimate of how compelling a game is to its players. A high “sticky factor” means that players stick with an app over time. Unity Analytics uses a common calculation for Sticky Factor, which is the percentage of monthly active users who played on a particular day (DAU/MAU). Note that this definition can hide the exit of existing users with an influx of new users, so it should not be relied on as an indicator of the “health” of your game in isolation from your retention metrics. |