In short:
- Classic exit intent: does not work on mobile. It watches a mouse pointer leave the window, and a phone has no pointer.
- Mobile exit intent: uses a different signal, a fast upward swipe after the visitor has read part of the page.
- Our Divi 5 test: a fast swipe up (4,000 px/s) opened the popup on a phone; a slow one (400 px/s) did not.
- Still a guess: visitors who tap Back without scrolling are missed, so a scroll trigger is often the better phone choice.
Why exit intent never fires on a phone
Exit intent never fires on a phone because desktop exit intent waits for the mouse pointer to move up towards the browser tabs or the Back button. On a touch screen that event never happens. Many popup tools stop there, so their exit campaign never appears on mobile.
Divi 5 itself has no exit-intent trigger at all, on desktop or phone. Its Mouse Exit interaction watches one module, not the browser window.
The fastest way to get exit intent on phones
The quickest route is a popup tool with a touch version of the trigger, plus a way to see why it did or did not fire. On a real phone, nothing on screen tells you which rule held it back.
We built Divi Smart Popup at ByteKeel to remove that guesswork. Its Exit intent trigger fires on the pointer leaving the window on desktop and on a quick upward scroll on touch screens. Check campaign opens the page in test mode, visible only to you, and lists which rule lets the popup open or holds it back.
You can try it on a private WordPress in the ByteKeel playground. If you are building natively in Divi 5 without a plugin, the native options are further down.
What "leaving" looks like on a phone
On a phone, leaving usually looks like a quick flick back to the top of the page to reach the address bar or the Back gesture. In the Divi Smart Popup 2.1.4 source, the touch version of exit intent fires only when all three of these are true:
- Touch screen: the device reports touch input.
- Read past 30%: the visitor has scrolled more than 30% of the page.
- Fast scroll up: they then scroll back up faster than about 1,500 pixels per second.
The touch version is its own switch on the trigger. It is on by default, and you can turn it off to keep exit intent for desktops only.

How we tested mobile exit intent
We used the exit-offer demo page on our popup demo site: a long article with an exit-intent popup, frequency set to once per visit. The browser was headless Chrome emulating a 390 × 844 phone with touch input. Each trial started with empty browser storage, so earlier runs could not affect the result.
- Load the page: wait for it to settle.
- Read most of it: swipe slowly down until about 70% of the page has been read.
- Swipe back up: 500 pixels, once at 400 pixels per second and once at 4,000 pixels per second.
- Check the screen: note whether the popup is open.
| Trial | Read before the swipe | Upward swipe | Popup opened? |
|---|---|---|---|
| Slow | 72% | 400 px/s | No |
| Fast | 72% | 4,000 px/s | Yes |

That is the behaviour you want. Scrolling back slowly to re-read a paragraph is not leaving, but flicking to the top often is. The test script and its raw result are part of our launch evidence, and you can repeat the trial on the exit-offer demo with a real phone.
Can you do mobile exit intent in Divi 5 without a plugin?
No. Divi 5 has no exit-intent trigger and nothing that reacts to phones leaving. What you can build natively is a popup that opens on reading, which is often the better phone trigger anyway. Fastest first:
- Build the popup section: a hidden section that Interactions can show, as in create a popup in Divi 5 without code.
- Open it on scroll: add a Viewport Enter interaction (Show Element, target the popup section) to a module about two-thirds down the article.
- Or open it on a delay: add a Load interaction with a Time Delay in milliseconds to a module that is always on the page.
- Limit repeats: add a cookie condition so it stops after a close. Divi's cookie is fixed at a year.
The Viewport Enter point moves when the article gets longer or shorter, so recheck it after edits. Without a frequency rule, a native popup opens on every page view.
What mobile exit intent cannot detect
Mobile exit intent is an estimate, so know its limits before you rely on it:
- It is a guess: a fast flick up usually means "I am done here", but some people flick up to reach a menu. Desktop exit intent guesses too.
- Leaving without scrolling: if someone reads the first screen and taps Back, the browser has seen nothing to react to.
- Short pages: on a page shorter than about two screens, reading past 30% and a fast upward swipe may never happen together.
- The Back gesture: no popup tool can intercept a system Back swipe on iOS or Android, and trying to block it is a poor experience.
Better triggers for phones
Often the better choice is to stop treating mobile as a smaller desktop. Give the desktop popup exit intent, and give a separate phone version one of these triggers:
| Goal | Trigger on phones | Type that suits phones |
|---|---|---|
| Offer to engaged readers | On scroll, 50–70% of the page | Bottom bar or slide-in |
| Reminder for idle visitors | Inactivity, 20–40 seconds | Slide-in |
| Campaign traffic | URL parameter, such as ?offer=spring |
Modal (they clicked expecting the offer) |
| Last chance before leaving | Exit intent with the touch switch on | Bottom bar, which covers less than a modal |
To split versions, duplicate the popup and set the Devices boxes on the Targeting step: desktop on one, phone (and tablet if you like) on the other. Device is decided in the browser by screen width, under 768 pixels for a phone and under 981 for a tablet, so it works behind a page cache.
Native Divi 5 vs Divi Smart Popup on phones
For click and delay popups, Divi 5 is enough. The gap is exit intent, repeat control and seeing why a popup stayed closed.
| Criterion | Native Divi 5 | Divi Smart Popup |
|---|---|---|
| Exit intent, desktop | Not available | Pointer leaves the top of the window |
| Exit intent, phones | Not available | Fast scroll up after 30% of the page |
| Scroll trigger | Viewport Enter on a module | Percentage or element in view |
| How often | One cookie, fixed at a year | Every time, once per visit, every few days or once |
| Finding why it did not open | Trial and error on a phone | Check campaign and test mode |
| Cost | Free with Divi 5 | $29 a year for one site |
When you do not need Divi Smart Popup: your popup opens on a click or after a delay, and showing it once a year per visitor is fine. Native Divi 5 Interactions handle that for free.
How to keep a mobile exit popup polite
Four habits keep an exit popup from teaching visitors to ignore you:
- Cap the frequency: once per visit or every few days, stop after a conversion, and hide it for a few days after a close.
- Prefer small types: a bottom bar or slide-in instead of a full-screen takeover, with a close button that is easy to hit.
- Avoid popups on arrival: Google's guidance on intrusive interstitials warns against covering the main content on mobile.
- Test on a real phone: open Check campaign, read past a third of the page, then flick quickly to the top. If nothing opens, test mode lists the reason.
For the exact setup, read set up exit intent for phones, or see Divi Smart Popup for plans and demos.
Frequently asked questions
Does exit intent work on iPhone and Android?
Classic exit intent does not, because it needs a mouse pointer. A touch version that reacts to a fast upward scroll works on both, since it only needs scroll events.
Can a website detect the phone's Back gesture?
Not reliably. A normal web page cannot see the operating system's navigation gestures, so mobile exit intent watches for a fast upward swipe instead.
Is exit intent the best mobile trigger?
Not always. A scroll trigger is easier to understand and test. Use exit intent when a fast return to the top matches the behaviour you want to catch.
Should a mobile exit popup cover the full screen?
Usually not. A bottom bar or small slide-in leaves more of the page visible, is easier to dismiss and is less likely to feel intrusive.



Leave a Reply