Error Summaries utilise generative AI to translate Errors into clear, plain language, giving you instant insight into occurring errors, how to qualify and how to reproduce them, the affected users, and the overall impact on your mobile app traffic.
Leverage these summaries to prioritize critical fixes and seamlessly share context with your engineering team.
Before you start
To use Error Summaries, make sure 'Error Analysis' is available and your account meets the requirements for Contentsquare AI features. No additional SDK configuration is required for 'Error Summaries'.
What an Error Summary includes
An 'Error Summary' is a plain-language text describing the main issue, an overview of the impact caused by the error, giving a comparative breakdown of the error’s occurrence and impact, and the steps to reproduce the path users followed before the error occurred.
For mobile SDK projects, the comparative breakdown can include the App version, OS version, device type, and compare metrics such as sessions with error impact on goal, missed opportunity …
For a refresh about the key indicators, please refer to this article: Error Analysis (Apps) - Key Performance Indicators.
Data collection
The availability of app version, operating system, network type, device type, country, language, and other mobile dimensions depends on the data collected for your project and analysis context.
Using the Error Summary
Generate the summary
- Open ‘Error Analysis’ for a mobile SDK project.
- Select the error that you want to investigate. Please select an error with enough data to generate a summary.
- Open the error details.
- Click the ‘Error Summary’ button to generate or view the summary.
- Review the title, overview, comparative breakdown, and steps to reproduce (details are below).
Review the summary
Start with the title and overview to understand the main issue and its source. Then use the comparative breakdown to identify where the error occurs most often and which users or business outcomes are most affected.
Use these comparisons to prioritize investigation and give your engineering team more context.
For a detailed explanation about how to analyze the error information, see How to analyze and share error information – Mobile.
Use the steps to reproduce
The Steps to reproduce section shows the typical path users followed before the error occurred. Use these steps to understand the user journey and identify where the experience began to fail.
Note that these steps represent typical user behavior and may not reproduce the error every time. They are intended to help you investigate the issue and reduce the time needed to understand what happened.
If no related Session Replay data is available, the Steps to reproduce section does not appear.
Share the summary with your dev team
Use the 'Copy summary' feature to share the error summary with your teams:
- Click on the copy button to add the whole summary to your clipboard.
- Click on the ‘Create Jira issue’ button to add the error summary directly to the Jira ticket creation form.
For technical investigation, open the full error details and share the error page or copied error details with your engineering team.