Rage Click Issues
Learn about Session Replay rage click issues.
If you've enabled Session Replay, you'll be able to see rage click issues on the Issues page in Sentry. Rage clicks are a series of consecutive clicks on the same unresponsive element. They are a sure sign of user frustration and most likely deserve your attention.
In order to see rage clicks in your issue stream on the Issues page, your organization needs to:
- Be sending session replay events
- Enable the JavaScript SDK (or framework-specific bundle), version 7.60.1 or higher
While you can enable session replay with JavaScript SDK version 7.27.0, or higher, you'll need to have version 7.60.1 or higher in order to be able to see rage click issues.
"Slow clicks" (also called "dead clicks") are only detected on <button>
, <input>
, and <a>
elements that don't lead to updates to the DOM or a page scroll within 7 seconds). When the user clicks on one of these elements 3 or more times within that 7 second time frame, it indicates frustration, and the SDK registers a "rage click".
There might be fewer rage clicks than you expect if the user stopped waiting for the site to respond before the 7 second threshold and instead chose to to something else. This is why the rage click issues that you do see are so valuable, because the user that clicked at least 3 times and continued waiting at least 7 seconds for the site to respond is likely very frustrated.
You might also see more rage clicks than you expected from buttons that don't trigger a DOM mutation or page scroll (such as Print and Download buttons). There is no reliable way for the SDK to detect that a download or print has initiated, so a slow click might be generated even if the button is not actually "dead". For these cases, you can configure the SDK via slowClickIgnoreSelectors
- see Configuration for more details.
For example, to ignore detection of dead and rage clicks for download links in your application:
Sentry.replayIntegration({
slowClickIgnoreSelectors: [
".download",
// Any link with a label including "download" (case-insensitive)
'a[label*="download" i]',
],
});
To set up alerts and get notified when a rage click occurs, follow these steps:
- Create a new Alert Rule in Sentry.
- In the "Set conditions" section, set the "IF" filter to "The issue's category is equal to", then choose "Replay" from the dropdown.
- Add an optional filter if you like.
- Choose the action to be performed in the "THEN" dropdown.
- Decide how often you'd like Sentry to look for rage click issues.
- Lastly, name your alert and add an owner.
If you don't want to see rage click issues, you can disable them by going to the Settings page in Sentry, clicking "Projects", and selecting the project for which you want to disable rage clicks. From here, select "Replays" under the "PROCESSING" heading and toggle off "Create Rage Click Issues".
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").