Which charts should a game dashboard show first?

Show the charts that answer one question each and lead to a decision. A chart that never changes what you do next is noise. For most indie games, eight charts cover the first months after a demo or a launch.

Each row below names the question, the chart and where it lives in Manalens. The Game KPIs, Game health and Channels and campaigns dashboard templates already hold these charts as SQL charts that you can edit.

ChartQuestion it answersWhere to find it
Install cohortsDo new players arrive, and do they stay?Game KPIs template
D1, D7 and D30 retentionDo new players come back on day 1, 7 and 30?Game KPIs template
DAU, MAU and stickinessHow large is the active base, and how often do players return?Game KPIs template
Session length and sessions per DAUHow long and how often do players play each day?Game KPIs template
Level funnel and levels tableWhere do players fail or stop?Game KPIs template
Crash-free sessions by buildDid the last build break the game?Game health template
Sessions by channel and UTM campaignWhich sources send visitors?Channels and campaigns template
ARPDAU and ARPPUDo in-game purchases earn money? (only with purchase events)Game KPIs template

Sources: Manalens dashboards and metrics documentation.

What do the core game metrics mean?

Each metric reads the events that the game sends. A player is one install, and only events from the game build count. The Godot and Unity SDKs send game_open, session_start and session_end for you, so most of these charts fill without extra code.

DAU is the average number of players active per day in the date range. MAU is the number of players active in the 30 days that end on the last day of the range. Stickiness is DAU divided by MAU. Day N retention is the share of players whose first game_open was N days earlier and who start a session on that day. So D30 needs a range of at least 30 days.

The levels table counts starts, completes and fails per level, and the fail rate is fails divided by completes plus fails. Crash-free sessions is 1 minus the share of sessions with an unclean exit or an unhandled critical error.

Sources: Manalens metrics documentation (Game section); Manalens game health guide.

What benchmarks can I compare my charts with?

Use public benchmarks only as a rough frame. The largest open set is mobile data from GameAnalytics, with 2024 data from 11,600 games on iOS and Android in 16 genres. PC and console games, and premium games in particular, can behave very differently.

The table copies only the figures that the report states in its text. Values in the report that we could read only from a chart are left out.

For PC and indie numbers, read our separate retention benchmark guide. For your own game, compare each new cohort with your earlier cohorts. That comparison is fairer than any benchmark, because the genre, price and audience stay the same.

MetricMedian (50%)Top 25%
D1 retentionNot stated in the text26.48% to 27.69%
D7 retention3.42% to 3.94%Not stated in the text
Session length5 to 6 minutes8 to 9 minutes
Sessions per day4Not stated in the text

Sources: GameAnalytics 2025 Mobile Gaming Benchmarks.

How do I read a retention chart without fooling myself?

Compare cohorts, not single numbers. A cohort is the group of players who started in the same day or week. If the cohort after a patch keeps more players on day 7 than the cohort before it, the patch probably helped.

  • Pick one retention type and keep it. Rolling retention counts a player who returns in that period or later, so it is always the same as or higher than recurring retention.
  • Ignore the last cells. Periods that are not complete at the end of the range show a dash, not a low number.
  • Read the drop from day 0 to day 1 first. A large drop often points to the first session, so check the level funnel next.
  • Watch cohort size. A cohort of 40 players moves by 2.5 points for each player, so wait for larger cohorts before you decide (our arithmetic).
  • Split by source. A cohort from a large creator video can retain very differently from a cohort from a Steam sale.

Sources: Manalens retention documentation.

Which marketing charts belong on the same dashboard?

Put sessions by channel and a UTM campaign table next to the player charts. Then you can see whether a campaign brought players who stayed, not only visits. The Channels and campaigns template credits each session to the channel and UTM fields of its first page view.

Steam keeps its own traffic report. It shows impressions, visits and the click-through rate from impressions to store page visits, by source. Steam notes that an impression does not mean the player saw the game. Its impression and visit reports start on 23 March 2021 and exclude users who opted out of the applicable cookies.

Do not copy Steam numbers into a chart by hand every day. Import the Steam UTM report instead, and read Steam wishlists by source on Overview. For installs by channel, use the Installs tab on the Attribution page.

Sources: Steamworks Store and Platform Traffic Reporting documentation; Manalens dashboards, Steam and install attribution documentation.

How do I build the dashboard in Manalens?

Start from a template, then add only the charts that answer a question the template does not.

  1. Open Dashboards in the left navigation.
  2. Under Templates, click Game KPIs. The preview shows your data for the last 30 days. Click Create board.
  3. Repeat for Game health, so crash-free sessions and top errors sit on their own board.
  4. Click Add chart and choose Retention. Set the period to Daily to see days 0 to 30.
  5. For a single number, add a SQL chart of type Number and set the Number format to .1% for a rate.
  6. Give a chart its own range with the date picker in its header, for example to compare the week after a patch.
  7. Send the page URL to your team. Viewers can see the dashboard but cannot change it.

Sources: Manalens dashboards and custom dashboard documentation.

Which charts can I skip?

Skip charts that only go up or that no decision depends on. This is our advice, not a rule from a study. A cumulative installs chart always rises, so it hides a bad week. Total events mostly measures how much your code sends. Page views by browser rarely changes what a game team does.

Keep a chart when you can name the action that a change in it would trigger. If D1 falls after a build, you check the first session. If crash-free sessions fall, you roll back or patch. If a campaign brings visits but no installs, you change the campaign.

Sources: Manalens metrics documentation.

Where do I start?

Manalens is the analytics and growth engine built for games. Open Dashboards, preview the Game KPIs template with your last 30 days of data and click Create board. Then compare D1 and D7 by cohort with the retention calculator.

Sources: Manalens product documentation.

Frequently asked questions

What is the most important chart for an indie game?

Retention by cohort. It shows whether new players come back on day 1 and day 7, and whether that improves after each patch. Traffic and wishlist charts show interest. Retention shows whether the game keeps the players that interest brings, which drives reviews and word of mouth.

What is a good stickiness (DAU / MAU) for a game?

There is no reliable public benchmark for PC indie games, so compare your own weeks. Stickiness is DAU divided by MAU. A rise means players return on more days of the month. A premium story game can have low stickiness and still sell well, so read it with retention.

Do I need SQL to build a game dashboard?

No. The Game KPIs, Game health and Channels and campaigns templates create the main charts for you, and retention, funnel and user path charts have settings instead of queries. SQL charts are there when you want a custom number, and every template chart opens in the editor.

How often should I look at the dashboard?

Check crash-free sessions after each build, and the rest once a week. Daily numbers for a small game move a lot by chance. A weekly review with cohort retention, active players and installs by source shows real changes and keeps the team focused on decisions.

Sources and implementation