How do I find JavaScript errors on my site?

Short answer

Open Monitoring › Errors. Script errors from real visits are grouped, with a count, the sessions involved and when each was last seen. Expand a group to see every occurrence (time, page, place, device) and open the session. Mark groups Resolved or Ignored when you are done.

Error collection must be on in the snippet: data-errors="true", which the default snippet includes.

1. Make sure collection is on

If the page shows a notice at the top, error collection is off. In Web analytics › Configuration › SDK code, turn JavaScript errors on and replace the snippet on your site. The snippet then includes data-errors="true" and loads a small extra error script.

<script defer src="https://static.pathclue.com/client.js" data-site="YOUR_SITE_KEY" data-errors="true"></script>

2. Read the page

• Cards: error count, error rate, affected visitors and affected sessions. The rate is errors ÷ pageviews in the selected range.
• Trend: error count over time; a jump after a release points to that release.
• Groups: one row per error, with count, sessions and last seen. Status is Active, Resolved or Ignored.

3. Work through the groups

1. Sort by sessions affected, not only by count; one visitor reloading can produce many errors.
2. Expand the group and check the pages, browsers and devices. An error on one old browser may not be worth fixing.
3. Click Open session to see what the visitor did before and after the error.
4. After the fix is released, mark the group Resolved. If it comes back, it is active again.

Frustration clicks

Below the groups, a table lists pages where clicks went wrong:

• Rage click: at least 3 clicks on the same element within 500 ms.
• Error click: a script error within 1 second after the click.
• Dead click: collected later; the column currently shows 0.

A page appears once it has at least 20 pageviews and a rage or error click. The rate is (rage clicks + error clicks) ÷ pageviews × 1,000. Rage clicks depend on autocapture being on.

Common questions

The list is empty. Does that mean no errors? Not if collection is off. Check the notice at the top and the data-errors attribute.

Is there a previous-period comparison? No; change the date range to compare.

The page is slow but there are no errors? Load time is a separate report; see check Core Web Vitals.

Can I get an alert? Monitors have a Frustration condition per 1,000 pageviews; see set up traffic alerts.

To see where on the element people clicked, use a heatmap. Background: rage click and user friction.