Less screen, no cursor, a keyboard that eats half the viewport — and one guideline from Google that applies to mobile popups and not to desktop ones.
Each one has a specific consequence.
Desktop exit detection watches a pointer accelerate toward the browser chrome. A touch screen has no pointer. What every vendor calls mobile exit intent is a substitute — a fast scroll upward, or a period of inactivity — and both fire on people who were not leaving.
So: Expect a higher false-positive rate and cap frequency harder than you would on desktop.
Tapping an email field raises the software keyboard, which can occupy half the viewport. A layout that looks balanced in a desktop preview can push its own submit button off-screen the moment someone starts typing.
So: Test with the keyboard open. This is the single most common mobile popup defect.
A small ✕ in a far corner is hard to hit accurately with a thumb, and a popup that feels inescapable gets the back button rather than the close button — which costs you the session, not just the signup.
So: Bigger target, clear contrast, and never a decoy close that opens something else.
Search guidance on intrusive interstitials applies specifically to content being obscured on mobile immediately after a visitor arrives from search results. The same popup on desktop is not covered by it.
So: This is the only popup decision with a direct search consequence. Details below.
Narrower than the panic suggests, and worth reading precisely.
This is a summary of published search guidance, not a guarantee about how any particular page will rank. The guidance itself is the authoritative source and it does change.
Triggers carry a device setting — all, mobile or desktop — so one campaign can use true cursor-based exit intent on desktop and a scroll or idle proxy on mobile, each with its own frequency cap, rather than forcing one compromise across both. Of the 3 exit conditions, only the first is genuinely available on a touch screen, which the builder does not hide from you.
Every popup is designed against a mobile and a desktop breakpoint separately, so the phone layout is something you decide rather than something that happens to the desktop one.
Starting with the one everyone worries about.
They can, in one specific configuration: content obscured on mobile immediately after the visitor clicks through from search results. Google's intrusive interstitial guidance targets that pattern. A popup that waits for a scroll, a delay or an exit signal does not match it, and neither does one shown to visitors arriving from email or social. The safest habit is simply not to fire on arrival for search traffic — which is also the configuration that converts better, so the two goals do not conflict.
Not in the way it works on desktop. Desktop exit intent tracks a cursor moving toward the browser chrome, and a touch screen has no cursor. What tools offer on mobile is a proxy — usually a fast upward scroll, sometimes an idle timeout. Both are useful and both fire on some people who were not leaving, so they need tighter frequency limits than the desktop equivalent.
Small enough that the page is visibly still there behind it, and short enough that the submit button stays visible when the keyboard opens. The keyboard is the constraint everyone forgets: it can take half the viewport, and a popup that needs scrolling once it appears will lose most of the people who started filling it in.
After the visitor has done something that shows they are engaged — reached a scroll depth, spent time on the page, added to cart. Firing on arrival is worse on mobile than desktop on every axis: less screen to share, a higher chance of an accidental mis-tap, and it is the pattern Google's guidance is about.
Usually yes, and the trigger matters more than the design. The same offer can work on both, but the desktop version can use true exit intent while the mobile one has to use a scroll or idle proxy, and mobile benefits from fewer fields and a larger close control. Running one campaign with device-specific triggers is normally simpler than maintaining two campaigns.
We will not publish a figure. Every benchmark in circulation comes from a vendor summarising its own customers, and mobile rates in particular swing enormously with traffic source — paid social behaves nothing like organic search. Measure your own mobile rate separately from desktop, because a blended average will hide whichever one is broken.
Source: Avoid intrusive interstitials and dialogs — Google Search Central