An exit-intent pop-up appears when a site visitor seems about to leave. On desktop the trigger watches the cursor head for the top edge. Phones have no cursor, so vendors listen for a quick scroll up, a tab switch or the back button, and OptiMonk arms the back button only on the entry page.
That last condition is written in OptiMonk’s own help center: “the Back button only triggers exit-intent popups when the visitor intends to go back from their entry page”, and only after the visitor has interacted with the site. Justuno’s current knowledge base describes its condition as the back button clicked to the point of leaving the website, once the visitor has clicked on the page; an older article kept in its legacy knowledge base says the overlay fires “only when they attempt to leave using the back button on the landing page”. Poptin’s rule is close: its mobile popup fires on a back press that leaves the site, and it “will not show up when the visitors just navigate between the inner pages of your website”. So in these three tools the back-button version of exit intent hears one door out of the site: a back press that leaves it, by a visitor who has already interacted with the page. This guide reads seven vendors’ trigger documentation as served on October 22, 2026, then describes examples by job. It is published by Relvino, which decides per shopper across email, SMS and pop-ups and so has a stake in how stores reach shoppers mid-visit; read it as informed but interested.
Nielsen Norman Group’s explainer describes the original version: “Users’ mouse movements are tracked, and when their cursor moves outside the upper page boundary, the popup is triggered.” The vendors phrase it in slightly different geometry:
Even on desktop it is a guess: a visitor reaching for another tab or a bookmark makes the same gesture as one who is leaving.
A touch screen gives a script nothing to track between taps, so vendors pick gestures that tend to come before a departure.
Wisepops explains the logic: on most phones the address bar disappears as a visitor scrolls down, so leaving by typing a new address starts with a small scroll up. Klaviyo’s mobile exit rule is this one: the form appears when someone “scrolls quickly upward on a mobile device.” Wisepops uses it too and names the trade-off: “If it's too sensitive, the popup will trigger as soon as the user scrolls up a bit. If it's not sensitive enough, your popup may never appear.” A shopper scrolling back up to reread a size chart makes the same motion as one heading for the address bar.
Wisepops notes that mobile visitors often leave by pressing back until they reach the previous site. Its script “triggers popups when visitors press the back button or scroll up slightly”; ConvertFlow’s mobile trigger fires “when the visitor clicks on the back button in the browser or swipes back”; Justuno and Poptin document the back button as their mobile exit rule. A back press from the third page only reaches the second page of the same store; OptiMonk fires only from the page where the visit began, and Justuno and Poptin only on a back press that leaves the site.
OptiMonk lists “the visitor changes focus”, meaning a switch between tabs, among its mobile exit signals. A pop-up shown while the tab is hidden is seen only if the visitor comes back to it, so it greets a returning visitor rather than a departing one.
Justuno suggests pairing its back-button rule with idle time to raise the chance of a showing; OptiMonk offers inactivity as a separate trigger. Idleness is a fallback, not proof of leaving.
Read together, the vendors’ own limits describe four kinds of mobile departure that at least one documented signal misses.
None of this makes mobile exit intent useless. The mobile version reaches a different crowd from its desktop twin, and a report that adds the two together averages two different triggers.
One more document bears on the back-button signal. On April 13, 2026, Google Search Central added back button hijacking to the malicious practices section of its spam policies, with enforcement from June 15, 2026. The policy page defines it: “Back button hijacking is when a site interferes with user browser navigation by manipulating the browser history or other functionalities, preventing them from using their back button to immediately get back to the page they came from.” The announcement says such pages “may be subject to manual spam actions or automated demotions”, and adds that “some instances of back button hijacking may originate from the site's included libraries or advertising platform.”
Google’s policy and announcement do not mention exit-intent pop-ups, and Google has not said whether a pop-up that appears on the first back press falls inside the definition. This guide does not answer it for any vendor. None of the vendor help pages read for this guide mention the April policy; OptiMonk’s own article titled “Will I get penalties from Google if I use OptiMonk popups on my site?”, updated in September, discusses Google’s 2016 guidance on intrusive interstitials rather than the back button. A store relying on the back-button signal can ask its vendor in writing how the trigger touches browser history. Google’s mobile interstitial guidance is covered in the email pop-up examples guide.
The examples that hold up would still be welcome if the guess were wrong. NN/g’s article on exit-intent pop-ups sets the same test: make sure “users get a benefit from the interaction that keeps them on the site.”
The pop-up names the items in the cart, says the cart will be kept, and offers a link to come back to it. NN/g’s example of this job is a store offering to save an unauthenticated shopper’s cart for later, worded as help rather than a sign-up. If the shopper is already known, the abandoned cart email does this job without interrupting the visit, and the cart versus checkout distinction decides which follow-up applies.
NN/g’s research on ecommerce promotions found shoppers leaving checkout to search for a coupon when they see an empty code field and have no code. The exit pop-up ends the hunt: one code, the saving in currency, no question in return. NN/g also flags the failure, a decline button worded to shame the shopper; a plain decline link is enough.
One question, one tap: what stopped the order today, with options such as shipping cost, sizing doubt or just browsing. NN/g advises framing the request around the shopper. On mobile, a survey tied to a back-button rule reaches only visitors who leave by pressing back, so a store wanting answers from deep browsers who leave another way needs a scroll or inactivity rule as well.
A size guide, a care guide, a gift-finder quiz or the returns policy, offered without a form in front of it. NN/g criticizes gating a free guide behind a newsletter sign-up. A good version answers the doubt behind the exit, such as a fit guide on an apparel page.
For considered purchases, a reminder nearer the date that matters; NN/g’s example is a wedding site. For a store, a price-drop or back-in-season alert fits. It asks for contact details, so it overlaps the signup plan.
Free returns, a price match or live chat, mentioned once as the visitor goes. NN/g lists both contact channels and user-friendly policies. It asks nothing, which makes it a safe example to show on a guess.
Narrowing the exit rule is how the guess gets better:
The Shopify popup apps guide compares the apps themselves.
An exit pop-up acts inside the visit, which is its strength: it can reach a shopper the store cannot yet identify, whom the browse abandonment email never sees. Relvino treats pop-ups as one of three channels, with email and SMS, and decides per shopper, in ~80ms, inside guardrails the brand sets.
On a phone the exit is always an inference from a gesture. The examples that age well are the ones a shopper would be glad to see even when the inference is wrong: a saved cart, a size guide, a single honest code.
They are pop-ups timed to the moment a visitor appears to be leaving, as opposed to pop-ups that appear on arrival, after a delay or after a scroll. Nielsen Norman Group argues that their timing is what sets them apart: because they arrive as the visitor is on the way out, it calls them less disruptive than traditional popups, while warning that most ask something of the user and that manipulative wording turns the exchange one-sided. Its test for a good one is whether the visitor gets enough benefit to balance the cost of not leaving.
Pick the exit rule in the pop-up or form tool, then narrow it. In Klaviyo it is a Timing option, Based on rules, then When visitor is exiting the page. In Shopify Forms it is a checkbox in the popup’s Behavior settings, for desktop only. In OptiMonk, add the On exit-intent trigger on the campaign’s Settings tab and switch Mobile on under On devices, or type Change trigger to exit intent in its chat. To test, Wisepops suggests replicating the mouse trajectory of someone about to close the tab, and Justuno recommends starting each test in a fresh incognito or private window so the site treats the visit as a first one.
Pop-ups are usually named by their trigger. OptiMonk’s help center lists six that run on phones as well as desktops: on exit intent, after a delay, after scrolling a share of the page, on a click of a chosen element, after a period of inactivity, and on a JavaScript event the site fires itself. Klaviyo adds cart rules for Shopify stores, such as total cart value or number of items. By job, the common ones are signup offers, cart reminders, exit surveys, announcements and spin-to-win games. Signup pop-ups have their own guide in the email pop-up examples post.
They can, through substitute signals rather than the cursor, and the coverage depends on the tool and the browser. OptiMonk notes that some mobile browsers do not support every signal it listens for, and a signal the browser lacks simply never fires the trigger. Poptin says exit intent does not always work well on mobile because of how mobile browsers behave, and recommends pairing it with a time delay or scroll trigger; OptiMonk lets a campaign hold up to 8 triggers that fire on whichever comes first, which is one way to add that backup. Before trusting a mobile result, check it on a real phone in the browsers the store’s visitors use, including the in-app browsers of the social apps that send traffic.
Google’s spam policies have listed back button hijacking as a malicious practice since its April 13, 2026 announcement, enforced from June 15, 2026, but the policy does not mention exit-intent pop-ups. If Google does take a manual action against a site, its announcement says the owner can submit a reconsideration request in Search Console after fixing the issue, and Google’s spam policy page says sites that violate its policies may rank lower or not appear in results at all. A store can ask its pop-up vendor in writing how the mobile back-button trigger handles browser history.
The technical cutover takes about 30 minutes: connect the Shopify store, point the sending domain and SMS number, and shopper data ingests automatically. Revenue is then measured in a 14-day pilot against the existing setup. Before switching, it is worth writing down each Klaviyo form’s Targeting and behavior settings, including timing rules, frequency, devices and which visitors are excluded, because those settings live on each form rather than in one place, and they are the record of which shoppers each form was meant to reach.