Overview
|
The Game Dashboard provides insight into:
|
Each graph represents a different part of your game’s performance. The most useful insights come from comparing them together, not viewing them in isolation.
You access the Game Dashboard by going to the Developer Portal and tapping on one of your published games. The performance metrics are the data that take up most of the page.
If you get a "Failed to load data" message, try again in a short while, the data may be refreshing.
Important:
- Revenue numbers are estimates, not final payout
- Final numbers may differ after reconciliation (see these articles for more details How and when are developers paid? and Refund Reasons)
Top Summary Metrics
Lifetime Users | |
|---|---|
|
Definition: How to use it:
|
|
Insights:
- Flat growth → discovery problem
- Sudden spikes → figure out what these might be caused by. Examples include featuring on Kongregate main page, or update posts to your players
Lifetime Estimated Revenue | |
|---|---|
|
Definition: Includes:
|
|
Insights:
- The last ~60 day contribution to this total may alter - see 'Important' note at the top of this page
Average Rating | |
|---|---|
|
Definition: Why it matters:
|
|
Insights:
- 4★ – 5★ → strong player approval
- 3★ or below → players consider the game low quality
- Low or declining ratings suggest you need to make improvements to your game
- See your game reviews, check bug reports for the most obvious sources of player dissatisfaction
- Consider posting updates (from your game page) to keep players informed about new updates or known issues you're addressing
All-Time Ratings | |
|---|---|
|
Definition: How to read it:
|
|
Insights:
- Heavy 4★ – 5★ → strong player approval
- Heavy 1★ – 2★ → major issues (UX, bugs, expectations mismatch)
Monetization Graphs
Daily Kreds Revenue (USD – Estimate) | |
|---|---|
|
Definition: How to read it:
|
|
Insights:
- This revenue is based on in-game purchases
- May fluctuate due to:
- Player spending behavior
- Promotions or updates
- The last ~60 day contribution may alter - see 'Important' note at the top of this page
- You only see data here if your game uses Kongregate's Virtual Goods API
Average Revenue per Daily Active User (ARPDAU) | |
|---|---|
|
Definition: Why it matters:
|
|
Insights:
- High ARPDAU → strong monetization
- Low ARPDAU → players are not spending
- If DAU rises but ARPDAU drops → new users aren’t converting
Engagement Graphs
Daily Active Users (DAU) | |
|---|---|
|
Definition: Why it matters:
|
x - last 30 days, left → right y - players total/day |
Insights:
- Consistent growth → healthy game
- Sharp drops → retention or technical issues
New Users | |
|---|---|
|
Definition: Why it matters:
|
x - last 30 days, left → right y - new players total/day |
Insights:
- Only includes registered users (i.e. have a Kongregate account)
- Does NOT include guest players
- If your New User count is low, or zero:
- Most players are unregistered
- Low discovery of your game (consider adding more tags to your game, changing screenshots or game description)
- Tracking depends on account creation timing
Retention
Retention | |
|---|---|
|
Definition:
|
x - last 30 days, left → right y - % of cohort returning Blue - D1: % cohort returning after 1 day Green - D7: % cohort returning after 7 days Purple - D30: % cohort returning after 30 days |
Insights:
- Expect retention rates to drop after Day 1, then gradually taper down
Strong retention:
D1 > 30% → good onboarding
D7 > 10–15% → solid engagement
Weak retention:
- Low D1 → players don’t come back
- High abandonment suggests poor first-time user experience (FTUE), limiting revenue
- If retention stabilizes (e.g., around Day 30), it indicates a loyal and engaged user base
- A high retention rate with low revenue suggests the app is engaging but not well-monetized (need for IAP features), while low retention with high revenue might suggest a "pay-to-win" model that burns through users
- Retention is calculated only for New Users (registered Kongregate players)
This means it may not reflect your full player base as guest player behavior is excluded
Ratings Over Time
Daily Ratings | |
|---|---|
|
Definition: How to use it:
|
x - last 30 days, left → right y - number of reviews Colors - star ratings |
Insights:
- Sudden spike in 1★ → bug or bad update
- Increase in 4★–5★ → successful change
- No ratings → low engagement or visibility
Support
PAYMENT | How and when are developers paid?
Kongregate's Virtual Goods API
Quick Reference Guide - Where To Find What You're Looking For
Comments
0 comments
Please sign in to leave a comment.