Error rate over time
per 1k views, stacked by class- Uncaught
- Rejection
- Console error
00:0004:0008:0012:0016:0020:00
Product tour · Epsilon Delta Gemini · Website monitoring
JavaScript error tracking from real user sessions
JS errors groups real-user JavaScript failures by message and class, with how many views each one affects, its trend and when it first appeared, so you fix the errors with the widest reach first.
JS errors real-user JavaScript failures
“Which real errors hurt the most users?”
- Sample data
- Last 24 hrs
- All platforms
- All events
- All classes · Exclude bots
- Error rate
- 269 per 1k views
- ▼ 4% vs last week
- Pageviews affected
- 12.6%
- Distinct problems
- 388
- grouped by message
- New in window
- 41
- first seen in last 24 h
- Top problem share
- 18%
- one problem
Problems
grouped by message · showing 5 of 388| Error | Class | Rate | Occurrences | Users |
|---|---|---|---|---|
| Uncaught Error: Minified React error #418 | Uncaught | 47.9 | 50,672 | 9.7% |
| TypeError: Cannot read properties of null (reading 'addEventListener') | Uncaught | 45.2 | 47,877 | 4.5% |
| Unhandled rejection: [object HTMLScriptElement] | Rejection | 40.6 | 42,983 | 4.1% |
| Failed to load static props | Console | 25.0 | 26,430 | 1.9% |
| ReferenceError: updateWebView is not defined | Uncaught | 11.8 | 12,479 | 0.9% |
Sample data on example domains (shop.example.com). Your dashboard shows your own sites and apps.
What you can see on JS errors
- Errors grouped by message and class
- Affected views and error rate
- New and recurring errors
- Bot traffic excluded in one click
Questions about JS errors
How are errors grouped?
By message and error class, so one bug appears once with its total reach.
Can I exclude bots?
Yes. One filter removes suspected bot traffic from error counts.
Last updated 6 Nov 2026 · Reviewed by [Name], [Role]