Teams shipping across Thailand often lose path continuity when users switch language mid-flow, hop to a bank app for payment, or resume on a different device after a commute.
Those gaps look like drop-offs in raw tools even when the user completed the journey. Path reports should call out known continuity breaks before anyone redesigns a step.
A useful first question: which events reset the session or user identity in your tracker? Until that answer is shared, path severity debates stay noisy.