JS Error Tracking Available (v1)
Capture the JavaScript errors that real visitors hit on your website, and see what they did right before.
Where in the dashboard
Errors in the sidebar (in the German interface Fehler). The page shows the overall situation and the daily trend at the top, and below it the list of errors, grouped by criticality by default. You can search the messages, sort by Last seen, Affected visitors or Occurrences, and mute single errors.
Key concept
The tracker reports errors through a dedicated ingest path
(/v1/ingest/error-report). It captures uncaught errors and unhandled
promise rejections in the browser. It does not capture console output or
failed network requests.
visz.ai groups identical errors: a recurring bug shows up as one entry with its number of occurrences and affected visitors rather than a flood of duplicates. Message text and stack are masked in the browser and once more on the server before anything is stored.
The point of error tracking in visz.ai is context, not just stack traces: Watch recording takes you to the recordings list, filtered to sessions with a JavaScript error. There you replay what the visitor did right before things broke. That turns “some users get an error” into “here is the exact path that breaks.”
Criticality and noise
Every error group gets a level: Critical when the error happened during an important action, for example in checkout; High, Medium or Low depending on how many visitors are affected. The detail of an error states why it got its level and how it spreads across browsers and devices.
Errors from third-party scripts carry the External script mark. visz.ai lists known, harmless messages under Known noise so they do not bury the list.
Errors as a frustration signal
Errors also feed frustration analysis: if an error happens within half a second after a click, the click counts as an error-click, one of the regular frustration signals.
Related
- Frustration Signals: rage-, dead-, and error-clicks
- Session Recordings: replay the session behind an error
Last updated: