Yes! Sometimes the results returned from Rage Clicks or Form Abandon can represent false positives. For example, you may have a calendar widget that requires a user to rapidly click through the months and FullStory will classify this as a Rage Click.
If you'd like to remove those instances, you can add the class fs-ignore-rage-clicks or fs-ignore-formabandon to the elements you wish to be ignored.
This post will be broken up into two main sections. The first one will cover Rage Clicks, while the second will cover Form Abandon. These are the only supported exclusions at this time.
Adding the class fs-ignore-rage-clicks on an element will make FullStory ignore Rage clicks on the element and the element's descendants.
In the following example, Rage Clicks will be ignored on the <div> element.
<div class="fs-ignore-rage-clicks"></div>
In the code below, Rage Clicks will be ignored on the main <div> element and all of its children, including:
<div> element;<span> element;"Peaches");<p> element and its child <a> element.<div class="fs-ignore-rage-clicks">
<span>Mangocados</span>
Peaches
<p>Copyright 2017 <a href="/">The Fruit Shoppe</a></p>
</div>
In the code below, Rage Clicks on the <div> element and the text node ("Peaches") will be ignored. However, Rage Clicks on the <article> element, the two <p> elements, and the text nodes inside the <p> elements won't be ignored,
<article>
<p>This is a true story.</p>
<p>The events depicted took place in Minnesota in 2006.</p>
<div class="fs-ignore-rage-clicks">Peaches</div>
</article>
fs-ignore-rage-clicks multiple times in the same HTML document to ignore multiple elements.FS-Ignore-Rage-Clicks will not have the desired effect.foo, fs-ignore-rage-clicks, and bar is okay to do:<div class="foo fs-ignore-rage-clicks bar"></div>
fs-ignore-rage-clicks classes, like in the following snippet. The overall effect is that Rage Clicks on the <article> element and its descendants will be ignored.<article class="fs-ignore-rage-clicks">
<div class="fs-ignore-rage-clicks">Peaches</div>
<p>Dragon Fruit</p>
</article><p> will be ignored just as well as clicks on the text "Peaches" (Though the fs-ignore-rage-clicks isn't required for FullStory to ignore Peaches since it is nested inside the already excluded <article>).Using fs-ignore-rage-clicks will only affect future session recordings; it will not retroactively exclude elements from Rage Clicks in your FullStory sessions.
Ignoring Form Abandon for a form
Adding the class fs-ignore-formabandon to a <form> element will disable tracking form abandonments on that form.
In the example below, adding the class on a form disables tracking form abandonment only for that particular form. Other forms on the page will continue to be tracked for form abandonment.
<form action="" method="post" class="fs-ignore-formabandon">
<input type="submit" value="Save">
</form>
In the example below, the code won't disable form abandonment for either of the two forms because the class is not directly on the <form> elements.
<body class="fs-ignore-formabandon">
<form action="" method="post">
<input type="submit" value="Save">
</form>
<form action="" method="post">
<input type="submit" value="Purchase">
</form>
</body>
fs-ignore-formabandon on multiple forms in the same HTML document to ignore multiple forms.FS-Ignore-FormAbandon will not have the desired effect.<form class="foo fs-ignore-formabandon bar"></form>Using fs-ignore-formabandon will only affect future session recordings; it will not retroactively exclude elements from Form Abandon in your FullStory sessions.
If you're not able to include the fs-ignore classes in the HTML itself, it's possible to run JavaScript on the page in order to include them when the page loads for the user. However, there's a caveat: it's possible the user could abandon the form or Rage Click before the JS fires and the class is added in which case FullStory would still record these as frustration events.
Because of this, the best practice is to add fs-ignore-formabandon and fs-ignore-rage-click directly to the element in the HTML to ensure the respective interactions are not recorded as frustration events.