The Error Explorer allows you to go beyond the top 10 errors surfaced in ‘Error Analysis’.
Search across all your errors, focus on a specific page or page group, and pinpoint which errors are affecting your key performance indicators (KPIs).
With Error Explorer you can:
- View and investigate all errors in a unified, sortable list.
- Search for a specific error, page, or page group to see how many errors there are and which have the highest impact.
- Apply multiple advanced filters simultaneously, by error type, status, API status code, custom attributes, and more.
- Sort by any column to prioritize errors based on their KPI impact.
- Ask questions in natural language using ‘Sense’, Contentsquare's AI assistant — it automatically configures filters, views, and sorting on your behalf.
- Share your exact filtered view with teammates via URL, all applied filters are automatically encoded in the link.
Before you start
You can open the Error Explorer from two entry points in ‘Error Analysis’:
- From ‘Search errors’, click ‘Search’ to open the Error Explorer directly.
- From any widget, click ‘See all errors/pages’ to open the Error Explorer pre-filtered to that widget's context.
Step 1. Set your analysis context
Define the scope of your analysis before diving into the results.
- Use the ‘Analysis context’ controls to select a ‘device’ (desktop, tablet, or mobile), a ‘date range’, and a ‘user segment’.
- Use the ‘Analysis scope’ dropdown to choose whether to display errors for:
- Full website (shows errors across your entire site)
- Page group ( you'll be prompted to select a page group from your mapping)
Tip
Narrowing your scope to a specific page group helps you focus on errors affecting a defined part of your site.
Step 2. Build your list view
Choose how the list is organised, then search and filter to zero in on the errors that matter.
Choose a list view
Use the ‘List by’ dropdown to display results grouped by:
- Errors : all grouped JS, API, Custom, Crash and Flutter errors across your full site or selected page group. Search by error name or request URL.
- Pages : the first 100 pages with errors. Search for a specific page to see which errors are affecting it.
- Page groups : all page groups with errors. Select a goal from the dropdown to measure error impact against it.
- Errors on page group : all grouped errors that occurred on a specific page group, with goal impact measurement.
Search
Use the ‘Search’ bar to find a specific page, page group, or error name. You can also search by request URL.
Filter your results
Use the ‘Filters’ panel to narrow down the error list.
Standard filters:
- Error status: Active | Excluded | All
- Error type: All | JS | API | Custom
Advanced filters:
- API : filter by Method (GET, POST, PUT, PATCH, DELETE), HTTPS status code (specific code, all 4xx, all 5xx), or Response body element (key + value).
- JS : filter by file name.
- Custom (CST) : filter by custom attribute key + value or filter on Console messages per log level
Tip
Every filter you apply is automatically encoded in the page URL. Share the link directly with teammates so they see your exact view.
Step 3. Explore and act on the results
Once your list is set up, use it to investigate errors and take actions.
- Drill into an error or page: click any row to open a detail panel with error breakdown and KPI impact.
- Sort the list: click the arrow icon on any column header to sort results. The URL updates automatically, making the sorted view shareable.
- Watch a session replay: click the ‘play’ icon on any row to watch the corresponding session replay(s)
- Go further with Sense: click the ‘sparkle’ icon on any row or in the detail panel to generate an AI summary of the error. You can also use Sense directly on the page to explore results through natural language (see Use Sense with Error Explorer below)
Use Sense with Error Explorer
Sense Chat, Contentsquare's AI assistant, is available directly on the Error Explorer page. Ask questions in natural language and Sense will automatically configure the Error Explorer, setting filters, changing views, sorting results, and displaying more than 10 errors at a time.
Example prompts you can use:
| What you want to achieve | Example prompt |
| Set analysis scope | "Show errors on the checkout page" |
| Change the list view | "Group errors by page group" |
| Search for a specific error | "Find errors mentioning 'undefined is not a function'" |
| Filter by error status | "Show me the excluded errors" |
| Filter by error type | "Show only JavaScript errors" or "Filter by API errors" |
| Apply advanced filters | "Show 404 API errors" |
| Select a goal | "Show impact on the purchase conversion goal" |
| Sort results | "Sort by missed opportunity" |
If you start a conversation with Sense on the ‘Error Analysis Overview’ page and your question requires advanced filtering or more than 10 results, Sense automatically navigates to ‘Error Explorer’ and continues the conversation. No need to start over.
Excluded errors
Sense on Error Explorer follows the same data access rules as the Error Explorer UI. Excluded errors are hidden by default, so you should ask "Show all errors including excluded" to include them.
Configure which errors are collected
To control what Error Explorer shows at a data collection level, click Configure errors (top right of the page). From there, you can:
- Enable or disable specific error types from being collected.
- Exclude Console messages from all Error Analysis features and metrics.