Why visitors leaveAsk once as they go. See what they click again and again.

Ask leaving visitors once, from five plain answers. See the element people click again and again.

Overview

Analytics shows where visitors leave. Two things in Clerion get closer to why. The exit question asks a visitor who is about to leave a page you choose what stopped them, once, from five plain answers. Rage clicks record the elements people click three or more times in a burst, so the thing that looks clickable and does nothing shows up by name.

The exit question

Add data-exit-question="/pricing,/signup" to your snippet with the pages you care about. When a visitor on one of them moves to leave, after at least five seconds there, a small card asks "Before you go, what stopped you?" with five answers:

  • Too expensive
  • Not sure what it does
  • Missing a feature
  • Something broke
  • Just looking

One click sends the answer. The Custom events page lists the answers for each page, most common first, and the briefing reads them. When one answer dominates a page, it explains the drop there better than any metric.

Desktop only

Phones have no leaving gesture to read, so phone visitors are never asked.

Once per visitor per page

Remembered in the browser. A dismissed card counts as asked.

Five fixed answers

No free text, which keeps it to one click and keeps the answers comparable.

Rage clicks

Three or more clicks on one element, each within 0.7 seconds of the last, are recorded as one burst, with the page and a short selector for the element. The Errors page lists them by page and element, with the number of sessions. There is nothing to set up: the snippet records them on every site.

Images, labels and plain text count as well as links and buttons. Most rows are one of three things: an element that looks clickable and is not, a button that is too slow to show it heard the click, or a control that is broken. The event log on the same page shows the third kind.

Set it up

The exit question needs one attribute on the snippet; the docs page has the path matching and the Next.js form. Rage clicks need nothing; their docs page explains how to name elements so they are easy to find in your code.

Questions

Can I change the question or the answers?

Not yet. The wording is fixed so answers mean the same thing across pages and sites.

Does the exit question need a cookie banner?

No. It stores one small marker so a visitor is not asked twice, and records the answer as an anonymous event.

Is a rage click the same as a dead click?

A rage click is repeated clicking on one element. A dead click is one click that does nothing. Clerion records rage clicks; an element that keeps getting them is usually a dead click people tried more than once.

Also in what they do on the site

Every feature is on every planThe MCP server and deploy markers included.

Start 14-day trial