Exit-intent popups and lead magnets

An exit-intent pop-up detects a specific signal — on desktop, the cursor moving rapidly toward the browser’s tab or close controls. It has no reliable equivalent on a touchscreen. That is worth knowing, before assuming the same tactic works the same way on the device most Australian small-business site visitors actually use.

What the trigger technically is, and where it breaks down

Exit-intent detection on desktop watches mouse movement for a fast upward trajectory toward the browser chrome. The reasoning is that this precedes closing the tab or navigating away. It is a real, specific technical signal — not a guess about intent, but a measurable cursor pattern. On a mobile browser there is no cursor. So mobile implementations substitute a different, less precise proxy: usually scroll depth, time on page, or an attempt to switch apps. None of these detect the same thing as directly. Most traffic on a small-business site arrives on a phone. So a pop-up strategy built and tested only on desktop is being validated against a minority of actual visitors. See why mobile-first matters for an Australian small business for the broader pattern this fits inside.

The accessibility requirement that is easy to miss

A pop-up that cannot be dismissed with the keyboard, or that traps keyboard focus inside it so a visitor using a keyboard or a screen reader cannot navigate back out to the page, fails WCAG 2.2’s No Keyboard Trap criterion. That is a real, checkable accessibility requirement, not a matter of taste. Any pop-up implementation should be tested by tabbing through it, and confirming the Escape key or an equivalent control closes it and returns focus to where it was.

Lead magnets are a marketing list the moment the address is used again

A “lead magnet” — a free guide, checklist or discount code exchanged for an email address — looks like a single, one-off transaction from the visitor’s side, but the moment that email address is added to an ongoing marketing list rather than used solely to deliver the single item promised, the Spam Act 2003’s consent requirements attach to it. Consent to receive the specific requested item is not the same as consent to receive an ongoing newsletter. Treating the two as identical is one of the more common compliance gaps in lead-magnet implementations. A genuinely separate, clearly labelled opt-in for ongoing communications — distinct from ticking a box to receive the one thing that was promised — is the structurally correct approach, covered in more depth on the Spam Act and email capture.

Where both genuinely help

A lead magnet can be a legitimate value exchange when what is offered is genuinely useful, and the ongoing-marketing consent is separate and honest. Picture a downloadable checklist relevant to the visitor’s actual problem, delivered immediately, with a clearly optional tick box for anything beyond that single delivery. An exit-intent pop-up can also recover a visitor who was otherwise leaving with no other offer made. That works when it offers a genuine, time-limited discount that actually is time-limited — see urgency and scarcity messaging for where that claim has to be true.

What a pop-up does to Core Web Vitals if built poorly

A pop-up that loads its own separate script, waits for a delay timer, and then injects content into the page can contribute to layout shift, if it appears without reserved space. It can also cause poor responsiveness. This happens if its script blocks the main thread while the visitor is trying to interact with the page underneath it. This connects the pop-up directly to the performance obligations covered on mobile page speed and why it differs from desktop. A pop-up is not exempt from a site’s performance budget just because it is a marketing feature rather than core content. A poorly implemented one can measurably worsen Cumulative Layout Shift.

Frequency and repetition matter for genuine usability, not just annoyance

A pop-up that reappears on every single page view, for a visitor who has already dismissed it once, creates a genuinely worse experience. This is distinct from the accessibility and consent issues already covered. Most implementations support suppressing a dismissed pop-up for a set period, using a cookie or local storage flag. Using this correctly is a basic usability requirement for the feature to be tolerable at all. That is separate from whether the underlying offer and consent handling are honest.

A short, checkable list

Check	Why it matters
Pop-up can be dismissed and does not trap keyboard focus	WCAG 2.2 No Keyboard Trap requirement
Mobile trigger uses a mobile-appropriate signal, not a desktop-only cursor detection	Exit-intent has no direct touchscreen equivalent
Ongoing marketing consent is a separate, clearly labelled choice from the single item promised	Spam Act consent requirement
The offer inside the pop-up is genuinely available as described	Consumer Law — see urgency and scarcity messaging

Also written “popup”: exit popup and exit-intent popup examples

This page writes “pop-up” throughout. “Popup” (no hyphen) is the more common spelling in casual use. Exit intent detection, spelled with or without the hyphen, is the same trigger either way. An exit-intent popup, an exit popup, or an exit-intent pop-up — however it’s spelled — is the same mouse-trajectory trigger described above. The exit popups people actually screenshot as examples online are almost always ecommerce ones.

Cart-abandonment exit popups, discount offers and Shopify or HubSpot popups

Ecommerce popup examples add cart-abandonment specifics this page hasn’t covered yet. A cart-abandonment popup targets abandoning visitors specifically, not the whole site’s traffic. Many exit-intent popups offer discount codes or free shipping as the default move, rather than a genuinely useful message or a survey asking why the visitor is leaving. A Shopify or HubSpot-powered popup, or a set of email capture forms feeding straight into ongoing marketing campaigns, triggers the same signal. The underlying accessibility and consent obligations covered above apply regardless of which platform or CTA generated the popup.

What to do next

Test any existing pop-up with keyboard-only navigation before anything else. It is the fastest way to find a live accessibility failure. If email capture is involved, confirm the consent flow separates the single promised item from any ongoing marketing list, and read the Spam Act and email capture in full before publishing the form. Building this kind of interaction correctly, including the keyboard and consent handling above, is development work rather than a plugin toggle. Web development services covers where it typically sits in a project.