We implement User Journey Mapping at the data level: we instrument navigation, build path analysis in Amplitude or Mixpanel, and identify bottlenecks that a UX designer cannot see. A typical situation: a designer created a 4-step onboarding, developers implemented it. Analytics reveals that 40% of users leave for settings on step 3, return, and then finish the onboarding. Nobody tested this edge case because they didn't know about it. Journey mapping uncovers it.
Why Standard Funnels Are Not Enough
Sequenced event funnels in Firebase, Amplitude, or Mixpanel only show a predefined sequence. They miss unplanned paths and don't see where users come from at each step. As a result, you know that 60% reach the payment screen, but you don't know that 20% of them arrived via push notification, not through the cart. Sankey diagrams and path analysis solve this: they display all possible transitions between screens without scenario restrictions. This reveals unexpected routes that become drop-off points.
How to Instrument Navigation for Accurate Data Collection
Every screen and every meaningful transition must be logged with context — the source and the element that triggered the transition. Without this, you know the user was on ProductDetail, but not where they came from.
// Android — tracking transition with context fun navigateToProduct(product: Product, source: ScreenSource) { analytics.track("screen_viewed") { put("screen_name", "ProductDetail") put("product_id", product.id) put("source_screen", source.screenName) put("source_element", source.element) } navigator.navigate(R.id.productDetailFragment, Bundle().apply { putString("product_id", product.id) }) } // iOS — navigation tracking with source enum NavigationSource { case searchResults(query: String, position: Int) case recommendations(algorithm: String) case pushNotification(campaignId: String) case deepLink(url: URL) } func openProduct(_ product: Product, from source: NavigationSource) { var properties: [String: Any] = [ "screen_name": "ProductDetail", "product_id": product.id ] switch source { case .searchResults(let query, let position): properties["source"] = "search" properties["search_query"] = query properties["search_position"] = position case .recommendations(let algorithm): properties["source"] = "recommendations" properties["rec_algorithm"] = algorithm default: break } amplitude.track(eventType: "screen_viewed", eventProperties: properties) } Route Segmentation Improves Analysis
Without segmentation, the path map shows an average path that doesn't exist for any real user. Important slices:
- By installation source: organic vs paid — conversion may differ by 2x
- By device type: tablet users are 30% more likely to use landscape mode
- By cohort: new vs returning users — day 7 retention differs by 15%
- By plan: free vs premium — browsing depth is 3x higher for premium
# Amplitude API — get User Paths with segmentation import requests response = requests.post( "https://amplitude.com/api/2/path", auth=("API_KEY", "SECRET_KEY"), json={ "start": {"event_type": "onboarding_started"}, "end": {"event_type": "subscription_started"}, "segment_definitions": [ { "name": "New Users", "filters": [ {"subprop_type": "user", "subprop_key": "new_user", "subprop_op": "is", "subprop_value": ["true"]} ] } ], "e": { "event_type": "any", "filters": [] }, "n": 8 } ) Tool Comparison for Path Analysis
| Tool | Analysis Type | Segmentation Depth | Setup Complexity |
|---|---|---|---|
| Amplitude Pathfinder | Sankey + arbitrary paths | High (user properties, event properties) | Medium |
| Mixpanel Flows | Automatic flows | Medium (filters) | Low |
| GA4 User Explorer | Linear paths | Low (only predefined segments) | Low |
Amplitude Pathfinder wins on analysis depth: it allows building paths considering any event and user properties, speeding up anomaly detection by 2-3 times compared to Mixpanel Flows.
Automatic Segmentation Speeds Up Analysis
Manual cohort labeling is time-consuming. Modern tools like Amplitude Pathfinder or Mixpanel Flows offer automatic path building with configurable filters. This reduces initial analysis time to 30 minutes instead of 2-3 hours of manual log digging.
Benefits of Automatic Path Map Building
Automation allows:
- Identifying non-obvious dependencies between screens
- Detecting recurring drop-off patterns
- Comparing cohort behavior without writing complex queries
In one project, automatic path building revealed that 25% of users after registration immediately hit an error screen due to an outdated token. This was fixed in one sprint, increasing subscription conversion by 12%.
Key Metrics on the Path Map
| Metric | What It Shows | Normal Value |
|---|---|---|
| Drop-off rate | % of users leaving a screen | <20% for key steps |
| Loop count | Average number of returns to previous screens | <2 |
| Dead-end ratio | % of sessions ending on a screen without CTA | <5% |
| Path diversity | Number of unique paths between two points | <10 for key scenarios |
Identifying Bottlenecks
After building the path map, we look for:
- Drop-off points — screens with abnormally high exit rates. For example, if 35% of users leave on the AddressInput screen, the form has a problem.
- Unexpected paths — transitions that shouldn't exist. If users go from Checkout back to ProductDetail, they have a question the checkout screen doesn't answer.
- Dead ends — screens from which users close the app instead of navigating further. Often error screens or empty states without CTA.
What Our Work Includes
- Designing a navigation event tracking schema with source_screen and source_element
- Setting up Path Analysis in Amplitude or Flows in Mixpanel
- Configuring segmentation for key cohorts (source, device, cohort, plan)
- Building main user journey maps: onboarding, conversion, retention
- Identifying top-3 drop-off points and generating hypotheses for A/B tests
- Documentation of the event schema and a report with interactive maps
Timeline and How to Start
Navigation instrumentation and basic journey reports take 2–3 days. Full analysis with segmentation and hypotheses takes 3–5 days. Cost is calculated individually.
Contact us for a consultation on your project. Get a preliminary estimate of work scope and timeline. Our experience: over 7 years in mobile analytics, 50+ analytics platform integrations. We guarantee quality instrumentation and transparent reporting.