User Paths is a feature that charts the user journey through your app based on the Custom Events you have tagged in your app. For all apps with Custom Events, Flurry automatically populates the User Path to help you visualize this progression.
Understanding User Paths is beneficial in a number of ways. For example, it can help you pinpoint bottlenecks, unused areas and exit points.
Example questions you can answer in User Paths in Flurry Analytics include:
- How do users navigate through my app? Are users taking the path I expect?
- What Events tend to be most or least frequently triggered by your users, and in what order?
- Where are there bottlenecks in the app? Do I need to modify a level in my game or a section in my app to ensure users can progress?
- What actions do my users typically take just before they exit the app?
- Given the most common user paths, where should I optimally locate ads or rewards?
An Example User Path¶
Let’s walk through an example User Path.
The first Event listed in User Paths in Flurry is always Start Session. This is the first action taken by any user of the app, regardless of whether it is a new or returning user or whether the app is starting fresh or returning from the background. Note that this Event is automatically generated by Flurry and does not need to be tagged in your app code. Similarly End Session does not need to be explicitly tagged.
After the start of a session, the some events triggered for this app are “search_term_started” and “carousel_moreimages_click”. As the UI only shows 5 boxes per row, the least common Events are bucketed together into “All Other Events” on the far right hand side. You are able to delve into these Events in the table format of this User Path below if desired.
To see how users progress beyond this first layer of Events, simply click on an Event name in the visual and the subsequent set of Events will appear. Here we see the breakdown of the sessions that began with the “search_term_started” Event. Percentage of the users, next triggered the “search_moreweb_click” Event. Some percentage of sessions end. This can be valuable information to a developer of what percentage of sessions end after simply viewing the main screen, and he might choose to make changes to try and minimize this occurrence. Note that the sum of the percentages in this row will add up to the value of the prior Event rather than 100%.
From here, you can continue clicking down one more layer if desired - User Paths allow you to look into four layers of Events at a time. You can also change the “root” Event (i.e. the Event at the top of the chart) in order to dig into more layers. To do so, click the small triangle at the upper right corner of the desired Event and the chart will update with this selected Event as the new root.
If you want to see more detail about the Events in your User Path, including those that have been bucketed in “All Other Events”, you can scroll down below to see the detailed view and corresponding statistics.
To manipulate this data, click on the “+” and “-“ symbols to maximize or minimize the level of detail shown.
One additional feature of Flurry User Paths is that you can filter the data shown in the chart and table by the version type of the app and a specific date range. This can allow you to understand, for example, if navigation flow changes based on a new feature that is launched. To look at a specific app version or date range, use the filters in the black bar at the top of the screen.