How is a taxonomy different from a tracking plan?
A tracking plan says which events you send now. A taxonomy is the set of rules that every event follows, now and in two years. The plan is a list; the taxonomy is the grammar.
Without a taxonomy, each new event gets a name in a new style. After a year you have LevelComplete, level_completed and finishLevel in one project, and three charts that should be one. A short taxonomy written before launch prevents this.
Sources: Manalens app events documentation.
Which naming rules should I use?
Use the six rules below. They match the app event conventions, so the built-in boards read your events.
Event names can be up to 128 characters, and string property values up to 1,024. Stay far below both. Short names are easier to read in a chart legend.
- Write names in lower snake_case: level_complete, not LevelComplete.
- Put the noun first and the verb second: level_start, chapter_complete, settings_change. Related events then sort together.
- Use one tense. The conventions use the present form (level_complete, session_end), so keep it.
- Keep values out of names. Send boss_defeated with boss: "fire_lord", not boss_fire_lord_defeated.
- Keep properties flat: strings, numbers, booleans or null. Use the same property name for the same idea in every event, such as level or chapter.
- Never put personal data in a name or a property.
Sources: Manalens app events documentation and event schema.
How is this different from a free-to-play mobile taxonomy?
A free-to-play taxonomy is built around ads and an in-game economy. GameAnalytics lists eight event types: Ad, Business, Design, Error, Health, Impression, Progression and Resource. Two of the eight, Ad and Impression, exist for ad revenue. A paid PC game with no ads does not need them.
The economy also changes. Business events in a free-to-play game are in-app purchases, many per player. In a premium game, the first payment happens in the store before the game starts, so the in-game purchase event is only for DLC or a supporter pack. Track it, but do not build the plan around it.
Resource events (a currency source or sink) still help if your game has gold, crafting materials or upgrade points. Use the resource event with flow, currency, amount and item. If your game has no economy, leave the family out.
What premium games need more is progression detail and choices. Players paid once, so the main risk is that they stop before the end and leave a negative review. Chapter completion, difficulty choice and settings changes tell you more than ad views ever could.
Sources: GameAnalytics event tracking documentation; Manalens app events documentation.
Should I use colon IDs like Kill:Sword:Robot?
No. GameAnalytics design events use a hierarchy string of 1 to 5 segments joined by colons, such as Kill:Sword:Robot. The Manalens conventions follow the GameAnalytics event model without these colon-joined IDs.
Send one flat event with named properties instead: enemy_defeated with weapon: "sword" and enemy: "robot". Each property is then a filter and a breakdown on its own. You can count robot kills across all weapons without parsing a string.
C#
// Unity (C#): flat event, named properties
Manalens.Track("enemy_defeated", new Dictionary<string, object> { ["enemy"] = "robot", ["weapon"] = "sword", ["chapter"] = 2 });
Manalens.Track("settings_change", new Dictionary<string, object> { ["setting"] = "subtitles", ["value"] = "on" });Sources: GameAnalytics event tracking documentation; Manalens app events documentation.
Which properties should every event carry?
Most context is automatic. The SDKs put platform, storefront, app_version, build and engine in context.app on every event, and the collector adds the country. Do not repeat them as properties.
Add your own shared properties only when they help most events. Each one adds a filter to every report, and each one is a field you must keep correct in every build. For a story game, chapter is a good one. For a roguelike, run_id and run_number are good ones. Pick at most two or three, and send them on every event in the progression family.
Sources: Manalens app events and what we collect documentation.
How do I keep the taxonomy clean after launch?
Treat the taxonomy as code. Keep it in the repository, review new events in the same pull request as the code that sends them, and keep test data out of real reports.
- Turn the SDK off in the editor: enabled: not OS.has_feature("editor") in Godot, Enabled = !Application.isEditor in Unity. Use a separate test project and key for SDK tests.
- Never rename a live event. Add the new name, note the build where it starts, and filter old data by build.
- Check new events in the activity feed of a development build before the build goes out.
- Once a quarter, list events with almost no volume. Remove the ones that answer no question.
Sources: Manalens Godot SDK and app events documentation.
How do I start?
Manalens is the analytics and growth engine built for games. Write the six families into your plan, add the Unity or Godot SDK, and the Game KPIs board reads your progression events without setup.
Sources: Manalens product documentation.
Frequently asked questions
What is the best naming style for game events?
Lower snake_case with the noun first and the verb second, such as level_complete or chapter_start. Related events then sort together in lists and charts. Whatever style you choose, use it for every event, because two styles in one project split one metric into two.
Does a premium PC game need ad and impression events?
Not if it shows no ads. GameAnalytics lists Ad and Impression as two of its eight event types because many mobile games earn money from ads. A paid PC game earns its money in the store, so progression and quality events matter more.
Should I track purchases in a premium game?
Track DLC and supporter packs bought in the game with the purchase event, using amount_cents, currency and store. The first sale happens in the store, so read it from your store reports or the automatic Steam sync (in early access), not from an in-game event.
How many custom properties should an event have?
As few as answer the question, often two to four. Platform, build, version, storefront and country arrive automatically, so do not repeat them. Use the same property names across events, such as level and chapter, so that filters work everywhere.