> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Rage Click Rate %, Microsoft Clarity

> Rage Click Rate % for Microsoft Clarity stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Card class:** [Hero](/nerve-centre/overview#card-classes-explained)  •  **Category:** [Behaviour Signals](/nerve-centre/connectors#connectors-by-type)

## At a glance

> Rage Click Rate % is the share of sessions where a visitor clicked the same element rapidly and repeatedly, which Microsoft Clarity flags as a strong frustration signal. It usually means something looked clickable but did not work, or did not respond fast enough. A rising rate is an early, vivid warning that part of your experience is broken.

|                       |                                                                                                                            |
| --------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**    | The percentage of Clarity-captured sessions containing rapid repeated clicks on the same element.                          |
| **Sample type**       | Behavioural session data from Microsoft Clarity (heatmaps and session recordings), refreshed on the standard data refresh. |
| **Why it matters**    | Rage clicks are a direct signal of frustration, often pointing to broken or unresponsive elements.                         |
| **Reading the value** | Lower is better; a rise versus the prior period flags a UX or technical fault worth investigating fast.                    |
| **Currency**          | percent                                                                                                                    |
| **Time window**       | `30D vsP`                                                                                                                  |
| **Alert trigger**     | `>5% of sessions`                                                                                                          |
| **Sentiment key**     | `clr_rage_click_pct`                                                                                                       |
| **Roles**             | owner, marketing                                                                                                           |

## Calculation

Microsoft Clarity detects rapid repeated clicks on the same element within a session and flags those as rage clicks, then expresses the flagged sessions as a share of captured sessions over the window. Vortex IQ reads that rate and compares it to the prior period. See At a glance for the time window and the worked example below for a typical reading.

## Worked example

*A representative reading of **Rage Click Rate %** for a typical merchant on Microsoft Clarity.* A store saw rage clicks jump from 3% to 8% of sessions over 30 days, tripping the 5% alert. Opening the heatmaps, the merchant found visitors repeatedly clicking an "Apply discount" field that had stopped responding after a theme update. They used Vortex Mind to trace the spike to the deployment date, then asked Ask Viq in plain English which pages and elements drew the most rage clicks so engineering could fix the highest-impact one first.

## Sibling cards merchants should reference together

| Card                                                                                                                     | Why merchants reach for it                                       |
| ------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------- |
| [`clr_dead_click_rate`](/nerve-centre/kpi-cards/clarity/dead-click-rate)                                                 | Dead clicks and rage clicks often share the same broken element. |
| [`clr_javascript_errors`](/nerve-centre/kpi-cards/clarity/javascript-errors-detected)                                    | Errors frequently cause the unresponsiveness behind rage clicks. |
| [`clr_frustration_signals_vs_cart_abandonment`](/nerve-centre/kpi-cards/clarity/frustration-signals-vs-cart-abandonment) | Connects frustration to lost carts.                              |
| [`clr_checkout_path_frustration_signals`](/nerve-centre/kpi-cards/clarity/checkout-path-frustration-signals)             | Isolates rage clicks happening in the checkout flow.             |
| [`clr_health_score`](/nerve-centre/kpi-cards/clarity/clarity-ux-health-score)                                            | Shows how rage clicks pull down overall UX health.               |

## Reconciling against Microsoft Clarity

**Where to look in Microsoft Clarity's own dashboard:**

Open the Clarity Dashboard insights for the rage click signal, or filter recordings and heatmaps to sessions flagged for rage clicks. Confirm the period and filter settings 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.             |

**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 Rage Click Rate % 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 may sample sessions on high-traffic sites and exclude bots, and its calendar period can differ from the Vortex IQ rolling window. Device or channel filters on either side will also move the rate. Match sampling, bot filtering, period, and filters before assuming a real divergence.

**Q: What is the difference between a rage click and a dead click?**
A rage click is rapid repeated clicking on the same element, usually out of frustration, while a dead click is a click on something that produces no response at all. They often appear together on a broken element, so reading both cards points you straight to the fault.

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

***

### Tracked live in Vortex IQ Nerve Centre

*Rage Click Rate %* 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](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.