Rage Clicks, Error Clicks, Dead Clicks, and Thrashed Cursor

FullStory surfaces what we call magic moments: those moments in sessions recorded on your website that, though painful to watch, teach you something insightful about your user’s experience with your product. 

Error Clicks

Error Clicks surface sessions with a click right before a client-side JavaScript error occurs.

Start by searching for Error Clicks > On Anything and scope the search to Today or This Week. While watching sessions, you can open the console log recorder to view the specific error that was triggered by the user during their session.

If you find something that seems wrong, you can run another search scoped to the specific click event that triggered the error and view all sessions with Error Clicks around that event. (This is extra easy if you use our Inspect Mode tool)

Dead Clicks

Dead Clicks are clicks that have no effect on the page.

Does that image look like it should zoom in when you click it, but doesn’t? Do users consistently expect that text string to be a link? Is that form-submit button just not working?

Searching for Dead Clicks helps you find the locations where these fruitless interactions are happening.

Rage Clicks

Rage Clicks are like punching your computer with your finger because it didn’t do what you wanted it to. The specific trigger for a Rage Click is clicking multiple times, rapidly, in the same area. 

To be clear, rage clicking is only based on what happens within recorded sessions–FullStory is not able to see user rage manifesting in mouse slamming, keyboard pounding, or some other user behavior.

Rage Clicks signal that your site didn’t react the way your customer wanted or thought it should – and you might want to take a look at changing it.

There is a default “Rage clicked recently” segment in your FullStory sidebar. You can also build your own search using Rage Clicks and any combination of User Scope or Event Scope queries.


Screen capture of a user rage-clicking

Click click click. Maybe if I click a few more times, something will happen!! Let's wear those mouse buttons out! You can almost hear the exasperated muttering from some frustrated computer user.

You can find more information about Rage Clicks through these articles:

Why don't rage clicks work for me?

You may be one of our customers whose Rage Click sessions don’t seem very ragey. That’s because some kinds of UI components, like Next and Previous buttons, naturally invite repeated clicks, which may trigger our heuristic even though it is “intended” behavior. (Then again, you may want to revisit any UI that requires users to click rapidly and repeatedly to accomplish a common task.)

You can add some extra code to ignore these elements in the rage click heuristic.

You can also use additional search refinements to target your Rage Click search. For example, search "Has Rage Clicks on CSS selector #submit-payment" or "Has Rage Clicks on URL path /cart." 

Thrashed Cursor [beta]

Thrashed Cursor finds sessions where users moved their mouse erratically or in circles. 

This can be an indicator that the customer was confused, lost, or waiting on a page to load. 

Try running a search like, "Has thrashed cursor when the URL page path was /cart" to find sessions where users hesitated or had a difficult time in their cart. 


Was this article helpful?

/

Can’t find what you’re looking for?

The FullStory team awaits your every question.

Contact Us