A dead click is a click or tap that produces no observable response from a web page or app screen. The element receives the input, and nothing follows: no navigation, no visual state change, no new content. Behavioural analytics platforms record these events automatically and count them as frustration signals, on the reasoning that a user who clicks expects something to happen. The category exists because conventional analytics cannot see the failure: a page view is logged, the session continues, and the funnel report shows a drop-off with no cause attached.

How detection works

Detection is heuristic, and every vendor draws the line differently. The common mechanism is a timer started on the click event and a watch placed on the Document Object Model, the browser's in-memory representation of the page. If the watch sees no mutation before the timer expires, the click is tagged.

Sentry publishes the most specific criteria. Its documentation states that dead clicks, which it also calls slow clicks, are detected only on <button>, <input> and <a> elements that produce no DOM update and no page scroll within seven seconds. Restricting detection to those three tag types is deliberate: a click on a paragraph of text is not counted, because paragraphs are not expected to respond. Sentry's documentation carries an internal inconsistency on the escalation threshold. Its Replays page reference defines a rage click as five or more clicks on a dead element, while the SDK-facing detection criteria define it as three or more within the seven-second window. Both pages were live in August 2026.

Microsoft Clarity applies the label more broadly and specifies less. Its semantic metrics documentation, last updated on December 1, 2025, states that click interactions are marked as dead clicks when a user clicks on an element but gets no feedback in a reasonable amount of time, meaning the visual status does not change and there is no navigation away from the page. Microsoft names three causes: broken elements, high latency requests and misleading interface design. No numeric threshold is published, and Clarity does not restrict detection to interactive tag types, which is why decorative images and body text generate dead clicks in Clarity but not in Sentry. The mobile SDK carries the same logic under the name dead taps.

Fullstory, which built the category, declines to publish thresholds at all. A support response from the company states that dead clicks are triggered if nothing on the page changes within a few seconds of a click or tap, and that the precise definitions are proprietary. Hotjar exposes dead clicks as a session filter rather than a dashboard metric, available on its Scale and Business tiers across recordings, heatmaps, dashboards, funnels and trends, refinable by page URL or CSS selector. Coverage is uneven elsewhere: Datadog collects rage, dead and error clicks through browser real user monitoring, but its mobile SDKs supported only error taps as of a June 2025 exchange on the company's React Native repository.

Where the numbers land

Clarity publishes a public benchmark report drawn from billions of anonymous sessions across fourteen site categories in the United States and Japan, updated daily. In its home and garden category during 2026, the report showed dead clicks occurring in 6.42 percent of sessions, rage clicks in 0.31 percent and quick backs in 9.63 percent. The twenty-to-one ratio between dead clicks and rage clicks is the important relationship: passive non-response is roughly twenty times more common than the escalated repeat-clicking that gets more attention.

Retail data shows the metric moving with traffic composition. Fullstory told CX Dive that across the five days from Thanksgiving to Cyber Monday 2023, dead clicks rose nearly 3 percent and error messages nearly 4 percent, against a 25 percent jump in rage clicks on Cyber Monday itself. The company's 2025 Behavioral Insights Benchmark Report, released on July 15, 2025 and covering 14 billion sessions, reported mobile error clicks up 667 percent year on year, with rage clicks rising 673 percent in food and beverage and 56 percent in retail.

Origin and evolution

The taxonomy originates with Fullstory. A post by Jaime Yap announcing rage clicks, error clicks and dead clicks as searchable event types carries a publication date of January 25, 2018 on the company's Medium blog, though the underlying feature predates that: Fullstory filed a United States trademark application for RAGE CLICK on July 10, 2017 under serial number 87521863. Thrashed cursor and form abandonment were added later, grouped under the label frustration signals.

Microsoft moved the metric into the free tier. Clarity launched on October 28, 2020 with dead clicks, rage clicks, excessive scrolling and quick backs on the default dashboard, no traffic ceiling and no paid plan. That decision did more than any other single event to spread the term, because it put frustration signals in front of small advertisers and agencies who would never have bought an enterprise digital experience platform.

Consolidation followed. Contentsquare announced its acquisition of Hotjar on September 1, 2021, completed its purchase of Heap on December 7, 2023, and fully absorbed the Hotjar business into the Contentsquare Group on July 1, 2025. Sentry entered from the developer-tools side, shipping rage and dead click detection in session replay on August 10, 2023 for SDK version 7.60.1 and above, then adding aggregated top-selector reporting that October. Sentry's framing was different: some broken experiences never throw an exception, so error monitoring alone misses them.

Why it matters for paid media

The metric sits directly on the post-click surface that advertisers pay for and rarely instrument. Clarity added a Google Ads integration on January 13, 2025, connecting campaign performance data to session recordings and heatmaps. The Campaign Insights feature that followed makes the connection explicit, surfacing landing pages that trigger rage clicks or dead clicks behind campaigns whose click-through rates look healthy. One example in Microsoft's own demonstration screenshots showed Italian traffic converting at zero percent against a 7.31 percent click-through rate.

Segmentation extended the diagnostic reach. Clarity made dead clicks and rage clicks filterable by city and state on October 22, 2025, separating a broken checkout on one device-region combination from a generalised landing page problem. Clarity's Copilot layer processes dead clicks among the signals it interprets in natural language, and the WordPress plugin brings dead click analysis into the publishing dashboard.

Distribution became compulsory in one corner of the market. Microsoft Advertising made Clarity a requirement for third-party publishers in November 2025, filtering clicks from pages without the tracking code as nonbillable.

Limitations and disputes

There is no standard. No industry body has defined dead click, and neither the Media Rating Council nor the IAB Tech Lab has issued a specification or accreditation for frustration signals. A dead click rate from Clarity and one from Sentry are not comparable numbers, and neither is auditable against a published methodology the way a viewable impression is.

False positives are acknowledged by vendors. Sentry documents that print buttons, download buttons and audio-playback controls are incorrectly recorded as dead clicks because they do not mutate the DOM, and provides a slowClickIgnoreSelectorsconfiguration option plus a project-level toggle to suppress rage click issues entirely. Text selection, copy-paste on code snippets and email addresses, and accidental taps during mobile scrolling all register as dead clicks and constitute noise rather than signal.

Measurement coverage is narrowing rather than widening. Clarity announced on August 27, 2025 that it would enforce consent signals for sessions from the European Economic Area, the United Kingdom and Switzerland from October 31, 2025, with session recordings and funnels affected where consent is absent. A dead click rate computed on a consented subset of European traffic is not a rate for that traffic. Client-side JavaScript capture also cannot observe agents that do not execute scripts, a gap Clarity addressed separately by building a server-log-based bot activity dashboard rather than extending the replay tag.

The interpretive claim is also contested. Vendors present dead clicks as evidence of a defect, but a click on a non-interactive element can equally be evidence of demand for interactivity that does not exist, which is a product finding rather than a bug report. The signal identifies a mismatch between expectation and behaviour; it does not identify which side is wrong.

Disambiguation

Rage click is repeated rapid clicking in the same area. In Sentry's model it is formally a subset of the dead click, since escalation is only counted on an element already judged unresponsive. In Clarity and Fullstory the two are independent metrics.

Error click is a click immediately preceding a client-side JavaScript or console error. It diagnoses code; a dead click diagnoses design or latency. The two co-occur but are not the same event.

Dead link is a hyperlink resolving to a 404 or an unreachable host. The click works, the navigation happens, and the failure is server-side. Dead clicks are client-side and involve no navigation at all.

Quick back is a click that navigates successfully, followed by a rapid return. Clarity flags it when dwell time on the destination falls below a threshold. The interaction functioned; the destination disappointed.

Recent developments

Attention has shifted from measuring frustration to identifying who is generating it. Clarity introduced AI Platform and Paid AI Platform channel groups on August 29, 2025 to isolate visitors arriving from chat assistants, whose navigation patterns differ sharply from search referrals. It subsequently added the bot activity dashboard in January 2026, drawing on CDN request logs rather than the client-side tag, and moved its Citations feature to general availability on May 13, 2026. As agentic browsing grows, the assumption underneath the metric, that a click reflects a human expectation, becomes the part most in need of testing.

Timeline

  • July 10, 2017 - Fullstory files a United States trademark application for RAGE CLICK, serial number 87521863
  • January 25, 2018 - A Fullstory post by Jaime Yap announcing rage, error and dead clicks as searchable event types is published to the company's Medium blog
  • October 28, 2020 - Microsoft Clarity launches with dead clicks, rage clicks, excessive scrolling and quick backs on the default dashboard
  • September 1, 2021 - Contentsquare announces its acquisition of Hotjar
  • December 7, 2023 - Contentsquare completes its acquisition of Heap
  • August 10, 2023 - Sentry ships rage and dead click detection in Session Replay, requiring JavaScript SDK 7.60.1 or higher
  • October 25, 2023 - Sentry adds aggregated top-selector reporting for rage and dead clicks
  • January 13, 2025 - Clarity launches its Google Ads integration, linking campaign data to recordings and heatmaps
  • July 1, 2025 - The Hotjar business fully transfers into the Contentsquare Group
  • July 15, 2025 - Fullstory publishes its 2025 Behavioral Insights Benchmark Report covering 14 billion sessions
  • October 31, 2025 - Clarity begins enforcing consent signal requirements for EEA, UK and Swiss sessions
  • December 1, 2025 - Microsoft's semantic metrics documentation for Clarity receives its most recent update

Summary

Who: Fullstory originated the frustration signal taxonomy and holds a trademark on the related term rage click. Microsoft Clarity, Hotjar and Contentsquare, Sentry, Datadog, Quantum Metric and Mouseflow all implement dead click detection. The consumers are conversion rate optimisation specialists, user experience researchers, front-end engineers and paid media teams auditing landing pages.

What: A click or tap producing no observable page response within a vendor-defined window, recorded automatically by client-side JavaScript and reported as a session-level metric, a heatmap layer and a session filter.

When: Formalised by Fullstory between 2017 and 2018, spread by Microsoft Clarity's free launch in October 2020, and extended to developer tooling by Sentry in August 2023.

Where: In the browser or app, captured by the replay tag and surfaced in behavioural analytics dashboards. Coverage is constrained in the European Economic Area, the United Kingdom and Switzerland by consent enforcement in effect since October 31, 2025.

Why: Conventional analytics record that a session ended without recording why. Dead clicks convert an unexplained drop-off into a specific element on a specific page, which is the difference between knowing a landing page underperforms and knowing which button is not wired up.