# Using User Path Analysis

## User Path Analysis Usage Tips

Insight Analysis and Funnel Analysis show clear values but make it difficult to **understand where users who did not convert went**. User Path Analysis is a feature that visually shows the paths users take within the service and the **drop-off and conversion rates along each path**, making it easy to understand the flow at a glance.

User Path Analysis **records all events triggered by a user within a single session**, and since paths are drawn based on this, it is best to select the event for the screen users first enter in the service. If there are multiple entry points like the home screen or product detail screen, you can select the `$session_start` (session start) event that Hackle auto-collects.

{% hint style="info" %}
Select the desired type to analyze the user's path.

* **Select steps manually**\
  Select analysis steps manually to view the subsequent journey of users who passed through those events.
* **Reverse flow analysis**\
  Select the final event in the user journey to view the preceding journey.
  {% endhint %}

### 1. Product Acquisition

#### What actions do users take most often after accessing the app?

You can use User Path Analysis not only to check conversion/drop-off rates and their magnitude for a specific event, but also to view the flow following a single specific action such as app access, login, or sign-up. This is because even if you select only one event such as app access in Step 1, the next events users performed the most and the drop-off rates are automatically displayed.

* **View data**

As shown in the example image below, simply selecting the session\_start event lets you see at a glance the types of actions taken most often after app access along with their conversion/drop-off rates. The widest flow represents the most users converting to the next event.

![](/files/jDCNb2j48HCtwIRzp9L5)

### 2. Product Usability

#### What did users who dropped off from the main behavioral flow (product click > add to cart > place order) do?

* **Set analysis steps and interpret data**

As shown in the example below, configure the service's key behavioral flow (Critical Path) as analysis steps: app entry > product click > add to cart > checkout click. In the Select Steps Manually section:

You can see that 20% of users who entered the service clicked on a product right away, while 20% clicked on search, etc., giving you visibility into what percentage of users do what in the second step.

By selecting events this way, the next events users performed the most and the drop-off rates are automatically displayed. Setting up to the final purchase completion step lets you view the conversion and drop-off of the entire purchase journey at a glance.

![](/files/9iOZWyx1YCvXmFyKAewE)

### 3. Payment/Revenue

#### What actions did users take after receiving a coupon?

You can use this when viewing the behavioral flow of a specific user segment through User Group configuration. Set a user behavior event or property in User Groups and check the user path those users took.

* **Set analysis steps and interpret data**

As shown in the example image below, manually select steps in `Analysis Steps`. Let's configure the flow: after viewing \[Product Detail Screen], going to \[Order Form] and \[Purchase Complete]. In `User Groups`, set users who received a coupon. Let's set users who received a coupon via an in-app message. (Users who clicked \[In-App Message Button] at least once within the last week)

You can see the flow from a user who received a coupon to actually placing a product order. Using this flow, you can improve the cart screen, improve related UX, and gain insights for improving the service and user experience.

![](/files/5nyen1mwtiZf3BDrcHiB)

#### What actions did users take before making a purchase?

Through Reverse Flow Analysis, you can see what actions users took before performing a specific action.

* **Set analysis steps**

As shown in the example image below, select the `Reverse Flow Analysis` type from the upper right of the analysis steps, then select only the order\_complete event. You can see at a glance the types of actions taken most often before purchase, along with their conversion/drop-off rates.

You can also set additional User Groups to check the reverse flow analysis for a specific user segment.

![](/files/OXxQDhcPknOGDJUJyJWK)

By adding steps, you can check up to 5 steps before the final step order\_complete.

![](/files/d2VibWmSWbJ4LIGM8f2R)

* **View data**

As shown in the example image below, after selecting the order\_complete event and adding steps, you can see at a glance the actions users performed most often before payment completion, and where they converted from or dropped off. Based on this user path chart, you can analyze user behavior at each step in more detail to gain insights for improving purchase conversion rates, such as improving the cart screen and running relevant CRM campaigns.

![](/files/xpvrKPlpueQZ2UzrihmF)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.hackle.io/en/data/analysis-tips/step-by-step-user-path-analysis.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.