Filter errors to focus on a specific investigation. You can choose to filter by error type and filter based on status code for API errors or add conditions for specific parameters.
1. Click on the ‘Filter’ drop-down menu
2. Check the box of the error type(s) you want to filter by, from the dropdown list (JS, API or Custom errors).
3. Choose the error status (Dismissed, Undismissed or All).
For API errors you can also filter by status code. The options available are:
Group | Details |
All status codes | All status codes |
All 400's | API errors that have a status code 400-499 |
All 500's | API errors that have a status code 500-599 |
For custom errors you can add custom attributes.
4. Click 'Filter' to save your filter options.
You will be able to see how many filters were applied and you can hover over the filter button to see information on the filters.
Dismiss errors
Note: Dismissing errors can only be carried out by Admin or Expert user roles.
Dismiss errors to focus on the errors you want to fix and the errors that you still want to analyze.
Example scenarios when you may need to dismiss errors:
- I have already investigated an error and concluded that it has no UX impact on users
- I have already investigated an error and decided not to fix it
1. Click on the '>' view more button to open the error side panel.
2. Click 'Dismiss this error'.
Good to know when dismissing errors
1. Applies to analysis context, segments and all error tabs: Once an error has been dismissed, it will be excluded from results after setting your analysis context (when using an error condition) and related error based segments. It will also be excluded from results in all Error Analysis tabs (All Errors, Errors by Pages and Errors by Page Groups). For example, If you dismiss an error group in the Errors tab and then go to the Errors by Pages tab, it will also be dismissed.
2. Dismissed for all users: Dismissing an error will mark the error as dismissed for all users on your project.
3. Dismissing an error is retroactive: For example, if you dismiss an error group today and then update your analysis context date range to one week ago, the error group will still be marked as dismissed.
4. Error data is still collected: We keep collecting errors that have been dismissed as they may become impactful later on.
5. Consider all contexts: When you dismiss an error group because it is not impactful in a certain context, you will dismiss it completely, even though it might be impactful in some other context. (E.g. The error was not impacting your checkout page, but it actually impacts your registration page).
FAQs
Will my filter be saved?
Filters are only saved on the current session. If you log out and return, the filters will not be saved.
Do you still keep collecting errors that are marked as dismissed?
Yes, we keep collecting errors that have been marked as dismissed as the error may become impactful at a later date.
Can I un-dismiss an error?
Yes. Open the side panel of the error you need to un-dismiss and click 'Un-dismiss this error'.
I've noticed a sudden change in my results when applying error based conditions, segments, and metrics?
If you noticed a sudden change in your error analyses from the 19th of March 2025 when:
- setting your analysis context with an error condition
- using error based segments
- using error based metrics in dashboard widgets and alerts
This may be related to an improvement we made to the handling of dismissed errors in those scenarios, from that date.
Previously, dismissed errors were included in these results, but from the 19th of March 2025 they became excluded to help you focus on your errors of interest. As this change is retroactive, depending on your volume of dismissed errors, you may notice a change in results.
You can check your volume of dismissed errors by going to Error Analysis and applying the "Dismissed errors" filter.
Are dismissed errors taken into account in the Frustration score?
Yes, dismissed errors are taken into account in the Frustration score. (Frustration score is part of Insights).