What should I track in the first week after launch?
Track six things: net sales, wishlist conversion, refunds, reviews, crashes and returns. The first three come from Steam. Crashes and returns come from your game. Each one has a home in Steamworks or in Manalens.
| Metric | Where to read it | Question it answers |
|---|---|---|
| Units sold and returned, gross and net sales | Steamworks; or the Steam sync in Manalens (Early access) | How many copies did we sell, net of refunds? |
| Wishlist purchases and deletes | Steamworks; or the Steam sync (Early access) | Are wishlists turning into sales? |
| Purchases by link and creator | Steam UTM report; or its CSV import | Which posts and creators sold copies? |
| Review score, recent and lifetime | Your Steam store page and Steamworks | What do players say? |
| Crash-free sessions by build | Game health dashboard template | Is a build broken? |
| D1 and D7 retention, session length | Game KPIs dashboard template | Do players come back? |
Sources: Manalens Steam, metrics and error tracking documentation; Steamworks User Reviews documentation.
How do I read sales against wishlists?
Divide first-week units by the wishlists you had on launch day. GameDiscoverCo found a median of 0.15x for games that launched with more than 25,000 wishlists, and 0.10x for games priced above $10 at launch, in launches analyzed through August 2025. An earlier 2024 poll found 0.17x for launches with more than 10,000 wishlists.
The spread is wide. GameDiscoverCo says results vary by 10 to 20 times, not by 10 to 20%. So a ratio near the median is normal, and a ratio far from it tells you to look at price, timing and audience.
- Write down outstanding wishlists on launch day from Steamworks.
- Add units sold in the first 7 days. With a Financial API key (the automatic Steam sync is in early access), Manalens syncs units sold per day.
- Subtract units returned, so the number is net of refunds.
- Divide net units by launch wishlists, and compare with the median for your price band.
Sources: GameDiscoverCo (17 October 2025).
How do refunds change my numbers?
Steam accepts refund requests within two weeks of purchase and with less than two hours of playtime. So week-one units shrink for 14 days, and the last launch-day refunds arrive two weeks later. Read sales net of returns, and read them again after day 14.
For DLC, the window is 14 days, and the base game must have less than two hours of play since the DLC was bought. For Early Access, any playtime counts against the two hours.
The automatic Steam sync (in early access) in Manalens brings in units returned per day and country. It does not tell you which player refunded. The first two hours of play are still yours to measure: the first session funnel and session length show whether new players reach the part of the game that keeps them.
Sources: Steam Refunds policy; Manalens Steam documentation.
How do Steam reviews work after launch?
Steam shows two scores: one for the past 30 days and one for the lifetime of the product. Only reviews from accounts that bought the game on Steam and played it count toward the score. Key activations do not count, so reviews from press keys do not move the score.
Valve says a game that falls below 40% into Mostly Negative is less likely to be featured. Manalens does not import Steam reviews. Read them in Steamworks, and match complaints to builds: a wave of crash reports should line up with the crash-free sessions of one build.
Sources: Steamworks User Reviews documentation.
How do I catch crashes and bad builds?
Set a new build value for every patch, then read the Game health dashboard by build. It shows crash-free sessions, crash-free players, errored sessions, errors per session by build, and the top errors with the latest build that sent them.
The Godot and Unity SDKs send app_unclean_exit at the next launch after a crash, in the session and build that crashed. On Godot 4.5 and later, engine and script errors are sent as error events. Manalens does not store native crash dumps or symbols, so keep Sentry or Backtrace for stack traces.
To mark updates, send game_updated with previous_version and previous_build on the first launch after an update. It is part of the event conventions, and you send it from your own code.
Sources: Manalens error tracking, game health and app events documentation.
Which retention numbers matter after launch?
D1 and D7 in the first weeks, then D30. In the Game KPIs dashboard, DN retention is the share of players whose first game_open was N days earlier and who sent a session_start on that day. D30 needs a date range of at least 30 days.
Compare launch cohorts with later cohorts, and compare storefronts with the App filter. Audience insights mark a player At Risk after 14 or more days without activity, and Churned after more than 30 days. Most public retention benchmarks are for mobile games, so compare your own cohorts first.
Sources: Manalens metrics and audience insights documentation.
When do wishlist emails and the first discount go out?
At release, Steam sends an email or mobile notification to everyone with the game on their wishlist. Later, a discount triggers a wishlist email only if it is at least 20% off the lowest priced package and lasts more than 8 hours. Each app has a cooldown of about two weeks per user for these emails.
So plan the first discount with the cooldown in mind, and measure each one as its own event in your weekly table: units, wishlist purchases and first launches for that week.
Sources: Steamworks Wishlists documentation.
What does a weekly post-launch review look like?
One table, the same rows every week, and one decision at the end. Keep the review short, so you do it every week.
- Net units, wishlist purchases and wishlist deletes for the week.
- Units returned, and the refund share of units sold.
- Recent review score and the main complaints.
- Crash-free sessions and errors per session for each live build.
- D1 and D7 retention for the latest complete cohorts.
- Purchases by source and creator from the Steam UTM report.
- One fix or one marketing beat for next week.
Sources: Manalens dashboards documentation.
How do I build the post-launch table?
Manalens is the analytics and growth engine built for games. Connect a Steamworks Financial API key (the automatic Steam sync is in early access), import the Steam UTM report, and add the Unity or Godot SDK. Then sales, wishlists, crashes and retention fill one weekly table.
Sources: Manalens product documentation.
Frequently asked questions
How long should I wait before I judge launch sales?
Wait at least 14 days for refunds to settle. Steam accepts refund requests within two weeks of purchase with less than two hours of playtime. Read first-week units net of returns after day 14, and compare the ratio to launch wishlists with the GameDiscoverCo median for your price band.
What is a normal ratio of first-week sales to wishlists?
GameDiscoverCo found a median of 0.15x for launches with more than 25,000 wishlists, and 0.10x for games above $10, in launches analyzed through August 2025. Results vary by 10 to 20 times, so treat the median as a reference point, not a target.
Does Manalens import Steam reviews?
No. Read reviews in Steamworks and on your store page. Manalens syncs Steam wishlists and sales with a Financial API key (the automatic Steam sync is in early access), imports the UTM report, and receives game events, so you can match a wave of negative reviews with the crash-free sessions of one build.
Which build data should I send after launch?
Send a new build value with every patch, and send game_updated with previous_version and previous_build on the first launch after an update. Then filter the Game health and Game KPIs dashboards by build to see whether a patch reduced crashes or changed retention.