What does an event contain?
Manalens builds every report from three event types. A page event is a page view. A track event is a named custom event, such as level_complete. An identify event links a player ID to a known user and sets traits.
Each event has a message_id. Reports remove duplicates by project and message_id, so a retry does not count twice. A track event name has 1 to 128 characters, and its properties are a flat object.
Sources: Manalens core concepts and track event documentation.
Which events does a game send by itself?
The Godot and Unity SDKs send game_open, session_start, session_end, app_unclean_exit and error without any code. You send the rest, such as level_start, level_complete, level_fail, resource and purchase. These names follow the GameAnalytics event model, as flat snake_case events.
Other tools work the same way. Unity Analytics records gameStarted at the start of a session, gameRunning every 60 seconds when no other event was recorded, and gameEnded when the player exits.
Sources: Manalens game events documentation; Unity documentation: Analytics standard events.
What does an example look like?
Example: a player launches your game, starts level 3, fails, tries again and completes it, then quits. That gives 7 events: game_open, session_start, level_start (attempt 1), level_fail, level_start (attempt 2), level_complete and session_end. The fail rate of level 3 for this player is 1 fail / 2 starts = 50%.
Sources: worked example; Manalens game events documentation.
Why do events matter for indie PC and web games?
Store reports show visits, wishlists and sales. They do not show which level players quit on or which build crashes. Your own events answer those questions.
Name events in snake_case and put variable values in properties. Send level_complete with a level property of 3, not level_3_complete. Then one event covers every level, and the reports stay short.
- What events to track first in your game →
- Event taxonomy for premium PC games →
- Game tracking plan generator →
Sources: Manalens track event documentation.
Frequently asked questions
How should I name game events?
Use snake_case names and keep variable values in properties. Send level_complete with a level property of 3, not level_3_complete. A track event name has 1 to 128 characters. The Godot and Unity SDKs already send game_open, session_start, session_end, app_unclean_exit and error for you.
Does a retried event count twice?
No. Each event has a message_id, and reports remove duplicates by project and message_id. So when a game sends the same batch again after a network error, each event counts once. This keeps launch, level and purchase counts correct, even for players on a weak connection whose game sends the same batch again.
What is the difference between page, track and identify events?
Manalens builds every report from these three event types. A page event is a page view on your website. A track event is a named custom event, such as level_complete, with optional properties. An identify event links a player ID to a known user and sets traits on that user.