Analytics

Analytics helps make informed decisions about game development. The Yandex Games Console has built-in tools for tracking key metrics: from player count and playtime to monetization revenue.

Data analysis allows you to:

• Track audience growth dynamics and identify factors affecting new player acquisition.
• Evaluate monetization effectiveness and find the balance between revenue and user experience.
• Identify technical issues that may reduce game launch conversion.
• Make informed decisions about game changes based on real data, not assumptions.

Analytics tools

Tool	Description	Purpose
Total income	Summary monetization information for all games.	Evaluate the overall financial performance of all projects and compare the profitability of different games.
Control panel	Key game metrics, alerts about important events, and charts showing player distribution by country and device.	Get an overview of the game's status and respond to critical changes in time.
Metrics	Statistics on product, financial, and technical metrics.	Analyze player behavior, evaluate gameplay quality, and compare metrics with category leaders.
Purchase metrics	Statistics on in-app purchases: revenue, paying players, popular items, and transactions.	Optimize pricing, identify popular items, and increase purchase conversion.
Reviews	User reviews about the game and your responses.	Learn player opinions, identify issues, communicate directly with the audience, and improve the game's reputation.

Yandex Metrica

Built-in metrics in the Developer Console work automatically and require no additional setup. They provide basic metrics for evaluating the game's status.

For more detailed analysis and custom reports, connect a Yandex Metrica counter. You will be able to:

• set up custom goals and events;
• build conversion funnels;
• analyze user behavior;
• create audience segments.

For more information about connecting and using Yandex Metrica, see the service documentation.

Experiment tools

Data-driven decision making is a good practice in game development. Use A/B testing tools to test hypotheses and evaluate the impact of changes.

For player acquisition

• A/B testing of icons — to increase conversion to game launch from the catalog, compare different icon and cover variants.

For game development

• Builds A/B tests — to evaluate the impact of major changes on metrics, compare different game builds on a portion of the audience.
• Experiments with flags — to test minor changes, use remote configuration without releasing a new version.

Working with charts

Metric charts in the Developer Console have a consistent interface:

• Metrics have tooltips with additional information.
• Filters are available for many charts. Use them to refine the data slice by device type, country, or period.
• Metrics of category leaders are available for comparison. Their display can be disabled.
• To download a table with metric values for each day of the selected period, click in the upper right corner of the chart.

Analytics best practices

• Regularly track key metrics. Pay attention to game rating, player retention, and game conversion.
• Respond to alerts. The control panel shows important notifications about declining metrics or game issues.
• Compare with competitors. Use category leader data to evaluate the growth potential of your metrics.
• Test hypotheses through experiments. Don't make changes blindly — use A/B tests to evaluate their effectiveness.
• Analyze metrics holistically. Growth in one metric may negatively affect others. For example, increasing the amount of advertising may increase revenue but reduce player retention.
• Consider seasonality. Player activity may vary depending on the day of the week, holidays, and other factors. The recommended minimum observation period is 7 days.