Demystifying user journeys: Revolutionizing troubleshooting with auto tracking

Alex Prokofiev23 Dec 2025

Problem

Grab developers needed to see what a user did before an issue appeared in the app. Their first attempt sent a clickstream event with every user interaction, but the app has hundreds of UI components and each developer had to instrument their own. Forgotten components left holes in the recorded journey, and the team kept patching omissions after they were found. Incomplete journeys slow troubleshooting and raise the mean time to resolution (MTTR).

Example from the article: a developer forgot to instrument one user interaction, and the recorded journey broke at that point.

Solution in brief

Grab built AutoTrack, an SDK that records three things on its own: the application state, every user interaction and the screen currently displayed. Because it hooks the platform's lifecycle and event-dispatch layer, no per-component instrumentation is needed. The captured journey is used to reproduce bugs, route issues to owners, generate UI tests and audit analytics events.

Questions this case answers
  • How to record a complete, gap-free sequence of user interactions in a client application when manual per-component instrumentation keeps leaving holes
  • How to capture a complete user journey in a mobile app without asking developers to instrument every UI component by hand?
  • How to reproduce a bug that a user hit somewhere on a long path through the app?
  • How to check that analytics events fire when and why they should?

Tools and methods

  • Application state tracking — foreground, background and launch source (icon, deeplink, push notification).
  • Interaction tracking — one hook in the platform event dispatch instead of per-component events.
  • Screen tracking — screen identity from view-controller and activity lifecycle callbacks.
  • Screen hierarchy snapshot — full view tree captured when a screen appears.
Continue reading — it's free

Google or a one-time email code. No password.