Engagement measured in sessions, not people
How deep sessions go, how long they last, when they happen and how often they convert. The session ID lives in memory and is replaced every two hours and on each launch.
Free for one app and 20,000 events a month, no card needed. The demo runs on sample data, no signup.
What you can measure per session
Engagement within each visit to your app.
Session depth
How many events sessions have, from a single event to 21 and more.
Session length
The time between the first and last event, as an average per day.
Hour of day
When sessions start, and when the ones that convert start.
Conversion per session
The share of sessions that reach one of your conversion events.
How a session ID works
Random, in memory, and never linked to the next one.
- App launch
- The SDK creates a new random session ID in memory.
- In memory only
- It is never written to the device, so it is gone when the app closes.
- Every two hours
- The SDK replaces it with a new one while the app keeps running.
- On the server
- It is hashed with a salt that changes every day before it is stored.
What sessions give you
Engagement you can act on, with nothing about a person to keep.
Depth, length and hours. How many events a session holds, how long it lasts and when in the day it happens, for any range you pick.
Conversion per session. Which sessions reach your conversion events, and what the ones that do have in common.
No ID to store or protect. The session ID lives in memory and the server keeps only a salted hash of it, so no stored field names a user or a device.
Nothing on the phone. No identifier is written to the device for analytics, and every launch starts afresh.
Questions buyers ask
Straight answers to what teams ask before they choose.
What is session-based analytics?
It measures what happens within each visit to your app instead of following a person across visits. Each session has a random ID that the SDK replaces every two hours and on each launch, and Respectlytics stores no user ID or device ID that could link two sessions.
Can I measure retention without user tracking?
Not day 1, day 7 or day 30 retention: that needs a persistent ID, which is exactly what Respectlytics leaves out. You can measure how deep sessions go, how long they last and how often they convert.
What happens to the session ID on the server?
It is hashed with a salt that changes every day before it is stored, so the stored value cannot be matched to the ID the app sent.
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.