They walked our onboarding screens step by step and marked where people stalled after OTP. The report named three drop-off points we had overlooked for months. Scheduling the kickoff took a week longer than I hoped, but the findings paid for the wait.
Client stories
Notes from product and analytics leads who brought us a stuck flow, an inconsistent event path, or a funnel that refused to explain itself.
Our checkout events were named inconsistently across Android and iOS. Dataenginebase rebuilt the path map so both teams finally spoke the same language. Quiet, careful work — not a flashy pitch.
We spent a half-day tracing how first-time bookers move from search to confirmation. I left with a whiteboard photo and a clear list of which events to fix first. Still waiting on their follow-up notes for the second session, but the live workshop was solid.
They challenged our assumption that the hotel filter was the problem. Path analysis showed the real leak was after date selection. That single correction changed how we briefed engineering.
I appreciated that they asked for raw session notes instead of polished slides. The audit tied qualitative friction to the exact event sequence in our learning app.
Extended story: OTP stall on a fintech onboarding path
A Bangkok fintech product lead asked for a User Journey Audit after activation stalled despite a “healthy” step-two conversion rate. We rebuilt the path from identity capture through OTP and first funded action.
Path clusters showed many users looping between OTP request and resend, then exiting after a long wait with no confirmation event. The loudest funnel step was not the true leak — confirmation latency was. The readout handed engineering a short list: emit a wait-state event, shorten resend cooldown copy, and measure time-to-code separately from form completion.
Three weeks later the team reported fewer support tickets about “stuck verification,” though they still needed a second pass on Android-only naming mismatches — work they covered in a follow-up Event Path Review.
Extended story: travel search filter assumptions
A regional travel brand assumed hotel filters caused drop-off. Funnel Path Assessment clustered successful and abandoned paths around date selection, guest count, and filter use. Successful bookers often skipped advanced filters entirely; abandoners frequently changed dates twice, then left.
The assessment memo redirected the next sprint toward date UX and calendar performance rather than filter redesign. The analytics manager later noted the brief helped quiet an internal debate that had run for two quarters.