KakapoWP KakapoWP
Log in Try for free
Help Center/Analytics/Rage clicks, dead clicks and forms

Rage clicks, dead clicks and forms

Applies to: Kakapo Analytics· 5 min read

Three reports show friction instead of reach: repeated clicking out of impatience, clicks without any effect and forms that are started but never sent. All three arise from the same behavior events as the heat map.

How the signals come about

  • Rage click: several clicks on the same element within the set time window — counted per element, not per screen position
  • Dead click: a click on an element that does not count as operable and after which neither the address nor the page content changes
  • Form: one start event per form, one event per field focus, the submission and, when the page is left, a drop-off for every form that was started but not sent
  • Field measurement: when a field is left, the dwell time is measured and a distinction is made as to whether it is left filled in or empty
  1. Start in the sidebar under “Analytics” at the “Rage Clicks” area.
  2. Read the table with the columns Element, Page, Frequency and Last; above it are metrics such as “Affected elements” and “Share of all clicks”.
  3. Repeat this in the “Dead Clicks” area — there it is about elements that look clickable but trigger nothing.
  4. Switch to “Form Analytics” and check the focuses, the submissions and the rate for each form.
  5. Below that, look at “Field dwell time and drop-offs”: field, form, type, Ø dwell time, filled in, left empty and drop-off share.
  6. If needed, download the “Most frequent drop-off fields” card via the “CSV” button.

Adjusting the thresholds

Under “Administration → Settings”, the “Thresholds” card controls when a behavior counts as conspicuous. “Rage clicks from” takes values from 2 to 20 clicks, the default is 3. “Rage time window (ms)” ranges from 500 to 10000 milliseconds, the default is 2000. The values go to the tracker and take effect from the next page view.

Briefly tabbing through empty fields in under 0.3 seconds is deliberately not counted as a drop-off. A long dwell time with a high drop-off share suggests that the field was understood but not answered; a short dwell time with a high drop-off rate rather that it was not understood. Password fields, card fields and similarly sensitive fields are reported neither by name nor by content, but are listed as ***. Forms that submit via AJAX are recognized as sent through the responses of Contact Form 7, WPForms, Formidable and Gravity Forms.
Was this article helpful?