Ad Monetization Uplift

Model how in-game KPIs compound into ad revenue

← Back to calculator

Why This Exists

Working at Unity and with game studios, I kept seeing the same pattern: teams pouring effort into waterfall optimisation to squeeze out marginal eCPM gains, while ignoring the game-side levers that actually move top-line revenue. View rate, impressions per session, retention — these compound in ways that a mediation dashboard never shows you.

Studios also underestimate nth impression dynamics. The instinct is to show more ads, but the returns diminish fast. Each subsequent ad in a session earns a lower CPM, fewer users watch it, and the churn risk climbs. Players who see the same number of impressions spread across sessions generate +21% more revenue — pacing matters.

When churn is high, the smarter play is to control ad frequency and bring players back tomorrow. In a world of rising CPIs and the shift from hyper-casual to hybrid-casual, LTV and long-term engagement are everything. ROAS is harder to achieve, so keeping players engaged session over session is no longer optional — it's the business model.

Who This Is For

Benchmarks are hard to come by. The relationship between game KPIs and ad revenue isn't explained anywhere comprehensive, and every studio ends up figuring it out independently.

This tool exists to give commercial context to the decisions game teams make every day. Why increasing view rate or IMPDAU often matters more than chasing higher CPMs. How fixing retention compounds into dramatically better Ad LTV. When showing fewer ads per session actually earns more money over time.

Whether you're a solo dev launching your first ad-supported game or a monetization lead building a case for your studio — the math should be transparent, testable, and shareable.

Built by Cathal O'Sullivan

This is the first project built and managed with PAPI Persistent Adaptive Planning Intelligence. PAPI is a sprint planning framework that gives AI assistants a persistent memory layer: sprint boards, build reports, active decisions, and cross-sprint learning. Every sprint builds on the last. No context lost between sessions.

The code itself is written with Claude Code— Anthropic's AI coding assistant. Every calculation is a pure TypeScript function with 70+ automated tests validating the math against real-world reference data. The AI writes the code. A human with domain expertise in ad monetization directs what to build, validates the outputs, and makes the product decisions.

The domain expertise is human. The velocity is AI. The planning layer is PAPI.

9 sprints

Sprints shipped

70+ tests

Test coverage

PAPI framework

Planning