Catch Errors Before Users Report Them
Error tracking collects JavaScript errors, failed requests, files that fail to load and missing pages, and shows first what affects the most visits.
Every error, captured and organized
Each error appears once with a readable title, its events, the visits affected and its trend for the period you choose. Needs attention lists the open ones, most visits first.
TypeError: Cannot read properties of undefined (reading 'map')
Top page: /dashboard
HTTP 500 from /api/checkout
Top page: /checkout
Could not load /img/hero.webp from cdn.example.com
Top page: /
Page not found: /old-pricing
Top page: /old-pricing
Error tracking capabilities
Everything you need to find, understand, and fix frontend errors.
Automatic Error Capture
The tracker reports JavaScript errors, unhandled promise rejections, failed requests, files that fail to load and missing pages, with no extra code. Each error appears once with a readable title such as HTTP 500 from /api/checkout, and its recent reports show the stack trace, the browser and device, and the visitor actions before the error.
Noise Stays Hidden
Reports from bots and scanners, browser extensions, cross-origin script errors and third-party files stay out of the counts. They are never deleted and stay one click away under Hidden.
Needs attention
Open errors from the selected period, sorted by visits affected, with New and Came back badges and a trend for each.
Status and Bulk Changes
Mark errors as in progress, resolve or ignore them, one at a time or up to 25 at once, and reopen them when needed. Editors and admins can change the status.
Error History per Plan
See errors from the last 60 days on Pro, 120 days on Scale and 180 days on Enterprise, and export the filtered list to CSV or Excel.
Know Which Errors Matter Most
See which errors your visitors run into, with stack traces and the actions before each one.
Pro and above • Errors ranked by visits affected • Cancel anytime