Field note · 9 Dec 2025

Bilingual onboarding paths and the metrics they distort

Person holding a phone displaying charts

Many apps serving Thailand ship Thai and English interfaces. Users toggle mid-onboarding. If your events treat language as a static user property set at install, Customer Journey Analytics for Apps will blend two experiences into one misleading path.

Capture language as a moment, not a trait

Log language_at_event or screen_locale with each onboarding step. Compare completion conditional on toggle frequency. Heavy togglers often signal copy confusion rather than “preference.”

Design implication

When toggle-heavy users stall on the same screen in both languages, the issue is information architecture — not translation quality alone. Journey scorecards should separate those hypotheses.

Classroom tie-in

Retention Story Clinic uses a bilingual marketplace case to practice this split. Bring your own locale events if you join a Bangkok evening cohort.

← All field notes · Ask about clinics