What rules apply to event properties?
In Manalens, properties are a flat object. Values are strings of at most 1024 characters, numbers, booleans or null. A number property named revenue is special: reports sum it as event revenue.
Mixpanel describes the same model: events are like database tables, and properties are like their columns.
Sources: Manalens track event documentation; Mixpanel documentation: Events and properties.
What does an example look like?
Example numbers: in one week your game sends 400 level_complete events with level 1, 300 with level 2 and 120 with level 3. A breakdown by the level property shows the drop in one chart. With level_1_complete, level_2_complete and level_3_complete as separate names, you would need three event filters.
Sources: worked example.
Why do event properties matter for indie PC and web games?
A small game needs few events, and properties carry the detail. Level, attempt, score, difficulty and weapon all fit as properties. The build, version, platform, storefront and engine come in the app context of each game event, so you do not need to send them as properties.
Keep personal data out of properties. Do not put names, emails or free text in them unless you need it.
Sources: Manalens app events and track event documentation.
How do I use event properties in Manalens?
Report filters, alert filters and breakdowns read any event property as properties.<key>. The dashboard suggests the property keys that your project already sends. In SQL, read a property with JSONExtractString() or JSONExtractFloat().
Sources: Manalens alerts, server events and SQL explorer documentation.
Frequently asked questions
Can an event property hold a nested object?
No. In Manalens, properties are a flat object. Values are strings of at most 1024 characters, numbers, booleans or null. Flatten nested data into separate keys, such as level, attempt and score. Then filters, alerts and breakdowns can read each key as properties.<key>, and SQL can read it with JSONExtractString() or JSONExtractFloat().
What is the difference between an event property and a user property?
An event property describes one event at the time it happened, such as the level on level_complete. A user property, called a trait in Manalens, describes the player and keeps its latest value until a later identify call changes it.
Do I need to send the build and platform as properties?
No. Each game event carries an app context with the platform, storefront, app version, build and engine. So you do not need to send them as properties. Use properties for the detail that only your game knows, such as the level, the attempt, the score, the difficulty or the weapon that the player picked.