Docs

Rage and dead clicks

The exact rules that make a click a rage click or a dead click, what does not count, and how click maps show them on the page.

Applies to EngineCloud At launch

View as Markdown
On this page
  1. Rage click
  2. Dead click
  3. What Sypnia does with them
  4. How an element gets its label
  5. Click maps
  6. Example: the Pay button
  7. Reference

This page is for anyone who wants to find the places where their app frustrates people. Detection happens in the browser SDK and the counts are part of the open-source engine, so the rules are the same on Sypnia Cloud.

An error tells you the code stopped. A rage click or a dead click tells you a person was stuck, even when no error was thrown. In the shop’s story the page showed no error at all: the customer clicked Pay, nothing happened, and they clicked four more times.

Rage click

A rage click is a burst of clicks on the same spot.

The exact rule:

  • A burst is a run of clicks in which each click lands within 30 pixels of the first one, with no more than 1 second between one click and the next.
  • The burst is a rage click when it has 3 or more clicks.
  • It is reported once, when the burst ends: one second after its last click, or when the person clicks elsewhere or leaves the page. The report says how many clicks the burst had.

What does not count:

  • Clicks inside a text field or a text area. People click there to place the cursor.
  • A double or triple click that selects text, such as copying a name from a table.

Dead click

A dead click is a click on something that looks like it should do something, after which nothing happens.

The exact rule: the click lands on an element a person would expect to act (a button, a link, a tab, a menu item, a checkbox or a similar control), and within 1 second none of these happens:

  • the page changes,
  • a request starts,
  • the app navigates,
  • the page scrolls by itself,
  • the answer happens outside the page.

What does not count, because nothing was supposed to change or the answer is elsewhere:

  • A control that is disabled, or already is what the click asks for: the selected tab, the pressed filter, the link to the current page, a checked option.
  • A click that opens something outside the page: a file, date or colour picker, a drop-down’s native list, a download, a link to a new tab, or a link to another app such as mail or the phone.
  • A click that makes the browser show a form’s validation message. That is reported as a form failure instead.
  • A click after which the tab was hidden.

The same element reports a dead click at most once every 2 seconds, so one stuck button does not flood the count. Like a rage click, a dead click is not reported for clicks inside a text field.

A click can be both. Five fast clicks on a button that does nothing are one rage click and one dead click.

What Sypnia does with them

  • They start the recording. A rage click or a dead click makes the browser SDK upload the replay of the session, beginning with the seconds before. See Sessions and replay.
  • They mark the session as having trouble, and appear in its timeline.
  • They are counted for each element: the page’s route, the element, its label, what kind of control it is, where on the page it sits, and how many clicks, rage clicks and dead clicks it got each day.
  • They are evidence in problems. When a problem’s sessions contain rage clicks, the analysis says so: «Two of them tried again and gave up.»
  • They feed the weekly suggestions, where the agent proposes fixes for the elements that frustrate the most people.

They never open a problem and never send an alert on their own. On Sypnia Cloud the daily summary mentions an element when at least 3 people rage-clicked or dead-clicked it the day before.

How an element gets its label

An element is listed with a label a person can recognise, such as «Pay» or «Add to cart». The label is the control’s accessible name or its visible text, up to 80 characters, never the value of a field.

A label is shown only when it is stable: when most clicks on that element carry the same text. Rows and cells of tables, and links whose address contains an id, are listed without a label, because their text is often a person’s name.

Click maps

A click map shows where people click on a page: every click, with rage clicks and dead clicks marked, drawn over a picture of the page.

The picture is a page snapshot: a copy of the page’s structure, taken by the browser SDK with the same masking as a replay. By default the SDK takes snapshots in half of the sessions, at most one for each route in a session and at most 5 routes in a session. It waits until the page has settled, so the snapshot is not a loading screen. A snapshot above 3 million characters is not sent.

Click maps can be read for one device class, because a page is laid out differently on a phone. If a route has no snapshot yet, the clicks are shown on a plain grid.

The Sypnia engine and Sypnia Cloud compared
Sypnia engineOpen source, self-hostedSypnia CloudPaid service, with a free tier
Detection, counts for each elementYes.Yes.
Click mapThe data: clicks by position, elements and the page snapshot, through the API.Drawn in the app, over the snapshot of the page.
Daily summary mentionNo daily summary.Yes, by e-mail.

Example: the Pay button

One customer’s clicks on the checkout page, with the times in seconds since the page opened:

TimeClickWhat Sypnia sees
27.0PayA click. A request starts, so it is not dead.
29.1PayMore than one second after the last click, so a new burst starts here.
29.4PaySecond click of the burst, 2 pixels from its first.
29.7PayThird click of the burst: it is now a rage click.
30.0PayFourth click of the burst.
31.0One second with no click: the burst ends and is reported as a rage click with 4 clicks.

The click at 27.0 is more than one second before the next, so it is not part of the burst. That is why the session’s timeline reads «Clicked Pay», then «Clicked Pay 4 more times».

None of these were dead clicks: each one started a request. The request failed, which is what the problem is about. If the button’s handler had thrown before sending anything, the clicks would have been dead clicks as well.

Over the day, the element «Pay», a button in «Your order» on /checkout, shows 3 rage clicks from 3 people. That is enough for the daily summary to mention it, next to the problem it belongs to.

Reference

The click fields are in the event schema. The numbers for each element and the click map data are in the API reference.

Sections

Start hereWhat Sypnia is, how it works, what is open source and what is the paid cloud, and the two ways to get your first problem in plain words.ConceptsThe ten ideas Sypnia is made of, each defined precisely, from a project and its keys to problems, traces and alerts.SDKsHow your app sends data to Sypnia. One SDK for the browser, one for Node, one for Next.js, and the OpenTelemetry intake for every other backend.The agentHow Sypnia analyses a problem, what it writes, what it sends to a model and what it never does.MCP and skillsConnect your coding agent to Sypnia so it can ask what is failing in production, read what it needs to fix it, and set Sypnia up for you.API referenceThe Sypnia HTTP API: one API for the open-source engine and for Sypnia Cloud, with every endpoint, parameter, response and error.CLI referenceThe sypnia command: how to install it, the variables it reads, what its exit codes mean, and where each command is documented.Self-hostingWhat you run when you host the Sypnia engine yourself, what you need, what it costs, and what you do not get compared with Sypnia Cloud.How the engine is builtThe whole Sypnia engine on one page, from a click in your app to the sentence your coding agent reads, with the design rules and the code that holds them.Sypnia CloudHow the paid service works, from organizations and roles to plans, limits, billing, where your data lives, the GitHub App and support.Privacy and securityWhat Sypnia collects from your app and its users, what it never collects, how masking works, how to delete data, and how the service is protected.LicensingWhich licence covers each part of Sypnia, what you may do with it, how the name may be used, and the terms of a contribution.GuidesStep-by-step recipes for the common ways to use Sypnia, from apps made with AI builders and Next.js on Vercel to Supabase, source maps in CI, alert e-mails from your own engine, and moving from Sentry.ReferenceThe pages you look things up in, from the event schema and the glossary to what is planned, the changelog and the common questions.
↑↓ to move↵ to openEsc to close