← All insights
Acquisitions
The Difference Between a Dead Game and a Sleeping Game
Low CCU has many causes. Only some of them mean the game is finished.
A low concurrent count looks the same whether a game is finished or merely quiet. The difference matters because one deserves a decision to move on and the other deserves a plan. Look at why the numbers are low, not only that they are.
Possible causes of a low count
- Temporary dip
- A short fall after an event ended, a holiday, or an outage. It often recovers without action.
- Seasonal demand
- Some games follow the calendar, such as school terms or seasonal themes.
- Broken acquisition
- Few new players arrive because the thumbnail, icon or discovery has weakened or traffic stopped.
- Poor retention
- Players arrive and leave. The game cannot hold anyone.
- Outdated content
- The game once worked and no longer meets expectations.
- Dormant community
- Former players are still around but have no reason to log in.
- Update-driven spikes
- The count only rises when something new ships, then falls back.
How to read the history
- Plot a long window and mark each update, event and change in traffic.
- Check whether the low is a slow decline or a sudden step. A step usually has a cause you can name.
- Compare the same period in earlier years if the game is old enough.
- Separate new-player arrivals from returning-player activity.
What each pattern suggests
| Pattern | Reading | Possible next step |
|---|---|---|
| Sudden drop after a change | A specific cause, possibly reversible | Find the change and test reverting it |
| Slow steady decline | Aging content or a shrinking audience | Check retention and content gaps |
| Regular peaks and troughs on a calendar | Seasonality | Plan around it, do not over-react |
| Spikes on updates, flat otherwise | Players come for new content only | Build reasons to stay between updates |
| Few new players, decent retention | Acquisition problem | Test creative, targeting, discovery |
| Many new players, poor retention | Game problem | Fix the first sessions |
Signs of recoverable potential
- Retention for new players is reasonable even now.
- Players who stayed show healthy long-term behaviour.
- There is a known cause of the decline that can be addressed.
- The technical base is workable.
- A community or group of past players still exists.
- The core idea still appeals, which you can test by watching new players.
Signs it may be finished
- Retention is poor and no clear cause exists.
- The core loop no longer appeals, and the audience has moved on.
- The code is so fragile that each change risks breaking it.
- The costs of fixing the game exceed any plausible return.
Test before deciding
Run a small, controlled test: a modest traffic sample aimed at the first-session experience, with funnel logging on. If new players behave well, the game is probably asleep. If they leave quickly, the sleep is not the problem.
For deeper evaluation, see Don’t Relaunch a Dead Roblox Game Until You Know Why It Died.