The short answer Track a small, planned set of events in six groups: sessions, the first-launch funnel, progression, economy, monetization and technical health. Write them in a tracking…

The short answer Track a small, planned set of events in six groups: sessions, the first-launch funnel, progression, economy, monetization and technical health. Write them in a tracking plan before coding, name them consistently and attach parameters. With about twenty well-chosen events you can calculate retention, find where players quit, balance the economy and see why revenue rises or falls. Start from questions Events exist to answer questions. Write the questions first. Where do new players drop out in the first ten minutes?

Which level is too hard? Are players running out of currency or sitting on piles of it? Which ad placement is used most? Do players who use a feature stay longer? Is the game stable on low-end phones? If an event answers none of your questions, do not add it.

The core event list Group Event Key parameters Session session_start, session_end Session number, duration Onboarding tutorial_step Step name or number, time since install first_level_complete Time since install Progression level_start Level, attempt number, character or loadout level_complete Level, duration, score, stars, boosters used level_fail Level, reason, progress percentage, attempt number Economy currency_earned Currency, amount, source currency_spent Currency, amount, item, sink Monetization shop_opened Entry point purchase_started, purchase_completed, purchase_failed Product, price, currency, failure reason Ads ad_opportunity, ad_shown, ad_completed, ad_reward_granted Placement, type, network Engagement feature_used Feature name daily_reward_claimed Day in streak notification_opened Notification type Technical loading_time Scene, seconds error Type, context Most analytics tools record installs, device model, country and app version automatically.

The first-launch funnel The steepest loss of players happens in the first session, so instrument it most carefully. Fire an event at each step: app opened, loading finished, each tutorial step, first action, first win, return to menu, second level started. View these as a funnel. A large drop between two steps points to a specific problem: a long load, a confusing instruction, a forced sign-up. Fixing the worst step is often the cheapest retention gain available.

See mobile game KPIs for what good retention looks like. Progression events Level start, complete and fail are the backbone for any level-based game. Completion rate per level shows difficulty spikes. Attempts per level shows frustration. Fail reason and progress show whether players lose at the start or one move from the end, which call for different fixes. Time per level helps content planning. Games without levels use equivalents: match start and end, quest accepted and completed, zone entered. See level design principles.

Source disclosure

This is a source-linked briefing. Read the original report from Dev Community .