4 November 2025 · Journal
What Thai product teams get wrong about bounce versus abandonment
Bounce is a landing-page idea inherited from acquisition analytics. Abandonment is a task idea. Mixing them hides month-end payment failures.
We still meet squads in Bangkok who report “bounce” on a logged-in bill-pay flow. The number comes from a web analytics property that was never retargeted after the product left marketing landing pages. Session Quality Analytics cannot use that number without laundering a definition.
Bounce
A bounce, in the old acquisition sense, is a single-page visit with no further hit. It says almost nothing about whether a returning customer failed to finish a transfer. It is also hostile to single-page apps, where “pages” are a fiction.
Abandonment
Abandonment requires a task model: started, completed, explicitly cancelled, or stuck. Explicit cancel is a success of sorts — the person was able to leave. Stuck is a quality failure. If your events cannot tell them apart, you do not have abandonment; you have a hole.
The Thai calendar problem
On salary days and utility due dates, payment switches slow down. People retry. Some close the app and open internet banking. Acquisition bounce rates spike. Actual task completion may hold. Teams that bonus on bounce then “fix” the landing experience while the switch timeout remains. Voice of Session exists partly to catch this mismatch between transcript (“I waited, then used the bank app”) and the bounce chart.
A working rule
Keep bounce, if you must, inside acquisition reports. For in-product Session Quality Analytics, name started, completed, cancelled, and stuck. If you cannot instrument cancel, say so in the charter. Do not relabel bounce as abandon to keep a historical chart alive.