JavaScript error monitoring for a small website

You do not need a separate error tool for a website. The script tag that counts your visitors also catches JavaScript exceptions and console errors, groups them, ranks them by severity, and counts how many sessions each one touched. Open one and Clerion explains what breaks for visitors, how to fix it, and gives you a prompt to hand to your developer.

What you see

On the Errors page	What it tells you
The event log	Every issue with its level, when it was last seen, the page, and how many events and sessions
An opened issue	What breaks, how to fix it, a copyable fix prompt, and the visitor's last actions before the error
Deploys	Each deploy against the day before it, so a release that caused the errors shows up by name
Rage clicks	The elements visitors keep clicking, often the same ones the errors are on

How it works

The snippet listens for uncaught exceptions, rejected promises and console errors. Each one is sent with the page, the stack and the visitor's last few actions, and deduplicated on the server so one bug is one row however many times it fired. Nothing personal travels with it: no form values, no page text.

The briefing watches the same log. A new error on a page that converts shows up as a signal, with the sessions affected.

Limits

Limit	What it means
Browser errors	Clerion catches what happens in the visitor's browser. Server errors are not seen unless they surface as a failed request on the page.
Source maps	Stack traces are resolved when a source map is reachable; otherwise they show the built file.

Set it up

Nothing beyond the one script tag. To tie errors to releases, add deploy markers.

Questions

Does this replace Sentry?

For a website, usually. Clerion groups and explains the errors visitors hit on your pages. For a backend, or a large app with alerting rules and ownership workflows, a dedicated error tool fits better.

Can I get the fix written up?

Yes. Each issue has a fix prompt to copy, and Ask Clerion can write a bug ticket with steps, the likely cause on your stack, sessions affected and the breadcrumbs.