Exit intent detection
Exit intent is a heuristic that predicts a visitor is about to leave the page, most often by detecting the mouse moving rapidly upward toward the address bar or close button. Sites use it to fire a final message such as an offer or reminder. It is a behavioural guess with clear limitations, especially on touch devices where there is no cursor to track.
What this means
Exit-intent detection watches pointer behaviour and infers departure when the cursor moves quickly toward the top edge of the viewport, the path toward the browser's address bar, back button, or tab close control. On detecting that pattern it fires a callback — commonly a modal with an offer, a save-your-progress prompt, or a feedback request. It is implemented with standard pointer events, typically mouseout or mousemove near the top boundary.
Limits and etiquette
The signal is a heuristic, not a certainty: users move toward the top for many reasons, and the prompt can fire when nobody intended to leave. More fundamentally, touch devices have no hovering cursor, so classic exit intent barely works on mobile, where much traffic lives. Some implementations fall back to scroll or inactivity signals, which are even rougher.
Ethically, the interruption has a cost. A single, relevant, easily-dismissed prompt can help; repeated or hard-to-close modals erode trust and may run afoul of intrusive-interstitial guidance. Measure dismissals, not just conversions, to know the true effect.
- Inferred from cursor moving toward the browser chrome
- Largely ineffective on touch devices (no cursor)
- A heuristic that can fire falsely; use restraint
How it appears in analytics and logs
An exit-intent trigger firing means the heuristic guessed the user was leaving — not that they definitely were. Conversions attributed to it should be read against the interruption cost and the false-trigger rate.
Diagnostic use case
Use exit-intent triggers sparingly to surface a relevant last prompt at the moment of leaving, while knowing the signal is approximate and largely absent on mobile.
What WebmasterID can help detect
WebmasterID measures the first-party events around such prompts — shown, dismissed, converted — so you can judge whether an exit-intent prompt helps or merely annoys.
Common mistakes
- Assuming exit intent works on mobile devices.
- Firing repeated or hard-to-dismiss interruptions.
- Counting conversions while ignoring dismissals and annoyance.
Privacy and accuracy notes
Exit-intent reads coarse pointer movement on the current page, not identity. Aggressive or repeated interruption harms experience; use restraint. This page is educational, not legal advice on consent prompts.
Related pages
- Cart abandonment
Cart abandonment happens when a visitor adds items to a cart but does not complete the purchase. The rate is usually one minus (purchases ÷ carts created). It is a useful friction signal, but it overstates 'lost sales' because many adds are research, comparison, or saving for later — not abandoned intent.
- Drop-off analysis
Drop-off analysis measures, step by step, how many users fail to advance to the next stage of a funnel and where the largest losses occur. By isolating the single biggest leak it directs limited optimisation effort to the step with the most upside, instead of guessing or polishing stages that already convert well.
- Micro and macro conversions
A macro conversion is a primary business goal — a purchase, a signup. A micro conversion is a smaller, intermediate action that signals progress toward it, like viewing a product or starting a form. Tracking both gives a richer picture of the funnel, but only the macro conversion should be treated as the headline success metric.
- CTA tracking
Track prompts as shown, dismissed, and converted.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.