Abandonment map
Web analytics taught a generation to treat “exit” as a personality trait. Inside a native or hybrid app, the shopper may have a wallet sheet open, a bank app in the foreground, or a process the OS just killed. This page is the map we use before we talk programmes.
Shipping surprises, login walls, and keyboard-unfriendly address forms live here. It looks like classic abandonment. It is still worth fixing, but it is not the leak most of our GB cohorts actually have when they arrive.
Wallet order, merchant identifiers, and silent failures sit here. Funnel tools often mark this as a successful checkout start. Native Checkout Recovery Studio spends two modules on this band alone.
3-DS, open banking, and SMS codes background your process. If persistence is weak, you converted a paying shopper into an empty cart. Cart Persistence for Mobile is the short programme aimed at this band.
Your API said 200; the UI never committed. Support hears “I paid twice”. Recovery surfaces have to name that state. Emailing a generic cart reminder makes it worse.
If you already know which band you are in, choose a programme. If you do not, send traces via contact and ask for a Desk Review. We will not invent urgency; the stalls in your logs are enough.