Game analytics: measure what this game's developer wants to know

Every game is different. A puzzle game cares about solve times and hints, a roguelite about how far runs get and which upgrades win, a mobile game about opens, modes, the paywall and purchases. Don't start from a template of "standard game events". Start from questions.

1. Get the questions

Ask the developer (or read the design doc, store page and code) for the five to ten things they'd check every week. Good questions name a decision:

• "Which mode do people actually play?" decides where to spend the next month.
• "Where do new players stop?" decides what to fix in the first ten minutes.
• "Does the tutorial help, or do people skip it and quit?"
• "Which level, stop or boss ends most runs?"
• "How many people who see the unlock screen buy, and where did they open it from?"
• "Did the last update make runs longer or shorter?"

2. Turn each question into events