Engagement

Error click

Also called error tap.

Error click is a click associated with a JavaScript error or failed request. The person did something and the page broke.

How it is measured

A listener ties a click to an error that follows within a short window, such as an uncaught exception or a 500 response. The pair is logged with the element and the message.

Tarsier does not collect JavaScript errors from your site. Pair it with an error tracker if you want this signal, and use a custom event to mark the click.

Worked example

On a booking page, 140 sessions in one day click Pay and then hit a console error from a payment script that an ad blocker removed. Support receives three messages, but 140 people ran into the problem.

The team adds a plain fallback link, and the lost sessions drop to 22 the next day.

How it differs

An error click follows a fault. A dead click has no response and no error. A rage click is repeated clicking. An error click is often the cause of the other two.

Common errors

Assuming the user caused the error. Ignoring ad-blocker effects. Not sampling across browsers. Mistaking third-party noise for your own bugs. Reading the log as a user count.

In practice

Match error logs against the two buttons that matter most, usually pay and sign up, and fix the top three errors.

See also

Dead click, Rage click, Session replay

Sources

Count this on a real site.

Watch my website