Investigate Microsoft Clarity "Dead Links" — are there problems we should address? #2089
Labels
Feature: Analytics
Google Analytics, Microsoft Clarity, other instrumentation & tools
Feature: Usability
Issues that make it easy for visitors to find the information they need quickly and easily
Research
Role: Design UI/UX
User interface / user experience design
Role: User Research
Tasks related to understanding users, needs, context
Overview
Importance: 4/5 (where 5 is most important) because it can identify frustrating usability issues
You will learn how to use Microsoft Clarity, a terrific user behavior analysis analytics package we use on Food Oasis.
This can be done by anyone on the team (researchers and designers may find this a great experience) and will probably take 4 hours to review recordings, 1 hr to write up.
Problem statement
We use Microsoft Clarity to do analytics to better understand used behaviors on our site.
According to its reports, about 10% of sessions have what Clarity calls "Dead Clicks" — users clicking on things that aren't designed to be interactive, such as plain text. This is a signal for us to investigate why users are doing this.
What is the cause of these "Dead Clicks" and what, if anything should we do to fix them.
Action Items
Preliminary work already completed
I did a little preliminary research on a subset of those dead links:
On the /organization pages, it seems that what count as 'dead links' are actually people selecting and copying/acting on text… probably copying organization names or their details — perhaps to do additional searches on them or to map, or to place phone calls. More details here: https://docs.google.com/document/d/1dzIZ8vJw23mfthigtB8xj5KRUG5QmciNPPeQWDZiVjI/edit?usp=sharing
How to see dead click recordings:
Sign in to Microsoft Clarity
If you are so inclined, also examine other types of clicks: Rage Clicks and Error Clicks
References
Introducing New Types of Click Heatmaps
Rage clicks – what do they tell you about user behavior?
Introducing: Click Errors and JavaScript Error Details
The text was updated successfully, but these errors were encountered: