You shipped an update. Did it help?

After an update it's tempting to read the next day's numbers as the verdict. A fairer look compares the same number of complete days before and after, waits until those days are published, and remembers that other things change at the same time.

How to review an update fairly

Write down before you ship what you expect to change, and which numbers must not get worse.
Compare equal windows of complete days before and after (for example 3 and 7 days), skipping the update day itself.
Check that both windows have enough players to mean something.
Note anything else that happened at the same time. Before-and-after numbers can't prove the update caused a change.

Sample: an update on an invented mid-size game

Sample

Sample update "Sample update: new map" on Oct 11, 2026.
3 complete days before vs 3 after: daily players 449 → 483 (+7.5%).
7 complete days before vs 7 after: daily players 442 → 503 (+13.8%).
This shows what changed around the update, not why.

Invented sample data from the learning lab, not a real game or customer result.

Explore the full sample lab

What LaunchBlip shows you today

Update before-and-after reports (3 and 7 complete days) and a release notebook where you record what you expected and what you decided: Pro and Studio.
On every plan, compare two periods you pick, using complete days inside your plan's history.

Review your own updates

Free for one game. Update reports and the release notebook are on Pro and Studio.