Field Notes
When the success toast lies about conversion
A checkout looked complete on screen while the backend order event never fired — how we untangled the mismatch during a Bangkok retail audit.
During a Full Funnel Audit for a retail shopping app, the product team was confident about their cart-to-order rate. The success toast appeared reliably in QA. Finance, however, kept asking why order counts in the warehouse lagged the analytics “purchase_completed” event.
We walked the Android guest path with a test card. The toast fired when the payment sheet closed, not when the order-created webhook returned. People who lost connectivity after the sheet closed still saw success copy. The event dictionary listed purchase_completed under “user-visible confirmation,” which matched the toast — and mismatched money.
What we changed in the report
We recommended splitting the taxonomy: a client-side payment_sheet_dismissed for UX debugging, and a server-confirmed order_created for conversion reporting. The toast copy moved to the true confirmation screen. Drop-off between sheet dismiss and order created became visible for the first time.
If your in-app conversion funnel analysis still treats a decorative success state as the business outcome, compare the toast timing to the webhook before redesigning the button labels.