Errors overview
Errors & feedback opens on the overview: how many people hit errors, what that may have cost, what people told you through the feedback widget, and what to fix first. It follows the date range and filters in the page header. A new site sees the setup page until its first error arrives.
Errors over time
The first section is a chart with two big numbers beside it.
- People who hit an error counts the visitors who hit an error that isn't noise. Its note gives the share of all visitors.
- Revenue at risk is what the visits that hit an error and left without buying would have earned. Without a connected payment provider it shows a dash.
The chart plots Errors and People hit, with a yellow Feedback dot on each day notes arrived, bigger for more notes. Group by switches between Daily and Weekly, which is available for ranges of two weeks or more. A single day is charted by the hour. Hover a day to see the top issue that day. The GitHub mark just above a day's line shows a release first reported that day, so you can see a spike line up with a deploy, and a note icon shows a day someone left a note. Click either to see that day's notes and releases. See Notes and releases.
Six small tiles sit beside the chart, each with its trend and a note:
| Tile | What it counts |
|---|---|
| Error-free visits | The share of visits that never hit an error. |
| New errors | Issues first seen in the last 7 days. |
| Feedback | Notes people sent through the feedback widget, against the period before. |
| Rating | The average of the stars people gave their visit after sending a note, out of 5. |
| Rage clicks | People who clicked rapidly on one element, and how many buttons. |
| Slow pages | Pages whose slowest quarter of loads is over 2.5 seconds. |
You can also show People hit by errors as a tile on the main Overview, once errors have arrived.
Needs you now
Three things to look at, side by side:
- Error: the open issue with the most revenue at risk, with the people it hit and the release it came in. Open the error opens it.
- Feedback: the open request that reaches the most people, counting the notes merged into it. Read the notes opens it.
- Speed: the slowest page, with its load time and device. See web vitals opens Web vitals.
Fix these first
The top seven issues and notes, ranked by revenue at risk and then by people, with a trend for each. A note's row counts the people asking for the same thing, and opens the note. An issue people wrote about shows how many notes it has. Beside it:
- What an error costs compares how often visits kept going with and without an error. It matches them by page, day and device, so a mobile checkout is compared with mobile checkouts.
- Where people hit them lists the pages with the most affected people.
How the numbers are defined
Hover a figure's label in the app for the same definition.
| Number | Definition |
|---|---|
| People hit | Distinct visitors who hit an error that isn't noise in the range. Its share is against the range's visitors. |
| Kept going | A visit that hit the error and then viewed another page or made a purchase. |
| Revenue at risk | For visits that hit an error and ended without a purchase: their number times what visits to the same page without an error earn. Without a revenue integration it shows a dash. |
| Error-free visits | One minus the visits with an error, over all visits. |
| Slow pages | Pages with at least 20 loads whose LCP at the 75th percentile is over 2.5 seconds. |
| Noise | Browser extensions, bots and suspect traffic, cross-origin Script error. lines, ResizeObserver loops and errors that come only from other sites' scripts. They are flagged, not deleted. |
Revenue at risk is an estimate, not a loss that happened. It rests on how similar visits without an error behave.
Empty states
- Nothing in this range. Widen the date range. An error-free site is a real result.
- No revenue figures. Revenue at risk and the money columns stay empty until a payment provider is connected.