Error tracking for your server and frontend
Get notified the moment your app starts throwing errors — from your own backend or visitors' browsers — grouped into issues, with visitor attribution.
Two independent toggles
Server-side and frontend error tracking are both off by default and configured separately under Settings → Errors, so you can turn on either one (or both) without the other. Server-side reporting is authenticated with your site's API key, the same as the Transactions API, and lets you choose exactly which response codes should count as an error for your app.
One issue, not a flood of duplicates
Every occurrence is grouped by the underlying error rather than creating a new row per request, so a spike in the same bug shows up as one issue with a rising count instead of drowning your inbox. You get notified by email the first time a new issue appears, and again if one you've resolved starts happening again — so "resolved" actually means something.
Know who it happened to
Frontend errors are automatically attributed to the visitor who hit them. Server-side errors can be too, using the same visitor cookie your Transactions integration already reads. Either way, the Errors page shows their real name if you've identified them, with a direct link to their full visitor journey.
What shipped
- NewReport server-side errors from your own backend (Laravel, Express, or anything that can make an HTTP request) via a new API, with your own rules for which response codes count as an error.
- NewTurn on frontend error tracking to automatically capture uncaught JavaScript errors and unhandled promise rejections from visitors' browsers — no code change beyond the tracking snippet you've already installed.
- NewRepeat occurrences of the same error are grouped into one issue instead of flooding you with duplicates, with an occurrence count and first/last seen times.
- NewGet an email the moment a new error shows up, or if one you'd already marked resolved starts happening again.
- NewSee which visitor an error happened to — with their real name if they're identified — linked straight to their visitor journey.
- NewNew Errors page and a Settings → Errors tab for configuring both tracking modes.