Exclude less-than-frustrating interactions from your Rage Click segments in FullStory.
Exciting news! You can now customize your Rage Clicks results by excluding specific interactions that you don't want recognized as frustration in FullStory.
To understand why you might want to exclude certain interactions from Rage Clicks, let's refresh on what Rage Clicks are:
Rage Clicks are moments of excessive clicking or tapping by users on your web site (or app), indexed and searchable in FullStory.
All Rage Clicks indicate areas where the customer experience on your site or app could be improved—whether those clicks are signals of something frustrating, broken, inefficient, or just downright confusing. If you're new to Rage Clicks, get up to speed on common causes and examples of Rage Clicks here.
While Rage Clicks help you find opportunities to improve your online experience, you might not always want successive clicking to trigger a Rage Click event in FullStory.
When are Rage Clicks less-than-frustrating and what can you do about it? Read on!
1. When Rage Clicks aren't super rage-y.
Sometimes Rage Click events merely point to inefficiency in the UX. For example, if a visitor to your site clicks a 'Next page' link multiple times in succession, FullStory might identify the event as a 'Rage Click.' This rapid-fire clicking may represent an opportunity to make navigation easier through search, keyboard shortcuts, or some more perfect solution only you can dream of.
But perhaps that dream is for another day, and you might not want to see those moments mixed in with your more rage-y session recordings.
2. When Rage Clicks represent desirable engagement.
In some cases, you might recognize back-to-back clicks as desired engagements.
For example, imagine that you design a hand clapping widget that encourages users to click many times in succession to applaud a fantastic read on your blog. Or, perchance, you now display an interactive thumb that users can rapidly click to indicate a great experience in your app.
By default, these types of engagements would be registered as Rage Clicks in FullStory. Not great.
Use fs-ignore to exclude interactions from being flagged as Rage Clicks.
Now you can refine your Rage Clicks results to your heart's content for pure, unadulterated raaaaage.
Here's how you ignore rage clicks.
In your site or web app's source code, add the CSS class
fs-ignore-rage-clicks to any elements that you see as acceptable for your users to click often in short succession. This will ensure that any interactions with that element and its descendents will cease to be flagged as Rage Click events in FullStory.
For example, imagine that:
You have a "Next"
<button>with the CSS class
next-button <button class="next-button">Next!</button, and
You want to make sure clicks on the "Next" button never register as Rage Clicks, then you can ...
fs-ignore-rage-clicksas a class to the element, like so:
<button class="next-button fs-ignore-rage-clicks">Next!</button>
Moving forward, any new sessions including rapid interactions with that button will not be flagged as Rage Clicks in FullStory.
class="fs-ignore-rage-clicks" won't retroactively affect old sessions.
Refined Rage Clicks results make it easier to see where to improve UX.
You can read more about how to use
fs-ignore-rage-clicks for Rage Clicks and — bonus! — Form Abandon (
class="fs-ignore-formabandon") in this knowledge base article.
We're excited to give more flexibility to FullStory users, and we're hopeful this little hack will help you hone in on more meaningful session recording research.