Home / Blog / Exit-intent popups

Exit-intent popups: one last offer before the visitor leaves

An exit-intent popup detects when a visitor is about to leave and shows one relevant offer: a discount, a reminder, or a way to stay in touch. It works because it speaks to leaving visitors only, at the one moment a message can still change the outcome.

Key takeaway: trigger one modal on exit intent (or inactivity on mobile), match the offer to the reason they hesitate, cap it at once per session, and make it dismissible in one click.

How the exit-intent trigger works

On desktop, exit intent tracks mouse movement toward the top of the browser window, the gesture of someone heading for the back button or the tab bar. When that pattern fires, the popup appears. On mobile there is no mouse, so the equivalent triggers are scroll-up behavior, a period of inactivity, or a simple time delay. A good setup combines them: exit intent for desktop, inactivity plus delay for mobile, so no leaving visitor slips through silently.

In GrowthTools all of these live in the Triggers tab: exit intent, delay, scroll, inactivity, or click, plus page rules and frequency limits. You catch the leaving visitor instead of losing the session.

Which offers actually recover visitors

Visitor doubtOffer that answers itWidget to use
Too expensiveFirst-order discount or free shippingCoupon modal, countdown collector
Not nowSend the offer by email, remind me laterEmail collector, modal collector
Not sure it fitsTalk to us: chat, callback, demoWhatsApp chat, contact widget, call to action
Needs proofBest review plus a small nudgeReviews plus coupon (see social proof notifications)

The pattern: match the offer to the page. Cart pages get shipping or discount help. Pricing pages get a demo or callback. Blog posts get an email capture tied to the topic, which is exactly the lead capture playbook.

Setup in 3 steps

1. Paste the script once

Create a free account, create a campaign, and paste the deferred script on your site or in your tag manager. Every widget below runs through it.

2. Build the modal

Choose a modal collector or countdown collector, write one headline that names the offer, one line that names the condition, and one button. Add your brand colors so it looks built in.

3. Arm the trigger

Enable exit intent for desktop and inactivity plus delay for mobile. Restrict to the pages where leaving hurts (cart, checkout, pricing). Set frequency to once per session. Publish and check impressions versus clicks in the dashboard.

Recover your first abandoning visitor this week.

Free plan available, no card required. One script, one exit campaign, live in minutes.

Create your free account

4 mistakes that kill conversion

  • Showing it to everyone. New arrivals do not need an exit offer. Page rules plus the exit trigger keep it targeted.
  • Asking for too much. An exit popup gets an email address or a click, not a ten-field form. Save detail for the request collector later.
  • No visible close button. A trapped visitor never becomes a customer. One click to dismiss, always.
  • The same popup on every page. A cart abandoner and a blog reader hesitate for different reasons. Build two campaigns, not one.

Questions

Mouse-based exit detection does not exist on phones, so use the mobile equivalents instead: scroll-up behavior, inactivity timers, or a timed delay. GrowthTools supports delay, scroll, and inactivity triggers that cover mobile visitors.

A popup that appears only on exit intent, is easy to dismiss, and does not cover the main content on load does not create the intrusive-interstitial problem Google penalizes. Keep it to one appearance per session.

Match the offer to the doubt. Price hesitation gets a first-order discount or free shipping. Timing hesitation gets a reminder or a lead magnet by email. Confusion gets a chat or callback option. A generic 10 percent off everything is the weakest option.

Paste one GrowthTools script on your site, create a campaign with a modal or countdown collector widget, enable the exit-intent trigger with page rules and a once-per-session frequency cap, and publish. No developer needed.