{"id":175,"date":"2021-09-02T08:08:47","date_gmt":"2021-09-02T08:08:47","guid":{"rendered":"https:\/\/uxsniff.com\/blog\/?p=175"},"modified":"2022-10-20T04:15:39","modified_gmt":"2022-10-20T04:15:39","slug":"rage-click-tracking-now-have-screenshots","status":"publish","type":"post","link":"https:\/\/uxsniff.com\/blog\/rage-click-tracking-now-have-screenshots\/","title":{"rendered":"Rage Click Tracking now have Screenshots"},"content":{"rendered":"\n

Looking back on 2019, we have a feature called rage alerts<\/strong>. It basically just a rage click tracking algorithm by monitoring every single element users are clicking. Rage alert will be triggered if a user clicked more than X times on a single element.<\/p>\n\n\n\n

The X is the rage click threshold where the user can set in the account preferences. By default the rage click threshold was set to “30”. It’s not common that a user will click on a single element more than 30 times in a single session, but still there are exception such as a “load more” button.<\/p>\n\n\n\n

However, we’ve received some feedback while tracking those rage clicks. The rage click tracking insights are great, but the only issue is the way to identify those elements.<\/p>\n\n\n\n

Imagine one day we would tell you that your website users were clicking 500 times on an element. The next questions you would be asking: <\/p>\n\n\n\n

“Where does this happen?” <\/p>

“What they click?”<\/p><\/blockquote><\/figure>\n\n\n\n

It’s easy to tell where does the rage click happens, say your homepage. But it’s hard to illustrate what they click. We have been trying to tell some clues about the element and you have to figure it out. No matter how hard we try to illustrate the element, our users might still need to spend extra time to decipher it. For example:<\/p>\n\n\n\n

“It’s a button”
“It’s a paragraph”
“It contains text: Register”
“Its CSS path: header > .menu > a:nth-child(2)”<\/p><\/blockquote>\n\n\n\n

Finally, we are able to show you the screenshots of the elements and it’s available for all plans. However, there are some known limitations such as:<\/p>\n\n\n\n