Rage Clicks and Dead Clicks: What They Reveal About Your Store
Rage clicks and dead clicks aren't a bug list. They're your buyers writing your next A/B test for you, one frustrated tap at a time. Here's how to read them in Clarity and what each one is asking for.
Your buyers are already writing your A/B tests. You just keep filing them as bugs.
That's what rage clicks are. A shopper taps the same spot three, four, five times in a second because she expected something to happen and it didn't. Dead clicks are the quieter cousin: one tap on something that looks clickable, then nothing. Microsoft Clarity counts both for free, on every session, and most Shopify founders glance at the number once and move on.
Here's the short answer. Rage clicks flag a broken expectation. Dead clicks flag an element shoppers think is a link. Both point at a specific spot on a specific page where the buyer asked for something and the page said nothing back. Every one of those spots is a test idea you didn't have to brainstorm.
A rage click is a buyer asking the same question five times. A dead click is a buyer asking once and giving up.
I'll show you how Clarity defines each signal (checked against Microsoft's own docs on October 28, 2026), where they pile up on product pages, and how to turn the worst one into a test this week.
What is the rage click meaning, according to Clarity?
Straight from Microsoft's semantic metrics docs: a session gets flagged with a rage click when the user clicks multiple times in a clustered area in rapid succession. Microsoft calls them strong indicators of user frustration.
A dead click, per the same page, is a click on an element with no feedback in a reasonable amount of time. The visual state doesn't change. The page doesn't go anywhere. Microsoft lists three causes: broken elements, slow requests, or misleading design.
Clarity tracks a few other frustration signals ux people should know. Here's the whole family on one table.
| Signal | Clarity's definition (paraphrased) | What it usually means on a product page | First test idea |
|---|---|---|---|
| Rage clicks | Rapid clicks in the same small area | A control is broken, slow, or doesn't do what it promised | Fix or swap the control, then test the new version |
| Dead clicks | A click with no response and no page change | Shoppers think something is a link or a zoom | Make it do what they expect, or make it look static |
| Error clicks | Clicks right before a JavaScript error | An app or script is crashing on interaction | Fix the bug first. No test needed |
| Quick backs | Leave the page, return fast | A link sent them away to find an answer | Bring the answer onto the page |
| Excessive scrolling | More vertical scrolling than expected | They're hunting for something they can't find | Move the missing answer higher |
One warning before you compare tools. Definitions vary. Fullstory's help article describes rage clicks as clicking or tapping multiple times, rapidly, in the same area, and flags dead clicks when nothing changes within a few seconds. Neither vendor publishes one shared threshold. So don't compare your Clarity rage click rate to a number from someone else's dashboard.
Why do dead clicks matter more than rage clicks?
Hot take. Founders chase rage clicks because they look dramatic. A red cluster, a frantic recording, it feels like an emergency.
But dead clicks are where the money hides. A rage click means something is broken, and broken things get fixed eventually. A dead click means the shopper wanted something the page never offered. Nobody files a ticket for a feature that doesn't exist.
The classic example is the product photo. Baymard Institute's mobile image gestures research found that 40% of 50 top-grossing US mobile ecommerce sites failed to support pinch and tap gestures on product images. That study is from 2016, but I still see it weekly on Shopify themes. Shoppers tap the photo to see the stitching, the texture, the label. Nothing happens. Dead click.
Here's the thing. That tap is a question: "Can I see this up close before I spend $58?" The page refused to answer.
A bug ticket gets fixed once. A test idea keeps paying every month you leave it running.
Where do rage clicks and dead clicks pile up on a Shopify product page?
Same five spots, almost every store.
- Variant and size selectors. A swatch that takes a second to update the price or photo gets hammered. Clarity's filters page lists an Interaction to Next Paint target of 200 milliseconds or less. A selector that sits past that feels broken to a thumb.
- Product photos. Dead clicks when there's no zoom. Rage clicks when the zoom loads slowly.
- Star ratings. Shoppers tap the stars expecting to jump to reviews. On many themes, the stars are a picture.
- Shipping and returns lines. Bold text that says "Free returns" gets tapped for the details. It's plain text.
- Add to cart while an app loads. A bundle or upsell app that blocks the button for a beat earns a burst of taps. Sometimes that burst adds three units to the cart, which is its own mess.
Notice the pattern. Every one of these is a buyer asking a question in the last 30 seconds before a purchase. Price for this size? Is it well made? Do other people like it? What if it doesn't fit?
I wrote up the visual side of this in how to read heatmaps. This post is about what to do once you've found the spot.
How do you find rage clicks in Microsoft Clarity?
Two routes. Do both.
Route 1, the map. Open Heatmaps, pick your best-selling product page, switch to mobile. Clarity's click maps docs list Dead clicks and Rage clicks as their own map types. The left panel ranks elements by click count. Select the top one and hit View recordings to watch the sessions where people clicked it.
Route 2, the filter. Open Recordings, then Filters. Under User actions, pick Rage clicks or Dead clicks. Per Clarity's filters overview, Shopify projects also get a Purchases filter. Set it to "No." Now you're watching only frustrated shoppers who left without buying. That's the list that matters.
If the install isn't done yet, my Microsoft Clarity setup guide for Shopify walks through it.
Can AI do the watching? Partly. Clarity's Copilot can write a plain-language summary of a single recording, according to Microsoft's session summaries docs. It skips sessions under five seconds, and Microsoft itself warns that generative AI can misread what happened. I use it to triage 30 recordings down to the 5 worth watching. Then I watch those 5 myself. More on that workflow in AI session recording analysis.
How do you turn a rage click into a test idea?
Every frustration signal has three parts: the element, the expectation, and the missing answer. Write all three down and the test writes itself.
Watch what happens on a hypothetical store. Run the math on a skincare brand selling a $58 vitamin C serum in two sizes. 15,000 mobile sessions a month on the product page. Conversion rate 1.6%, average order value $58. That means revenue per visitor is $0.93 (1.6% x $58 = $0.928). On 15,000 sessions, that's $13,920 a month.
Clarity shows a rage click cluster on the size selector. Recordings show the price takes a beat to update after the tap, and the photo never changes to the bigger bottle. The buyer's question, in her words: "Wait, how much is the big one?"
- Element: the size selector
- Expectation: tap a size, see its price and bottle instantly
- Missing answer: the price per ml, and what the big one looks like
The test: show both sizes as cards with the price and price per ml printed on each, and swap the photo on tap. Say conversion moves to 2.0% at the same $58. Revenue per visitor becomes $1.16 (2.0% x $58). On the same 15,000 sessions, that's $17,400. $3,480 more a month from one selector.
Conversion rate x average order value x sessions. 1.6% x $58 x 15,000 = $13,920. 2.0% x $58 x 15,000 = $17,400.
Rank your list before you test it. Not every red cluster deserves a test slot. My A/B test prioritization framework scores each idea on traffic, revenue at stake, and effort. Then run the winner properly, with the setup in my ecommerce A/B testing guide.
When should you ignore rage clicks?
More often than you'd think. I'll admit I wasted a week once chasing a rage click cluster that turned out to be people flipping through a photo carousel. Fast, happy, on purpose.
Fullstory makes the same point: Next and Previous buttons can trigger the signal when repeated clicking is expected. Quantity plus buttons do it too. So does a shopper zooming in and out.
Three rules before you act:
- Watch three recordings. If the shopper keeps going and buys, it's not frustration.
- Check concentration. One element owning most of the page's rage clicks is a signal. A sprinkle across 20 elements is noise.
- Check speed first. If the rage sits on something slow, the fix is speed, and no copy test will save it. Start with our page speed and conversion rate study.
Frustration on a slow button is a speed problem. Frustration on a working button is a message problem.
What do rage clicks reveal about the page itself?
This is the part nobody puts in the Clarity tutorials.
Fix every dead click and rage click on your store and you've plugged leaks. Good. Leaks are small money. The big money is the page that answers the buyer's questions before she ever needs to tap around looking for them.
Real client numbers, not typical results, and not a promise of what your store will do: our flagship bedding store started at a 1.0% conversion rate and a $125 average order value. That's $1.25 revenue per visitor. After the page rebuild, conversion rate was 3.5% and average order value was $231, which is $8.10 per visitor (3.5% x $231 = $8.09, rounded). On 10,000 visitors, that's $12,500 against $81,000. The full before and after numbers are on our results page.
No zoom fix did that. A page that said the right thing in the right order did. That's why I judge every change on revenue per visitor instead of conversion rate. Rage clicks show you where the page is mute. The rebuild is what makes it talk.
What to do next
Open Clarity today. Go to Recordings, filter by Rage clicks, set Purchases to No, and limit it to your best-selling product page on mobile. Watch five sessions. Write down the one element that shows up in at least three of them, plus the question the shopper was trying to answer. That's your next test.
Book Your Profit Audit
Rage clicks and dead clicks show you where the page went silent at the exact moment a buyer asked a question. On a profit audit, Ishan Soni's team at RevenueFlows AI will show you what those silent spots cost you in revenue per visitor, and how to rebuild a high-converting product sales page in less than 15 minutes.
Or go here to check it out → revenueflows.ai
P.S. Treat rage clicks as a bug list and you'll fix a button. Treat them as a test queue and you'll fix the page.
Frequently asked questions
What does rage click mean?
A rage click is when a shopper clicks or taps the same small area several times in rapid succession. Microsoft Clarity flags it as a strong sign of frustration, usually because the shopper expected something to respond and it didn't, or it responded too slowly.
What is the difference between a rage click and a dead click?
A dead click is one click that gets no feedback: nothing changes and the page doesn't move. A rage click is a burst of clicks in the same spot. On a product page, a dead click usually means the shopper thought something was a link, and a rage click usually means something they relied on was broken or slow.
How do I find rage clicks in Microsoft Clarity?
Two places. Open Heatmaps, pick your product page, and switch the click map type to Rage clicks or Dead clicks. Or open Recordings, select Filters, and under User actions pick Rage clicks. Clarity Shopify projects can also filter by Purchases, so you can watch only the frustrated sessions that didn't buy.
Are rage clicks always bad?
No. Some controls get clicked fast on purpose, like image carousel arrows or quantity plus buttons, and Fullstory notes that Next and Previous buttons can trip the signal when repeated clicking is expected. Always watch three recordings before you call it a problem.
How many rage clicks are too many?
There's no universal number, because every tool defines the signal a little differently. I care about concentration: if one element on a top product page owns most of the rage clicks on that page, it's a test this week, regardless of the raw count.