Game Economy Analytics and KPIs: Measuring What Matters

Revenue Metrics

ARPDAU (Average Revenue Per Daily Active User) is the most commonly tracked revenue metric in free-to-play games. It measures the total daily revenue divided by the number of daily active users. For ad-supported web games, a healthy ARPDAU ranges from $0.01 to $0.05. For games with in-app purchases, $0.05 to $0.30 is typical, with top-performing titles reaching $0.50 or higher. ARPDAU trending upward means your economy is converting engagement into revenue more efficiently. ARPDAU trending downward means either fewer players are spending, spenders are spending less, or your user base is growing faster than revenue (which is not necessarily bad if retention is healthy).

ARPPU (Average Revenue Per Paying User) isolates the spending behavior of players who actually make purchases. A game with ARPDAU of $0.10 and a 3% conversion rate has an ARPPU of roughly $3.33 per paying user per day. ARPPU is the metric that reveals whether your pricing is right: if ARPPU is low but conversion rate is high, your prices may be too low. If ARPPU is high but conversion rate is low, you may be extracting too much from a small group while failing to offer value that appeals to moderate spenders. The ideal is a balanced distribution where moderate spenders contribute meaningful revenue alongside the high spenders.

LTV (Lifetime Value) predicts how much total revenue a player will generate over their entire relationship with the game. LTV is calculated by multiplying ARPDAU by the average player lifespan in days. A player with ARPDAU of $0.05 and an average lifespan of 60 days has an LTV of $3.00. LTV determines how much you can afford to spend acquiring each new player (CAC, Customer Acquisition Cost) while remaining profitable. If LTV is $3.00, spending $4.00 per player on marketing is unsustainable. If LTV is $10.00, spending $4.00 per player is profitable. Economy design directly impacts LTV because a well-balanced economy increases both the spending rate and the player lifespan.

First purchase conversion rate measures what percentage of new players make their first purchase, and when. This metric is critical because the first purchase is the hardest to get, and once a player has spent money, the psychological barrier to subsequent purchases drops dramatically. Track the percentage of players who make a first purchase within 1 day, 7 days, 14 days, and 30 days. If the 7-day conversion rate is 1% but the 30-day rate is 4%, your economy is working but the initial offer is not compelling enough. If the 7-day rate is 3% and the 30-day rate is 3.5%, your economy front-loads conversion well but fails to capture late-deciders. Starter packs priced at $0.99 to $2.99 with extremely high perceived value are the standard tool for boosting first-purchase conversion.

Currency Flow Metrics

Daily currency generation is the total amount of each currency created across all players in a single day. Track this for every currency in your game: soft currency, hard currency, event currencies, seasonal currencies. This number should be roughly stable day-to-day (adjusted for daily active user count) if your sources are functioning as designed. A sudden spike in currency generation indicates either an exploit, a bug, or a new content release that generates more currency than intended. A sudden drop indicates that a source is broken, that content is being played less than expected, or that your player base is declining.

Daily currency destruction is the mirror metric: the total amount of each currency removed from circulation through sinks. Compare this to daily generation. The difference, net daily flow, tells you whether the economy is inflating (positive net flow, more created than destroyed) or deflating (negative net flow, more destroyed than created). Persistent positive net flow means your sinks are insufficient and the economy is accumulating excess currency that will eventually devalue everything. Persistent negative net flow means your sinks are too aggressive and players may be feeling resource-starved.

Reserve distribution shows how much currency players hold at each progression stage. Plot a histogram of currency holdings across your player base. A healthy distribution looks roughly normal, clustered around the amount that players at the median progression stage should have, with tails extending toward wealthy veterans and new players. An unhealthy distribution is bimodal: a large group of players with almost nothing and a small group with enormous reserves. This bimodal distribution signals an economy that is failing its middle class, the players who are engaged enough to have been playing for a while but not hardcore enough to have mastered the earning systems.

Velocity of currency measures how quickly currency moves through the economy. High velocity means currency is earned and spent quickly, indicating an active economy with compelling sinks. Low velocity means currency sits in player accounts unused, indicating either insufficient sinks, overpriced items, or a player base that is hoarding for a future they are unsure about. In multiplayer games with player-to-player trading, velocity can be measured directly as transaction volume. In single-player economies, velocity is approximated by the ratio of daily spending to average reserves.

Progression and Retention Metrics

Milestone timing tracks how many sessions or days it takes the median player to reach key progression milestones: first level-up, level 10, level 20, first major purchase, access to endgame content. Compare actual milestone timing to your economy model's predictions. If the model predicted that the median player would reach level 10 at session 8 but actual data shows session 12, the earning rate is slower than modeled, which means either sources are under-delivering or players are engaging with fewer sources than expected. If the model predicted session 8 and actual data shows session 5, the economy is faster than intended and mid-game content may be trivialized.

Progression dropout rate identifies where in the progression players quit. If 40% of players who reach level 5 quit before level 6, there is a progression wall at level 5 that either costs too much, offers too little reward, or introduces too much friction. Economic walls (the next upgrade is too expensive given the earning rate at that level) are a leading cause of mid-game dropout. The fix is adjusting the cost of the wall item, increasing the earning rate at that stage, or adding a more affordable alternative that provides partial progress and maintains the earning motivation.

Day-1, Day-7, and Day-30 retention are the industry-standard metrics for measuring how many players return after their initial session. For web games, healthy benchmarks are roughly 40% Day-1 retention, 15-20% Day-7 retention, and 5-10% Day-30 retention. Economy design directly impacts these numbers: a game that delivers a reward in the first session and creates a clear reason to return ("your crops will be ready tomorrow," "your daily bonus resets at midnight," "your new weapon will be unlocked after one more session") has measurably higher retention than a game with identical mechanics but no economic hook for return visits.

Engagement and Spending Segmentation

Segmenting your player base by spending behavior reveals patterns that aggregate metrics hide. The standard segments are non-payers (never made a purchase), minnows (spent less than $10 lifetime), dolphins (spent $10 to $100 lifetime), and whales (spent over $100 lifetime). Track each segment's size, retention, session frequency, and average session length. In a healthy economy, non-payers have strong retention (they enjoy the game enough to play without spending), minnows have the highest session frequency (they are engaged enough to spend a little and may convert to dolphins), and whales have the longest session length (they are deeply invested).

Warning signs in segment data include: whale concentration (if the top 20 players generate 80% of revenue, losing any one of them represents a material financial risk), minnow churn (if players who make a first purchase stop playing shortly after, the initial purchase is not leading to a satisfying experience), and non-payer exodus (if free players are leaving rapidly, the game may be too aggressively pushing monetization, which degrades the free experience and eventually collapses the community that makes the game worth paying for).

Cohort analysis, tracking groups of players who started at the same time, reveals how the economy affects player lifecycle. A cohort of players who joined during a generous promotional event will have different spending and progression patterns than a cohort who joined during normal conditions. Comparing cohorts tells you whether economy changes are improving or degrading the player experience over time. If more recent cohorts have lower retention and lower conversion than older cohorts, something in the economy has gotten worse, and the cohort data points you toward exactly when the degradation began.

Analytics Tools for Game Economies

GameAnalytics is the most widely used free analytics platform for indie and mid-tier games. It provides built-in support for tracking economy events (resource earned, resource spent), progression events (level reached, milestone achieved), and business events (purchase completed). The free tier supports up to 100,000 monthly active users, which covers most web games. The platform includes pre-built dashboards for retention, revenue, and progression, with the ability to create custom dashboards for economy-specific metrics.

Unity Analytics integrates directly with Unity-built games and provides economy-specific tracking through custom events. For games built with other engines or frameworks, Unity Analytics is less convenient but still usable through the REST API. The platform excels at funnel analysis, showing exactly where players drop off in multi-step economic processes (open shop, browse items, select item, confirm purchase, complete purchase).

For web games built with JavaScript, a lightweight custom analytics approach using a simple event logging API is often sufficient. Each economy event (currency earned, currency spent, item acquired, level reached) sends a JSON payload to your server with the player ID, event type, amount, context, and timestamp. Store these events in a database (PostgreSQL, DynamoDB, or even a flat file for small games) and query them with SQL or a simple dashboard tool. This approach gives you full control over your data and avoids the vendor lock-in of third-party platforms, though it requires building the dashboard and analysis tools yourself.

Mixpanel and Amplitude are general-purpose analytics platforms that work well for game economies when configured with custom events. Both support funnel analysis, cohort analysis, A/B test analysis, and user segmentation. Their advantage over game-specific platforms is flexibility: you can track any event and build any analysis without being constrained by the platform's assumptions about what a "game" looks like. Their disadvantage is cost at scale, both charge based on event volume, and a popular game with economy tracking can generate millions of events per month.

Building Your Economy Dashboard

A minimum viable economy dashboard tracks five numbers updated daily: ARPDAU (is the economy generating revenue?), net currency flow (is the economy inflating or deflating?), first-purchase conversion rate (is the economy converting players?), median time to first progression milestone (is the economy pacing correctly?), and Day-7 retention (is the economy keeping players?). These five metrics, displayed as daily trend lines over the past 30 to 90 days, give you an at-a-glance health check that catches problems before they become crises.

Add drill-down capabilities for when the top-line numbers look wrong. If ARPDAU drops, drill into spending by segment (did whales stop spending, or did the conversion rate drop?). If net currency flow spikes positive, drill into source-by-source generation to identify which source over-produced. If Day-7 retention drops, drill into progression dropout to identify the specific level or milestone where players are leaving. Each drill-down should answer "why" and point to a specific parameter that can be adjusted.

Set automated alerts for threshold breaches: ARPDAU drops below a minimum, net currency flow exceeds a maximum, conversion rate drops by more than a standard deviation, or any individual currency source generates more than 2x its historical average. These alerts let you respond to problems within hours rather than discovering them in a weekly review meeting when the damage has already compounded for days.