TapCub is live — analytics, insights and live chat, free on one platform
Glossary

What are frustration signals? Rage clicks, dead clicks and how to use them

Frustration signals are click patterns that suggest a visitor is stuck: rage clicks, dead clicks, error clicks. How tools define them, why each is only a lead, and a worked example.

Oliver Reed Reviewed by Emma Collins Also called user frustration signals Last updated Nov 17, 2026 Glossary

Quick answer

Frustration signals are click and interaction patterns recorded in a session that suggest a visitor is stuck, such as rage clicks, dead clicks and clicks followed by a script error. They are leads, not conclusions: rank pages by them, then watch sessions to find the cause.

Formula: Rate per 1,000 = (rage clicks + error clicks) ÷ page views × 1,000

What are frustration signals?

Frustration signals are behaviours recorded in a session that suggest a visitor tried to do something and the page did not cooperate: clicking the same spot again and again (a rage click), clicking something that does nothing (a dead click), clicking just before a script error (an error click), and similar patterns. They are detected automatically from clicks, scrolls and navigation, with no survey. The word is also used for human emotion in general; this page is about website and app analytics.

The idea to keep in mind is that a signal is a lead, not a conclusion. It tells you which page and roughly where, but not why, and it can fire for harmless reasons. The workflow that works is: rank pages by how often signals fire, check that the signal is spread across people, then watch a few sessions to confirm the cause before you change anything.

The main signals and how tools define them

Definitions vary between tools, so compare thresholds before comparing numbers.

SignalWhat it meansDatadog's ruleMicrosoft Clarity's ruleTapCub
Rage clickRapid repeated clicks on one spotMore than 3 clicks on the same element within a one-second sliding windowSeveral clicks in a clustered area in quick successionTwo documented rules: the third click within 300 ms and 50 px (heatmap), or 3+ clicks on the same element within 500 ms (Errors page)
Dead clickA click that produces no visible responseClick on a static element that triggers no responseNo visual change and no navigation within a reasonable timeNot collected yet
Error clickA click followed by a script errorClick immediately before a JavaScript errorJavaScript error after a clickA script error within 1 second after the click
Excessive scrollingFar more vertical scrolling than usualNot one of its three signalsSession scrolls more than the expected averageNot a TapCub signal
Quick backLeaves, then returns within a short timeNot one of its three signalsBack to the original page under a time thresholdNot a TapCub signal

All of these come from interaction data (mostly clicks), not from keyboard input, which is one reason they can miss frustration that does not involve clicking.

Why a signal is only a lead

Signals fire for reasons that are not frustration, and they miss some that are.

  • Intentional repeated clicks. Game-like controls, increment buttons, carousel arrows and "like" buttons produce rage-click patterns from happy users.
  • Slow responses. A button that works but takes two seconds invites a second click. The fix is performance, not the button.
  • Non-clickable things that look clickable. An image or a heading that people expect to open something. This is a design fix.
  • A few intense users. One person hammering a button 20 times counts as 20 clicks. Count affected sessions as well as clicks.
  • Silent frustration. People who give up without clicking leave no signal; exit pages and session replay catch those.
  • Bots. Automated clients can produce odd click patterns; check that your analytics separates bots.

Worked example: ranking pages, then checking people

Sample data: one week of a store, with autocapture on. TapCub-style rate = (rage clicks + error clicks) ÷ page views × 1,000.

PagePage viewsRage clicksError clicksRate per 1,000Sessions with a rage clickRage clicks per session
/checkout4,200584624.8292.0
/signup3,100153114.8121.3
/docs/api2,400935.061.5
/pricing9,5002142.645.3
/blog/post12,000600.551.2
/promo1850277.8 (not listed: under 20 page views)31.7

How to recompute: /checkout = (58 + 46) ÷ 4,200 × 1,000 = 24.8. The five listed pages total 193 flagged clicks over 31,200 page views, a site-wide rate of 6.2 per 1,000.

What the table says:

  1. The site-wide number hides the problem. 6.2 per 1,000 sounds mild, but /checkout is at 24.8, four times the average, and /signup at 14.8.
  2. Small pages mislead. /promo shows 5 rage clicks on 18 page views, a rate of 277.8, from three sessions. A minimum page-view threshold keeps it out of the ranking.
  3. Clicks and people are different things. /pricing has 21 rage clicks but only 4 sessions, 5.3 clicks each: a few people hammering one control. /checkout has 58 clicks across 29 sessions, a problem many people hit. Rank by affected sessions before you rank by clicks.
  4. Error clicks point to engineering. /checkout and /signup have many error clicks, so open the error group for that page first.

Decision rule: take the one or two pages that hold most flagged clicks, confirm that at least several different sessions are involved, then watch sessions until you have seen the same element three times or have watched about ten. If most replays show the same element, fix it. If they do not agree, the signal was noise.

What to do with the confirmed cause

What the replay showsLikely causeFix
Click, nothing happens, user clicks againHandler failing or slowCheck errors on the page; make the response immediate, show a loading state
Users click an element that is not a linkMisleading designMake it interactive, or change its look
Click followed by a script errorBroken code pathFix the error; mark it resolved afterwards
Clicks on a form button after validation failsUnclear error messageShow which field failed, next to the field
Everything works, user still repeatsHabit or double-clickIgnore, or debounce the control

After the fix, check the same page's rate the next week. A lower rate with unchanged traffic is the evidence that the diagnosis was right.

Frustration signals in TapCub

Take the sample week. Here is how you would work it in TapCub.

  1. Turn on autocapture. Frustration clicks come from the autocapture script, which needs the Pro plan or higher, set under Web analytics › Configuration › SDK code. If it is off, the Errors page says so instead of showing zeros.
  2. Rank the pages. Open Monitoring › Errors. Under the error groups, the frustration table lists rage clicks, dead clicks and error clicks per page with a per-1,000 rate. A page appears only with at least 20 page views and a rage or error click above zero. Sort by the rate.
  3. Find the element. Open the page in All-platform analytics › Behavior › Heatmaps, choose a device and the Rage clicks tab, then the Elements tab for the most clicked controls.
  4. Watch the sessions. In All-platform analytics › Behavior › Session replay, filter the list by issues (rage clicks, errors) and the page path. Replay is off by default, records web only, and samples 10% of sessions by default, so you see a share of affected visits. See session replay and rage clicks.
  5. Get told next time. In All-platform analytics › Operations › Monitors, a Frustration condition fires when rage clicks per 1,000 page views reach the rate you enter; a dry run shows how often it would have fired in the last 30 days.

Limits to know: TapCub does not currently collect dead clicks (the dead-click column is always 0, so a zero does not mean none happened), and there is no per-session frustration score. The only composite is the stage Sentiment in All-platform analytics › Business › Journey maps, which subtracts weighted error, frustration and exit rates and is computed only for stages that have page patterns. See heatmaps and click maps.

Sources

Was this explanation clear?

We use your answers to fix and expand this page.

Oliver Reed

Product Experience Specialist

Explores usability, user journeys, and feature adoption through practical examples of onboarding and everyday product use.

FAQ

Questions people ask

Short answers to the follow-up questions that come up most.

Still have a question?

Chat with the team behind TapCub — we usually reply within a few hours on business days.

What are frustration signals in web analytics?

They are patterns in clicks and interactions that suggest a visitor is struggling: rapid repeated clicks, clicks with no response, clicks followed by a script error. Tools record them automatically so you can find pages where people get stuck.

What are the three common frustration signals?

Rage clicks (rapid repeated clicks on one spot), dead clicks (a click with no visible response) and error clicks (a click followed by a script error). Some tools add excessive scrolling and quick backs. Thresholds differ between tools.

Does a high number of frustration signals mean the page is broken?

Not necessarily. Intentional repeated clicks, slow responses and a few intense users can all inflate the count. Check the rate against page views, count affected sessions, then watch replays before deciding.

How do I fix a page with many rage clicks?

Find the element first, using a heatmap and session replays. Then match the cause: a slow or failing handler, an element that looks clickable but is not, or an unclear form error. Re-check the page rate the following week.

See this number on your own site

Add one script tag for web and apps, and the first reports fill in within minutes.

See your data clearly. Find your growth.

Every click, backed by data. Install one line of code and see your first numbers in a minute.

No credit card · Free plans for analytics and chat · Cookieless analytics