What sessions do, never who did it
Which events happen and how often, on which platform and in which country, and which events go with converting. All from five stored fields per event and only the properties you declare.
Free for one app and 20,000 events a month, no card needed. The demo runs on sample data, no signup.
Five stored fields
The API refuses unknown fields. A paid plan can add properties you declared, and nothing else.
event_name- what happened
session_id- a random ID from the app, hashed on the server with a salt that changes daily
timestamp- when it happened
platform- iOS, Android or another platform
country- looked up from the IP address, which is then discarded
Boosters and blockers
Pick your conversion events, and see which behaviour helps and which hurts.
Boosters
Events whose sessions convert more often than sessions without them. These experiences are working: promote them.
Blockers
Events whose sessions convert less often. Something there is causing people to leave: investigate.
Lift is the conversion rate of sessions with the event divided by the rate of sessions without it, minus one, as a percentage: +100% means twice as often. An event needs at least 10 sessions before it gets a score, and anything within 10% either way counts as neutral.
What teams use it for
Questions these fields can answer.
Feature adoption
Which features are used and which are ignored, and which go with converting.
Platform differences
Where iOS and Android behave differently, and where one of them has more friction.
Countries
Which markets send sessions, and how their behaviour differs.
Friction
Blockers point at the events that come before people give up.
Questions buyers ask
Straight answers to what teams ask before they choose.
What is stored for each event?
Five fields: the event name, a session ID, the timestamp, the platform and the country, plus on a paid plan any property you declared, with a value you declared. The API refuses unknown fields, and the IP address is discarded after the country lookup.
What are boosters and blockers?
Events whose sessions convert more often than sessions without them (boosters) or less often (blockers). An event needs at least 10 sessions before it gets a score.
Can I compare app versions?
Not by default. The app version is not one of the five stored fields. You can compare platforms, countries, session depth and the hour of day, and on a paid plan you can declare the app version as a property, with the versions listed, and compare by it.
Can I see returning users?
No. Sessions are never linked to each other, so there are no returning users, retention cohorts or lifetime values.
More of the dashboard
Every view works from the same five fields per event, plus the properties you declared on a paid plan.
Try it on your own app
Free for one app and 20,000 events a month, no card needed. Unlimited apps on every paid plan.