JavaScript Errors Detected, Microsoft Clarity

JavaScript Errors Detected for Microsoft Clarity stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

Metrics type: Supporting Metrics • Category: Behaviour Signals

At a glance

JavaScript Errors Detected counts the script errors Microsoft Clarity observed during captured sessions. Errors on ordinary pages hurt the experience, but errors on checkout pages are direct revenue blockers because they can stop a sale completing. Any error appearing on a checkout page is worth treating as urgent.

What it counts	The number of JavaScript errors observed during Clarity-captured sessions over the window.
Sample type	Behavioural session data from Microsoft Clarity (heatmaps and session recordings), refreshed on the standard data refresh.
Why it matters	Script errors break functionality, and checkout-page errors can directly stop conversions.
Reading the value	Lower is better; any rise, especially on checkout or cart pages, demands immediate investigation.
Currency	count
Time window	7D
Alert trigger	>0 on checkout pages
Sentiment key	clr_javascript_errors
Roles	owner, marketing

Calculation

Microsoft Clarity records JavaScript errors that occur while a session is being captured and surfaces them with the pages where they happened. Vortex IQ totals those errors over the window and flags any that land on checkout pages. See At a glance for the time window and the worked example below for a typical reading.

Worked example

A representative reading of JavaScript Errors Detected for a typical merchant on Microsoft Clarity. A store recorded 48 JavaScript errors over 7 days, 6 of them on the checkout page, which tripped the alert. The merchant opened recordings of those checkout sessions and saw the payment button failing to respond. They used Vortex Mind to trace the errors to a third-party script deployed two days earlier, then asked Ask Viq in plain English to estimate how many sessions hit the broken step so they could quantify the lost revenue.

Sibling cards merchants should reference together

Card	Why merchants reach for it
clr_checkout_path_frustration_signals	Links errors to wider checkout frustration.
clr_checkout_path_frustration_spike	Flags the moment checkout problems spiked.
clr_rage_click_pct	Errors often trigger repeated frustrated clicking.
clr_dead_click_rate	Broken scripts can turn working buttons into dead clicks.
clr_health_score	Shows how errors drag down overall UX health.

Reconciling against Microsoft Clarity

Where to look in Microsoft Clarity’s own dashboard:

Open the Clarity Dashboard insights for JavaScript errors, or filter recordings to sessions where errors occurred. Confirm the period and filter settings match the Vortex IQ profile before comparing counts.

Why the Vortex IQ value may legitimately differ:

Reason	Direction	What to do
Period boundary. Vortex IQ uses rolling windows by default; Clarity may use calendar periods.	Variable	Match the period range.
Sampling. Clarity may sample sessions on high-traffic sites; Vortex IQ reads what Clarity exposes.	Variable	Allow for sampling on busy stores.
Filter scope. Profile-level filters (device, channel, bot exclusion) may narrow the Vortex IQ view.	Variable	Match filter settings.

Cross-connector reconciliation: complement with sibling cards in the same category for the full diagnostic picture. For divergence investigations, use Vortex Mind.

Known limitations / merchant FAQs

Q: How often does JavaScript Errors Detected update? The card refreshes on the standard data refresh (typically every 30-60 minutes for live integrations). For real-time signals, force a manual refresh from the dashboard.

Q: Why does my Microsoft Clarity dashboard show a different number? Clarity only records errors during sessions it captured, so sampling on high-traffic sites and bot filtering can change the count. Period boundaries and device or channel filters also shift the total. Match sampling, bot filtering, period, and filters before assuming a real divergence.

Q: Why are errors on checkout pages treated differently? A script error on a checkout or cart page can stop a customer completing their order, so it maps directly to lost revenue. That is why the alert fires on any checkout-page error, even a single one, while ordinary pages tolerate a higher baseline.

Q: Can I customise the alert threshold? Yes, alert thresholds are configurable per profile in the Alert Rules tab. Adjust to match your business baseline rather than relying on the generic default.

---

Tracked live in Vortex IQ Nerve Centre

JavaScript Errors Detected is one of hundreds of KPI pulses Vortex IQ tracks across Microsoft Clarity and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English.

Start for free or book a demo to see this metric running on your own data.