At a glance
This table ranks your pages by how many dead clicks they attract, so you can see exactly where shoppers are clicking things that do nothing. A dead click is a tell-tale sign that something looks interactive but is not, whether a flat image, a broken link, or an element that fails to respond. Sorting by page turns a vague usability worry into a prioritised fix list.
| What it counts | Dead-click events grouped and ranked by the page they occurred on over the window. |
| Sample type | Behavioural session data from Microsoft Clarity (heatmaps and session recordings), refreshed on the standard data refresh. |
| Why it matters | It pinpoints the exact pages where shoppers waste effort on non-working elements, so fixes go where they pay off most. |
| Reading the value | Lower per page is better; the pages at the top of the table are where dead clicks concentrate and should be reviewed first. |
| Currency | count |
| Time window | 30D |
| Alert trigger | - |
| Sentiment key | clr_dead_click_hotspots |
| Roles | owner, marketing |
Calculation
Microsoft Clarity records dead clicks, where a click produces no response, per page from real sessions. Vortex IQ groups those events by page and ranks them so the worst offenders rise to the top of the table. See the At a glance table for the time window, and the worked example below for how it reads in practice.Worked example
A representative reading of Dead Click Hotspots (by page) for a typical merchant on Microsoft Clarity. Over 30 days a store’s product template tops the table with around 1,200 dead clicks, far ahead of any other page. The merchant opens Vortex Mind to trace the hotspot upstream and finds shoppers repeatedly tapping a product image expecting a zoom that was never wired up. They ask Ask Viq “what are shoppers clicking on the product page that does nothing?” in plain English, add the zoom behaviour, and the page drops down the ranking on the next refresh.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
clr_dead_click_pct | The store-wide dead click rate this table breaks down by page. |
clr_rage_click_rate | Rage clicks often cluster on the same hotspot pages. |
clr_javascript_errors | JavaScript errors are a common cause of dead clicks. |
clr_checkout_path_frustration | Flags when hotspots fall on revenue-critical checkout pages. |
clr_top_pages_by_sessions | Puts hotspot volume in context of each page’s traffic. |
Reconciling against Microsoft Clarity
Where to look in Microsoft Clarity’s own dashboard: Open the Clarity Dashboard dead-click insight and the per-page heatmaps to see exactly where clicks land. Confirm the period and any device or channel filters match the Vortex IQ profile. 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. |