Launch stages and KPIs
På denne side
Launch stages and KPIs
Every game follows the same path. Knowing what each stage is for tells you what to build next.
| Stage | Ads and revenue | Purpose | How you leave it |
|---|---|---|---|
| Draft | None | Private to your team. Build, upload, fill in the listing. | You submit. |
| QA | None | A reviewer plays the build against the requirements. | Approved, changes requested or rejected. |
| Basic launch | Ads off, no revenue | Measure whether players like the game. | After 7 days and 500 plays, or automatically after 21 days, a reviewer promotes, extends or ends it. |
| Full QA | Ads off until it passes | A second review of the full SDK integration. | Approved for full launch, or changes requested. |
| Full launch | Ads on, revenue share accrues | Growth, artwork experiments, updates. | Ongoing. |
The console always shows the current stage on the game's launch card.
KPIs during basic launch#
Four numbers are measured automatically. No SDK call is needed, although gameplayStart makes play time more precise.
| KPI | Target for full marks | Weight |
|---|---|---|
| Average play time per session | 10 minutes or more | 30 % |
| Day-1 retention | 15 % or more | 30 % |
| Conversion (views that last at least a minute) | 80 % or more | 20 % |
| Click-through rate (tile seen to game opened, versus your category) | 50th percentile or better | 20 % |
The portal combines them into a score and gives the reviewer a recommendation. It is advice, not a decision. The details, partial credit and tips for each number are on basic launch metrics explained.
What changes at full launch#
- Midgame and rewarded ads and banners switch on, served only through the SDK. See advertisement rules.
- The SDK integration becomes required:
gameplayStartandgameplayStop, ads at natural breaks, and the data, user and leaderboard modules where they apply. - Two preview videos are needed in addition to the three covers.
- Updates wait for a reviewer. See updating a live game.
- Your studio earns its revenue share and receives monthly statements. See revenue share and payouts.
KPIs to watch after full launch#
The developer console shows revenue and traffic by day, game and country. These are the numbers that usually decide whether a game grows:
| Number | Why it matters |
|---|---|
| Plays and unique players | Reach. Driven by cover, title and category. |
| Average play time and retention | Whether players come back. |
| Ad impressions per session | Whether your ad breaks fit natural pauses. |
| Revenue per thousand plays | Combined effect of players, geography, devices and ad pacing. |
Compare against games in your own category and split by device. Use artwork experiments to lift click-through and the monetisation guide to tune ad pacing.
Preparing early#
You can do the full-launch work while basic launch runs: add gameplayStop, ad breaks, cloud save and the second video. The requirements checklist lists everything in one place.