Announcement

Agent Analytics now tracks rage clicks

Ask your agent where people rage-click, get the stuck control, then fix it. Docs: Tracker.js.

Agent Analytics now tracks rage clicks

A rage click is when someone hits the same button or link three times in about a second because nothing useful happened. Agent Analytics records that as a rage_click event. Turn on click tracking (data-track-clicks="true") and the tracker emits it alongside normal clicks. Details: https://docs.agentanalytics.sh/reference/tracker-js/

Click burst, rage_click event, agent asks, fix

What to ask your agent

Replace my-site with your project name.

How many rage_click events did my-site get in the last 7 days?
Which pages and controls on my-site produced the most rage_click events this week? Rank by path and element id.
Compare rage_click and $click on my-site for the last 14 days. Where is click volume high but rage clicks concentrated?
Every weekday at 9:00, check my-site for rage_click. If any control has more than 5 in the last 24 hours, tell me the path, the element, and the count in three lines. If none, say so in one line.

The kind of answer you want

Illustrative shape (not live numbers from your project):

my-site, last 7 days
rage_click: 18
Top:
1. /pricing · button#checkout · 9
2. /docs/install · a#copy-command · 5
3. / · a#hero-cta · 4

Or when nothing has fired yet (live check on agentanalytics.sh, 2026-11-06, 30 days, raw count):

rage_click: 0
$click is flowing; no qualifying burst in this window yet.

What you do next

  1. Open the top path and click the named control yourself.
  2. Fix the stuck thing: wrong href, disabled state with no feedback, modal that never opens, copy button that fails on some browsers.
  3. Ask the same question again a few days later and watch that control’s count fall.

Healthy $click volume can still hide one control that frustrates people.

Docs: https://docs.agentanalytics.sh/reference/tracker-js/ Package: @agent-analytics/core@0.2.4

Related posts