Stop Believing Benchmark Metrics for Your Game
summary
Common benchmarks like 40/20/10 retention mislead because retention definitions vary wildly and genre matters; use installs, ARPU and real retention curves to model revenue instead. Example math: 5¢ ARPU → $0.61 LTV (180d) versus 15¢ ARPU → $1.45 LTV (180d), and a played-out case where poor retention (day1 4%, day7 7%, day30 3%) still scales because organic volume hits 25,000 installs/day → $140k/mo, later growing to 200,000/day. Calculate daily revenue from installs × ARPU × retained days.
AI-written summary · about
chapters (7)
- 0:00Benchmark misconceptions
- 1:09Why retention benchmarks fail
- 3:59Retention and ARPDAU misleading
- 6:09Define your game's success
- 8:17Key metrics beyond benchmarks
- 10:05Lockwood Games case study
- 12:56Conclusion
related talks
18mLifetime value forecast – How to predict your game's revenue
19mHyper-casual math
26mMonetizing your games as a service
07m20 words no one in the mobile games industry should use
21m80% data, 20% luck – How to make profitable games in 2019
03mPaying Customer, not Necessarily a Retained Customer in Freemium Games
49mMonetisation Design - A Story of Love and Retention
37mHypercasual monetisation versus long-term retention monetisation