Session length is a vanity metric in travel apps
A thirty-minute session on an OTA can mean a traveler found a fare. It can also mean they were stuck on a spinner in Suvarnabhumi with one bar of Wi-Fi. Travel App Analytics that celebrate longer sessions are borrowing a metric from news apps.
I still see weekly reports where “engagement” is average session duration, sometimes with a target that ratchets up each quarter. That target trains product teams to add screens, not to finish jobs.
Travel jobs are bursty
Planning a Bangkok–Chiang Mai weekend might take four short sessions across two days: search, compare hotels, check a train, pay. Day-of-travel use is even shorter: open boarding pass, check gate, close. If you average those into one duration KPI, you punish the day-of job — the one that actually determines whether the traveler trusts you next time.
Retention After the Booking exists because post-purchase opens are short on purpose. Calling them “low engagement” is a category error.
Airport Wi-Fi inflates duration
When a session stays open because the OS never backgrounded the app, duration climbs while the traveler is looking at a departures board, not at you. Without a foreground/background signal and a “meaningful tap” definition, you will congratulate yourself for dead air.
A more honest pair of metrics: time-to-first-useful-result on search, and time-to-pass on day-of. Both can fall while trust rises. That is the opposite of a duration target.
Comparison is not confusion — until it is
Multi-city comparison can look like a long, healthy session. Sometimes it is. Sometimes the traveler cannot tell whether a fare includes baggage and is looping the same three screens. Session length cannot distinguish those states. Search telemetry can: repeated identical queries, fare-rule opens, and back-taps on the same card.
If your schema cannot see those, do not publish duration as a success metric. Publish it as a diagnostic, if you publish it at all.
What to retire
Retire duration from executive dashboards. Keep it in a lab view for engineers hunting hung spinners. Replace the executive number with job completion: search that produced a bookable offer, checkout that produced a reservation, day-of open that produced a pass or gate update.
The studio programs spend almost no time on session length except to unlearn it. That is deliberate.