Rage clicks and dead clicks, found for you.

A rage click is someone hitting the same button again and again. A dead click is a click on something that does nothing. ClickClacks looks for both every night and lists what it finds, by how many people it hit.

Start tracking free All features
kinds of friction: rage clicks, dead clicks, abandoned retries
3
people in seven days before a pattern counts as a finding
25
detection across all your sources, with nothing to set up
Nightly
with nothing seen, and a finding closes by itself
3 days

What it does

Friction is where your product fights people. Instead of asking you to watch for it, ClickClacks searches the last seven days of events for three patterns and shows each one as a finding: the element, the page, the people affected and what they did next. There is no setup and nothing to assign.

Detection

Three patterns, defined in plain numbers.

A rage click is five or more clicks on the same element within ten seconds. A dead click is three or more clicks on the same element, with no other event recorded in the thirty seconds after the last one. An abandoned retry is one of your own events fired three or more times, with the session ending within a minute.

  • Clicks come from autocapture, so rage and dead clicks need no code.
  • Each finding is one pattern on one page and one element.
  • Fewer than 25 different people in seven days is treated as noise.

Evidence

What we saw, kept apart from what we think.

Open a finding and the counted facts come first: the element, the pattern, how many events across how many sessions, how many people were hit each day, and what those people did next. The likely cause sits in a separate card, with its confidence and one thing to try.

  • What they did next: clicked it again, carried on elsewhere, or did nothing more in that session.
  • Confidence is high when 90% or more of the people with that pattern on the page hit this one element.
  • “View related events in Events” opens the events behind it.

Investigator

Ask about a finding, and check the answer.

On Pro, each finding has an AI investigator. Ask where these people came from or how your signup funnel did, and it reads the finding, runs your saved funnels and reads your segments and page, referrer and country breakdowns. Every answer lists the evidence it used, and when the data can’t settle a question it says so.

  • The AI model gets aggregates only: never a person, a session or a raw event.
  • It can only read. It offers a pre-filled experiment, and never creates one.
  • 100 questions a month per organization, shared with Ask and “Why did this change?”.

After the fix

It closes itself, then you measure the fix.

Nobody ticks a finding off. After three days with nothing seen it moves to Stopped by itself, and if the pattern returns it comes back as a new finding. To see whether the fix mattered, link a saved funnel and compare two windows, or link an A/B experiment.

  • Before, After and the change in percentage points, each window up to 90 days.
  • Stated plainly as a before-and-after, not proof the fix caused the change.
  • Mute a finding until it stops, for 30 days, or forever. It is still watched.

Questions it answers

Ask it the way you’d ask a colleague.

How ClickClacks answers it

Open Friction on the Happening tab. Each row is one element on one page, with the people it hit in the last seven days and whether it is new, steady or getting worse.

214

people rage-clicked Upgrade on /pricing

Who it’s for

Three ways teams use it.

  • Agencies

    Each client project gets its own findings. Before a retainer call, open Friction and bring the element, the page and the number of people it hit, not a hunch.

    One list per client project

  • Indie developers

    You have no time to watch how people use your app. Install the snippet, and after about a week of events the buttons people hammer and the ones that do nothing are listed for you.

    Nothing to configure

  • Product teams

    After a release, check Happening for anything new. Fix it, link your signup funnel to the finding, and read the before and after once the finding has stopped.

    Finding → Link an outcome

How it works

Under the hood

  1. 01Clicks arrive with the snippetAutocapture sends a click event with the page and the element. Abandoned retries are read from the custom events you already send.
  2. 02Detection runs once a dayEvery night, each project’s last seven completed days are searched for the three patterns, within sessions that end after 30 minutes without activity.
  3. 03Small patterns are droppedA pattern on a page and element becomes a finding only when 25 or more different people hit it in those seven days.
  4. 04The status follows the dataA finding is New, then Steady or Getting worse. After three days with nothing seen it moves to Stopped, with no one marking it done.

Spec sheet

from the product

Rage click
5+ clicks in 10 seconds
Dead click
3+ clicks, then 30 s of nothing
Abandoned retry
3+ repeats, session ends in 60 s
Finding
Pattern × page × element
Threshold
25 people in 7 days
Runs
Once a day, all sources
States
Happening, Stopped, Muted
Stops after
3 days with nothing seen
Mute
Until it stops, 30 days, forever
Investigator
Pro · 100 questions a month

Same events, different question

Works well with

All features →

FAQ

Friction, in detail.

  • Someone clicking the same thing over and over because it isn’t doing what they expect. ClickClacks counts it when one person clicks the same element five or more times within ten seconds, in one session on one page.

  • A click on something that gives no response, such as a card that looks like a button. ClickClacks counts it when one person clicks the same element three or more times and no other event is recorded in the thirty seconds after the last click.

  • No. Rage and dead clicks are found from the clicks the snippet already captures, across all your sources. Abandoned retries use your own custom events. A new project needs about a week of events before findings can be told apart from noise.

  • No. ClickClacks doesn’t record sessions or mouse movement. Findings are counted from events: which element, on which page, how many people and what they did next. To see where a finding sits on the page, open the Friction tab on that page’s heatmap.

  • Aggregates only. The questions you type and totals from your reports are sent to the AI provider, Anthropic. It never receives a person, a session, a visitor ID or a raw event, values that look personal are removed, and a group smaller than five people is shown as “<5”. It is part of the Pro plan; findings themselves are on every plan.

  • Friction doesn’t send email. Findings that are happening are listed on the Friction page and on Home, and any MCP client you connect can read them. A muted finding is hidden for everyone in your organization, and is still watched.

Start hearing your clicks.

One script tag. Your first report in minutes.

Start tracking free Sign in

About 5 KB · pageviews, clicks and scroll depth, automatically