TRACK THE DATA THAT HELPS YOU DECIDE
Know what to track before the dashboard fills with noise.
A telemetry plan that tells developers which events to send, what each event needs, how the KPIs are calculated, and how to test the setup.
WHEN IT FITS
Use this when the next decision needs to be clearer.
- The game has little or no useful data yet.
- The current dashboard shows a drop but cannot explain what the player did before it.
- Teams disagree about how a KPI is calculated or which event should answer a product question.
WHAT WE AUDIT OR DESIGN
The work stays tied to the decision.
- The product questions the data must answer and the decisions the team expects to make.
- Player actions, game states, level outcomes, rewards, offers, economy movements, and failure reasons.
- Existing events, missing context, naming conflicts, KPI definitions, and QA gaps.
WHAT YOU RECEIVE
Your team gets clear instructions.
- Event names with exact trigger rules.
- Required properties, allowed values, and player or session context.
- KPI formulas and plain-language definitions.
- A developer handoff and QA checklist with test cases.
What we need from you
A game build or product flow, the decisions you want the data to support, and any existing event list, dashboard, schema, or sample export.
How the work is measured
The specification includes QA checks for duplicate events, missing properties, invalid values, ordering, retries, and state transitions. Every KPI is tied to the events needed to calculate it.
RELEVANT WORK
See what this looks like on a real game.
QUESTIONS BEFORE STARTING
What teams usually ask.
Can you work with the analytics tool we already use?
Yes. The event and KPI specification is written around the game and its decisions. It can then be mapped to the analytics stack your developers use.
Do you decide which data is useful?
Yes. We start with the questions the team needs to answer, then define the smallest event set that answers them properly.
Will developers know when each event fires?
Yes. Each event includes its trigger, properties, valid values, and the QA checks needed before release.