Metrickle

See where people click in frustration, and what they clicked

Find the clicks that cost you sales and sign-ups. The Metrickle script tag notices the moments your interface lets people down: rage clicks, dead clicks, slow controls, clicks that throw an error, quick u-turns, up-and-down scrolling, form errors and form abandons. The friction report ranks them by element and page, so you know what to fix first.

Friction reportquillmere.example · last 30 days
Sessions96,400
With friction13,980
Friction rate14.5%▲ 2.1 pts
Top friction hotspots by element and page, with sessions affected
Element and signalPageSessions
button "Apply discount" Dead click/checkout1,412
input#vat Form error/checkout986
select "Billing country" Slow control/checkout511
/help/vat U-turn/checkout344
a "Download PDF" Error click/invoices207

“Apply discount” looks like a button and does nothing until a code is typed. One in three checkout sessions with friction starts there.

Captured automatically, with nothing to tag

Add the script tag and friction is recorded from the first page view. Each signal carries the element’s selector and visible label, so the report can point at the exact button or field. Rage-click capture can be switched off in the npm package options.

Rage clicks

Three or more clicks within a second, all within about 30 pixels of each other. Usually something slow, or something that looks like it should respond and doesn’t.

Dead clicks

A click on something that looks clickable, followed by nothing: no page change, no DOM change, no focus move and no scroll within four seconds.

Slow controls

A control that did respond, but took between one and four seconds. Long enough for people to wonder whether it worked, and click again.

Error clicks

A click followed by a JavaScript error within a second. The error is tied to the click that caused it, not to whatever was clicked last.

U-turns

Someone goes from page A to page B and comes straight back within seven seconds, in a single-page app or across full page loads. Page B wasn’t what the link promised.

Up-and-down scrolling

Someone scrolls up and down the page four times or more within ten seconds, as if hunting for something. Only wheel, trackpad and touch scrolling counts, so keyboard and screen reader use never sets it off.

Form errors

A field failed the browser’s own validation or was marked aria-invalid. The field is recorded; what was typed is not.

Form abandons

Someone started filling in a form and left the page without submitting it.

A friction rate for every page

Counting clicks overstates the problem on busy pages and hides it on quiet ones. The friction report counts sessions instead: how many sessions hit a signal, and what share of each page’s sessions that is.

Hotspots list the element, the page and the signal, sorted by sessions affected.

  • Sessions affected, not raw click counts, so one frustrated visitor doesn’t top the list.
  • Friction rate per page, to compare a busy page fairly with a quiet one.
  • Filter like anything else: by device, browser, campaign, app version or survey answer.
Friction rate by pagequillmere.example · last 30 days
Sessions on each page, and the share of them that hit any friction signal
PageChartSessionsFriction rate
/checkout13,66531%
/signup9,11524%
/settings2,73012%
/pricing12,9046%
/blog/*41,3302%

Rank pages by rate, not volume. The blog has the most sessions and almost no friction. Checkout has a third as many and the highest rate.

See who your interface breaks for

Every event carries the accessibility settings seen on the device, such as keyboard navigation, zoom, large text, high contrast, forced colours and reduced motion. The friction report shows friction rate and conversion rate for each, next to people using no accessibility settings.

A dead click that a mouse user shrugs off can be a wall for someone on a keyboard. This is where that shows up.

Friction by accessibility settingquillmere.example · last 30 days
Friction rate and conversion rate for each accessibility setting, compared with people using no accessibility settings
SettingSessionsFriction rateConversion
No accessibility settings79,30013%4.1%
Reduced motion5,02013%3.9%
Zoomed in2,84022%2.6%
Large text3,88019%2.8%
Keyboard navigation2,14038%1.4%

People using keyboard navigation hit friction about three times as often and convert at about a third of the rate. Since v4.12 their top hotspot is a form abandon on /checkout/pay, where focus skips “Pay now”.

Browsers hide whether a screen reader is running, so on the web Metrickle reports sustained keyboard navigation instead. Screen readers are reported in your iOS and Android apps.

From hotspot to fix

  1. Find the hotspot

    Sort by sessions affected, or open the page with the highest friction rate.

  2. Check who it hits

    Split by device and accessibility setting, or filter to sessions that didn’t convert or tasks that were abandoned.

  3. See it happen

    Open consented, masked replays of sessions that hit the signal, and read what people said in surveys on that page.

  4. Confirm the fix

    Link the hotspot to an issue. Seven days after it closes, Metrickle measures the share of sessions hitting it again and posts before and after. On a protected task, the case only closes once the same people are getting through again.

Friction without reading what people type

The script tag never reads the values of form fields. A form error records which field failed and why the browser rejected it, never the value. Selectors and short visible labels are kept so hotspots are recognisable.

  • data-mk-mask keeps an element’s text out of every event, for labels that include names or account details.
  • Works in cookieless mode: friction is captured with nothing stored on the device.
  • Web and mobile: the iOS, Android, Flutter and React Native SDKs detect rage taps, dead taps, slow controls, u-turns between screens and form errors (through a formError() helper); error clicks are web-only for now. In SwiftUI, dead taps are judged on controls marked with .metrickleTag(). In React Native, rage taps need touch() on your root view and dead taps need controls wrapped with pressable().
<!-- Field values are never read. -->
<!-- For text that must never be captured, -->
<!-- such as a name on a button, add: -->
<button data-mk-mask>
  Pay as Jane Doe
</button>

See which release is costing you conversions, and who it broke for

Free to start. One script tag on the web, one SDK on mobile, and no cookie banner in cookieless mode.

Start free