The Answers Kit will automatically collect the most important data about the health of your app.
If you’re looking for a list of all the metrics, then you’ve come to the right place. When looking at your Answers dashboard, there are question marks for each metric that explain those particular metrics. The top level metrics will be listed first, followed by additional metrics that the Answers Kits collects for you automatically.
You can also set up additional data collection with Answers Events.
The number of users that have started a session in the last 5 minutes.
Daily Active Users:¶
The number of unique app installations across all devices that were active on a specific day. Note: Foreground activity must happen for a device to be active.
Daily New Users:¶
The number of new app installations across all devices on a given day. Deleting and reinstalling the app would create a new daily user. Updating versions of the app will not create a new daily user.
Monthly Active Users:¶
The number of unique app installations across all devices that were active over the trailing 30-day period. Note: Foreground activity must happen for a device to be active.
The percentage of daily active users that had a crash-free experience on a given day. Note: On Android or iOS, caught exceptions or logged errors are not considered crashes and are not included in this metric.
The total number of sessions across all app installations on a given day.
How is usage broken into sessions?
A session is measured as a pair of foreground and background events, as illustrated below. Answers only recognizes a session when a foreground event is followed by a background event.
What is not reported as a session?
Several things may cause Answers to discard events that might have led to a session. If an app rapidly transitions between foreground and background states, Answers will not report separate sessions for each period of time the app spent in the foreground if it spent less than 30 seconds in the intervening background states. Answers will only report two sessions if the time from backgrounding to foregrounding again is 30 seconds or more.
Also, if something occurs that prevents a background event from being detected, such as a crash or other abrupt termination of the process, Answers will not consider the prior foregrounding event as part of a session.
All builds that have been used by at least 10% of your Daily Active Users (DAU) on any single day in the past 30 days or at least 4% of DAU on the current day.
Daily Users for Top Builds:¶
The percentage and number of daily active users using a specific top build.
Daily Active Users by Device:¶
The number of daily active users using a specific device type.
Daily Active Users by OS:¶
The number of daily active users using a specific OS version.
New Users Over Active Users:¶
The percentage of daily active users that installed the app on a specific day.
The number of Daily Active Users divided by the Monthly Active Users on a specific day.
The percentage of unique users that were daily active users on a specific day, 1, 7, or 30, post-installation.
For example, D7 is the percentage of unique users that used the app on the 7th day after the install.
The percentage of sessions that did not experience a crash on a given day.
This is subtly different from the “Crash-Free Sessions” you see on the Crashlytics dashboard for the same time period. Answers groups sessions to count by the time they are submitted, and Crashlytics groups them by the time the events occur. If users experience crashes but wait sufficiently long to relaunch the app, the same crash could be calculated in different groups between Answers and Crashlytics, so these numbers may never exactly align.
Average Sessions per User:¶
The number of sessions divided by the number of daily active users.
Time in App per User:¶
A measure of how long the typical daily active user is active in the app on a specific day.
Median Session Length:¶
The median session length seen on a given day across all daily active users. A session is considered complete when the app has been sent to the background for more than 30 seconds.