For Android and iOS apps, Conviva DPI auto-collects conviva_application_error events and records the events as application crashes, due to segmentation faults, fatal exceptions, and other causes of native app crashes. These events contribute to application crash metrics, which for example, populate the App Crashes metric as the count of app crashes.
When an app crashes, the metric tracking varies depending on what happens within the next 30 seconds. If the app restarts, the session continues and the event is recorded in both the App Crashes and Crash → Restart metrics. If the app exits, the event is recorded in both the App Crashes and the Crash → Exit metrics.
If multiple app crashes occur within an app session, each crash event is counted in the App Crashes metric and the 30 second app restart behavior determines the whether an app restart or exit is counted.
The Conviva app crash metrics provide robust measurements of app crash conditions to prioritize user experiences and mobile performance impacts.
-
Monitor the user engagement impact of app crashes, distinguished by exits and restarts after crashes.
-
Assess the issue severity of app crashes, using frequency and affected time intervals.
| App Crash Metric | Definition | How to Use |
|---|---|---|
| App Crashes | Tracks application crash occurrences in native mobile applications. As a count, it shows the total number of crashes. | Monitor trends in crash counts and percentages to detect increases or decreases. |
| Crash -> Exit | Shows the percentage of sessions that become inactive within 30 seconds after an app crash. This metric measures the how often users end their sessions immediately following a crash, reflecting the extent to which the crash impacts the user experience. | Identify critical crashes that drive users to abandon the app. High exit rates signal severe user experience issues. |
| Crash -> Restart | Shows the percentage of app crashes followed by an app restart in less than 30 seconds. The metric is calculated as the number of app crashes where the user restarted the app in less than 30 seconds, divided by the number of Crash to App Startup Init events. | Gauge engagement impact and crash tolerance. High restart rates suggest users remain engaged despite crashes, indicating lower-level severity issues. |
| Mins with Crash | Shows the percentage of minutes with application crashes during the user's interval time. The metric is calculated as the number of minutes with application crashes during the user's interval time, divided by the number of active minutes. |
Assess crash severity by measuring how much active time is affected. High percentages indicate widespread impact. Set automatic AI alert notifications based on impacted active time. |
| Mins with Crash → Restart | The percentage of impacted minutes in app sessions with application crashes followed by an app restart in less than 30 seconds. The metric is calculated as the count of impacted minutes in app sessions where an application crash occurred and the user restarted the app in less than 30 seconds, divided by the count of active minutes. | Determine the engagement impact and urgency of app crashes. High impacted minutes indicate more critical issues. |
After ensuring the required the App Crashes metrics are selected in the metric selector, the metrics and related error events appear in the Trends App Crashes metric widget time series. Analyzing these metrics help identify fatal exceptions and resource constraints causing crashes. Additionally, select the App Crashes metric widget and use the dimension tables to isolate crash-related root causes, such as connection issues and under-resourced server processes.
Metrics for Crash -> Restart and Mins with Crash provide data for troubleshooting issues when the app restarted within 30 seconds. For more details, see DPI Metrics.
Note: Conviva DPI performs a best-attempt to detect and report app crashes before the app terminates. If not reported, Conviva DPI attempts to report the crash during the next app launch. In some cases, app crashes may not be reported, for example if Android terminates the app within its 20-second ANR (Application Not Responding) limit.
For iOS/Android apps, in the Trends Analysis tab select the App Crashes time series to access the related error messages and stack trace data.
App Crashes Crash Exit Crash Restart