Mobile User Journeys visualizes how end users navigate your mobile app in aggregate. It reveals patterns in user behavior — where users go after opening the app, where they get stuck, and which paths lead to the outcomes you care about.
重要
Mobile User Journeys is currently available within the Errors experience in the New Relic mobile monitoring UI. A standalone Mobile User Journeys view (similar to the Browser User Journeys feature) is planned for a future release.
How to access
Mobile User Journeys is available across all four sections under Triage in the left navigation: Crashes, Request errors, Handled exceptions, and ANRs. How you reach it depends on where you're coming from:
From the Triage tab:
- Go to one.newrelic.com > All capabilities > Mobile.
- Select your mobile application.
- In the left navigation, under Triage, click Crashes or Request errors.
- From the error groups, select the one you want to investigate to open the error detail view.
- In the detail view, click the User Journeys link to see the navigation paths that led to the error.
From the "Group crashes or error" tab:
- Go to one.newrelic.com > All capabilities > Mobile.
- Select your mobile application.
- In the left navigation, under Triage, click Crashes or Request errors.
- Click the Group crashes or Group request errors tab.
- Select the crash or error group you want to investigate to open the group detail view.
- Under Triage, click the User Journeys link to see the navigation paths that led to the error.
How to use Mobile User Journeys
Sankey diagram
The User Journeys visualization uses a Sankey diagram to show the flow of users between screens. Each node represents a screen or interaction in your app, and the width of each connecting path reflects the number of users who followed that route.
Key elements of the diagram:
- Nodes: Individual screens or interactions in the app.
- Paths: Connections between nodes, sized proportionally to the volume of users who followed that path.
- Entry points: The screens where user sessions begin.
- Exit points: The screens where users ended their session or triggered an error.
When viewed from within an error group, the visualization automatically anchors on sessions that experienced that error, so you can trace the navigation paths that preceded the crash.
Path and event details
Click any node or path in the diagram to drill down into the sessions that followed that exact route. This opens a split view with two panels:
- Profiles: Shows the distribution of attribute values (such as app version, device, OS, architecture, and crash details) across the sessions that followed the selected path. Use this to identify commonalities among affected users.
- Sessions that include this event: A table listing individual sessions, including User ID, date, occurrence count, app version, device, OS version, and carrier. Click any session to open the Event Trail Drilldown page.
Event Trail Drilldown
Click a session in the sessions table to open the Event Trail Drilldown page — a chronological timeline of every event recorded in that session.
In the Event Trail Drilldown you can:
- Filter by event type: Use the Interaction and Crash buttons to focus on specific event types.
- Expand event details: Click any event to see its full attribute payload — including crash metadata such as
diskAvailable,osBuild,processName,timeSinceLastInteraction, andinteractionHistory.
This view lets you reconstruct the exact steps a user took before a crash occurred, down to the individual screen interactions.
How to customize the visualization
Event type filter
Use the Event type filter to choose which event types appear as nodes on the diagram. You can include any combination of:
- Crash
- Breadcrumb
- Interaction
- User action
- Handled exception
- JavaScript error
- Request error
- Custom
- ANR
App version
Use the App version filter to focus on journeys from a specific release. This is useful for comparing user behavior before and after a deployment to identify regressions or improvements.
Filter by user attributes
Use the filter bar to narrow results by additional attributes such as device type, OS version, geography, or custom attributes you've instrumented with the Mobile SDK.
Related features
- Mobile crashes: View and triage crash groups across your mobile app.
- Handled exceptions: Track non-fatal errors and trends.
- Session replay: Watch recordings of real user sessions to understand exact user behavior.
- Browser User Journeys: The equivalent User Journeys feature for web apps monitored with Browser.