Experience Journey Map

Experience Journey Map provides real-time insights into business and application performance, visualizing key user journeys and the correlation between performance and traffic. This perspective unifies all application stakeholders: application owners, developers, and IT operations.

Experience Journey Map visualizes:

Performance metrics for each step in a user journey
Top incoming and outgoing traffic data for each step
Drop-off rates

Learn about use cases for Experience Journey Map.

Requirements

To use Experience Journey Map, the following requirements must be met:

SaaS: Controller >= 20.6.0
On-premise: Controller >= 20.7.0
EUM Peak license (RUM Peak, Browser RUM Peak, or Mobile RUM Peak)
Instrumented browser or mobile application

Access Experience Journey Map

To access Experience Journey Map:

Under the User Experience tab, go to a browser or mobile app.
In the left application panel, click Experience Journey Map.

Experience Journey Map UI

The sections below provide an overview of the Experience Journey Map UI. In the Controller, click on the Legend for key terms.

Experience Journey Map Dashboard

The Experience Journey Map dashboard displays the top user journeys, or the most trafficked parts of an app. The default time frame is set to one hour, but you can adjust the time and the dashboard automatically updates the user journeys and data for that time frame.

End User Events

Each step in a user journey is visualized with an end user event. An end user event is a browser page or mobile view/activity. Experience Journey Map displays the most trafficked end user events.

Click an end user event to see:

Total user visits from all sources
Incoming and outgoing traffic sources
Performance breakdowns for each traffic source
Drop-off rate

Traffic Segments

A traffic segment connects two end user events and contains data about users who journeyed from one end user event to the next. Traffic segments display a health status icon for errors and exceeded performance thresholds. To edit performance thresholds, see Configure Experience Journey Map.

Click a traffic segment to see:

Number of users who came from the previously mapped end user event
Performance metrics for those users
Option to analyze individual browser or mobile sessions for that end user event

Experience Journey Map for Browser vs. Mobile Apps

The table below describes the differences in Experience Journey Map data for browser vs. mobile apps.

Component	Browser App	Mobile App
End User Event	An end user event shows data for one browser page. To customize end user event names, see Configure Page Identification and Naming.	An end user event shows data for one iOS view or Android activity. To customize how the mobile agent reports the view/activity names via the `SessionFrame` API, see the following: Customize the iOS Instrumentation Customize the Android Instrumentation Customize the Xamarin Instrumentation Customize the Cordova Instrumentation Hybrid agents (Cordova, React Native, and Xamarin) do not support individual screen tracking, which affects how Experience Journey Map displays events in a user journey. To ensure each screen is displayed in a user journey, we recommend using the `SessionFrame` API to define when a screen starts and ends. See documentation for each hybrid agent: Customize the Xamarin Instrumentation Customize the Cordova Instrumentation Customize the React Native Instrumentation
Default performance threshold metric	Performance thresholds (Slow, Very Slow, Stall, and Normal) are set to End User Response Time (EURT), or page load time.	Performance thresholds (Slow, Very Slow, Stall, and Normal) are set to the average time of mobile network requests.
Types of errors captured	JavaScript and AJAX errors.	Crashes and Application Not Responding (ANRs).
Analyze functionality	When you click Analyze, you are redirected to Browser RUM Analyze with filters applied for that mapped browser page.	When you click Analyze, you are redirected to Mobile Sessions with filters applied for that mapped mobile view/activity.
Misc.	Iframes are captured and included as a node with performance metrics, such as for SPA2 base pages.	You may notice that sometimes the metric breakdowns of performance thresholds do not add up to 100%. See Analyze Traffic for an example. This is because for mobile apps, performance thresholds are set to an average of only the network request(s) triggered from a view/activity. If the number of triggered network requests is less than the number of total network requests, the performance threshold breakdown does not add up to 100%.

Download PDF