Rage clicks and dead clicks without session recordings

You can spot UX problems from counts alone. No screenshots, no text, no replays.

Last updated

Session recordings show exactly what a visitor did, which is also why they raise privacy concerns: screens can contain personal data. Frustration signals give you most of the “where is it broken?” value without capturing anything visual.

The signals

  • Rage click: three or more clicks within one second inside a small area, usually on something that is not responding.
  • Dead click: a click on something that looks interactive, such as a button or a placeholder link, where nothing on the page changes within a short time.
  • JavaScript error: an uncaught error or rejected promise on the page, which often explains rage clicks.
  • Outbound and download clicks: where people leave, and which files they want.

What aydex collects

aydex detects these in the browser and sends only a count, the page path and a CSS selector (for example button#buy), or for errors a scrubbed message with emails, long numbers and query strings removed. It never captures screenshots, page text, keystrokes or form input. The Behavior tab ranks pages and elements so you know where to look.

How to act on them

  1. Open the Behavior tab and sort by the page with the most rage clicks.
  2. Reproduce the problem on that element: slow response, missing loading state, or a click target that is too small.
  3. Cross-check with JavaScript errors on the same page.
  4. Fix it, then watch the count fall over the next week.

Limits to know

  • Dead-click detection is a heuristic. Elements that act without changing the page, such as copy buttons, can be flagged. Use data-aydex-ignore on those elements.
  • You see where and how often, not the full story of a single session. For that you would still need a replay tool.
  • Counts are capped per page view to avoid noise from a single frustrated visitor.

Frequently asked questions

Does this record what users type?
No. aydex does not listen to keystrokes or form input and does not read page text.
Can I turn it off?
Yes. Add data-behavior="off" to the script tag, or data-aydex-ignore to individual elements.

Try it on your own site

Free for up to 10,000 pageviews a month. One script tag, no cookies.

Start free