Error tracking: Catch the errors your visitors hit, and see what led to them

Error tracking, also called error monitoring, records the JavaScript errors your visitors run into, then groups repeats of the same bug so you can see which ones happen most. Betterlytics catches them with the same script that tracks your pageviews, and keeps the session each one happened in.

Yes. It's on every plan, including the free one. Each error counts as one event toward your monthly limit, like a pageview.

Uncaught exceptions and unhandled promise rejections, each with its stack trace and the page it happened on. You can also capture console.error calls. A failed request is only captured when your code leaves its error unhandled. Failed image and script loads are left out, because ad blockers and flaky connections would flood your list with them.

No. It covers frontend errors, the JavaScript that runs in your visitors' browsers. Errors in your server code, API routes or background jobs aren't captured.

Yes. The script skips errors whose stack trace points into a browser extension, so a visitor's ad blocker or password manager doesn't show up as your bug. Errors from bots, headless browsers and test tools like Playwright are dropped before they're stored, the same as their pageviews.

Yes. The script catches errors on any site, whatever framework it runs. Errors a framework catches itself, such as in a React error boundary or Vue's error handler, are usually logged with console.error instead of thrown, so turn on console.error capture to see those too.

Every occurrence of the same bug lands in one group with a running count, so each bug shows up once in your list instead of every time a visitor hits it. Errors of the same type, thrown from the same place in your code, count as one bug even when their messages differ.

No. Stack traces show the code as the browser ran it, so frames from a minified bundle point into the minified file.

It uses no cookies, like the rest of Betterlytics. Messages are kept as your code wrote them, so keep personal data out of them, and leave console capture off if your logs can contain it.

Each page sends at most 10 errors of the same type every 10 seconds, so a loop that throws on every frame stays small. Ignoring a group hides it from the list, but new occurrences still count as events until you fix the cause.

If a visit with an error was recorded, the error links to its replay, with a red marker at each error on the timeline. You can also keep up to two minutes before every error as a replay, even for visits session replay wouldn't otherwise record.