-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make use of $rageclick event from posthog-js #2772
Comments
I think we'll have to iterate the definition we set for rage clicks, but that sounds like an initial good approach. I would just add a threshold for some minor mouse movement. |
The plan is to turn it on for us and see whether it's useful. If it is, we'll autocapture it going forward if session recording is turned on. PostHog/posthog#2772
I believe this can be closed now @macobo ? |
rageclicks are done, I guess this isn't closed because we'd want to display them in recordings? |
A simple implementation is done but the thing is that it's not driving any insights yet - so I wouldn't consider it done. :) |
It's not clear to me if RageClicks are implemented only for PHP/Javascript modules that you need to install setup separately from the JS snippet........ |
Closing as we have the ability to filter for rageclicks and have them highlighted in the events list |
Is your feature request related to a problem?
I want to know when my users are getting frustrated. Either to watch recordings or to find areas of the product which might be frustrating to use.
Describe the solution you'd like
Emit a
$rageclick
event in posthog-js.Expose it in sessions, allow filtering
Describe alternatives you've considered
Looking through all of session recordings. 🥱
Additional context
I think a good first approximation of a rage click is clicking or tapping 3x within 3 seconds without moving the mouse. Any better definitions are welcome.
Once we have the event, after allowing filtering by these events (#2595) we can close #2761
Thank you for your feature request – we love each and every one!
The text was updated successfully, but these errors were encountered: