Dead click detection
A dead click is a UX-signal event where a user clicks an element and nothing observable happens — no navigation, no DOM change, no network call. Experience tooling derives it by watching for the absence of a reaction after a click within a short window. Like rage clicks it is not a native GA4 event; you compute it and send it as a custom event. It flags elements that look interactive but are inert.
How it is derived
The detection rule is: a click occurred, and within a short window there was no observable change — no URL change, no mutation to the DOM near the target, no triggered request. The window length and what counts as 'a reaction' are tool conventions. Because there is no standard dead_click event, you implement the rule and emit a custom event when it matches.
Dead click vs rage click
A dead click is a single inert click; a rage click is repeated clicks driven by frustration. They often co-occur — a dead control gets clicked again and again — but the signals answer different questions. Dead clicks tell you which elements are inert; rage clicks tell you which ones frustrate users enough to repeat. Use both to separate 'looks clickable but isn't' from 'fails repeatedly under pressure'.
- Rule: click with no observable reaction in a short window
- Single inert click, unlike repeated rage clicks
- No native GA4 event — send as custom
How it appears in analytics and logs
A dead click means the affordance is misleading: the element invites a click but has no handler or effect. It is a design issue, not necessarily a script error.
Diagnostic use case
Find controls that users click but that do nothing, by detecting clicks with no following DOM, URL, or network change, then make them responsive or non-clickable-looking.
What WebmasterID can help detect
WebmasterID can store a labelled dead-click signal (selector plus 'no reaction') as a custom event without capturing replays of real visitors.
Common mistakes
- Confusing dead clicks with rage clicks in reporting.
- Counting intentional no-op clicks (already-active tab) as dead.
- Capturing user identity to detect a UI defect.
Privacy and accuracy notes
Detection needs only the clicked selector and whether a reaction followed — not user identity or typed content. Keep the signal non-identifying.
Related pages
- Rage click detection
A rage click is a UX-signal event: a user clicks the same element several times in quick succession, usually because something looks interactive but does not respond. Frustration-signal tooling defines it by a click count within a short time window on a small pixel area. It is not a standard GA4 event name; it is a derived behavioural signal you compute or import. Treated carefully it flags broken or confusing UI.
- Error click detection
An error click is a UX-signal event where a user's click is shortly followed by a JavaScript error, suggesting the click triggered a fault. Experience tooling correlates click timing with the next thrown error within a window. It is a derived signal, not a native GA4 event; emit it as a custom event. Unlike a dead click (no reaction) it indicates the handler ran and failed.
- Custom events: tracking what matters to you
Custom events capture meaningful actions a pageview cannot — a CTA click, a signup, a video play, a form submit. The value is in a consistent naming taxonomy and well-chosen properties. The risk is putting personal data into event names or properties, which turns analytics into surveillance. This page covers both.
- Website observability
Detect inert UI controls without replaying users.
Sources and verification notes
- MDN — Event (DOM events and reactions)Reaction primitives; dead-click definition is a tool convention.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.