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 page element. They are a strong signal 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.
"Dead clicks" (also called "slow 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 timeframe, it indicates frustration, and the SDK registers a "rage click".
You can configure Replay to ignore specific selectors if you are seeing too many rage clicks reported. For example, you might want to ignore clicks on "Print" or "Download" buttons.
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, follow these steps:
- Go to the Settings > Projects page in Sentry.
- Select a project from the list.
- Go to the "Replays" sub-page for this project under the "Processing" heading.
- 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").