---
description: This document describes the use of path metrics and steps to create paths.
---

# Paths

Path Metrics is an effective analytical tool from Lemnisk that allows you to know your campaign performance and its engagement level by knowing every action performed by users _in between_, _before_ and &#x61;_&#x66;ter_ certain events. This supports knowing about the user actions across all data sources not limited to just App and Website and identifying the bottlenecks that deviate the users from achieving a certain event and drop off.&#x20;

Path Metrics will also support the business to identify the flaws in the architecture of their Website/Application and campaign performance and optimize it with precise data analytics rather than making decisions by guesswork. With this feature, businesses can gain promising engagements with proven records from the history of user behaviour.

{% hint style="info" %}
**Use Case**

Let's say,

As a marketer, you want to know the actions of the users and analyse where the major drop off and major conversion happens in your website/Application. Creating a perfect journey towards your end goal and analyzing the journey performance will help you to know your users better and support you in improving your campaign performance. This will also help to architect a better website or application that directs the users towards reaching the end goal without any deviations.

Let's assume you are a marketer of an e-commerce business and you want to know at which point the majority of users get dropped off. You can configure the journey with multiple events like`productVisited`,`added to wishlist`,`Checkout` etc. If there occurs a major dropoff after the event `product visited` or before `Checkout`, you can analyse the actions performed before after and between each event to get detailed insights into your user behaviour with the help of these path metrics and optimize your platform or marketing campaign for better traction.

It also supports you to gain answers to critical business questions like,

* _What are the activities performed by the user before attaining a certain event?_
* _When do users exit the Website/Application?_
* _How do users move from one step to another?_
* _When do users drop off before purchasing a product?_&#x20;
* _What makes a user uninstall the application?_
{% endhint %}

Before diving deep into the path let's know how to read the path by knowing its indicators.

## **Analyzing the Path Diagram**

<figure><img src="https://1782533751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FazJDZwzHkmWIbkYOetQH%2Fuploads%2FdIFr4LIOslPk7czXcdWs%2FDia.png?alt=media&#x26;token=7bcc32bc-68d1-4190-988c-49013cba4ba7" alt=""><figcaption><p><em>Image: Analyzing path diagram</em></p></figcaption></figure>

* **Event:** Each action configured in the path like, product visited, check out, drop off, etc.
* **Steps:** Number of actions performed by the user before, after or in between certain events, which is also a collection of events.&#x20;
* **Node:** Each event is a node, hovering over each node will show the number of drop-offs and the next steps with its counts and percentage.
* **Path:** Path is the direction the user took from one event to another event in another set of steps. hovering over the path will show the direction of each path from one step to another.

## Steps to plot the path

**Go to > Analytics > User Journey > Path**

**Step 1:** Select a path metrics chart that needs to be plotted down. You can Plot the paths **Before an Event**, **After an Event** or **Between the Events**.

* **Before an Event:** The plot will be shown before a certain event. The steps will be calculated from the point before the particular event.
* **Between Events:** The plot will be shown from one event to another. The steps will be calculated between those events.
* **After an Event:** The plot will be shown after triggering a certain event. The steps will be calculated from the point the event is triggered&#x20;

**Step 2:** While choosing path metrics as **After an Event** in Step 1, Select the path you want to plot from **Show all paths starting with**. These paths can be configured by the marketer based on the website/Application.&#x20;

* If you choose **Between Events** in Step 1, Then you must select Events from **Show All Paths starting with** and the Events from **Show All Paths ending with.**
* If you choose **Before an Event** in Step 1, Then you must select Events From **Show all paths ending with** to plot the charts.

<figure><img src="https://1782533751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FazJDZwzHkmWIbkYOetQH%2Fuploads%2Fe9ZrgIqdwH4In39LtGZP%2FLemniskApp-GoogleChrome2024-01-1015-34-35-ezgif.com-censor.gif?alt=media&#x26;token=53b72575-6004-40c0-90fc-ec7b59320052" alt=""><figcaption><p><em>Image: Filters</em> </p></figcaption></figure>

## **Filters**

You can plot the Paths by filtering the data based on URL to segregate precise data as required&#x20;

## Case 1: Filter event based on URL

In this use case, we plot the path After an event Productviewed and filter it with the URL that includes Insurance.

Clicking on the filter icon beside the event will pop up the following Input window where you can filter the the path based on URLs

<figure><img src="https://1782533751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FazJDZwzHkmWIbkYOetQH%2Fuploads%2FjCC7j6qZHICUqqIKMEWf%2Fimage.png?alt=media&#x26;token=712272bb-8abd-4f76-b46a-79b61939660a" alt=""><figcaption><p><em>Image: URL filters</em></p></figcaption></figure>

The path will be plotted for the applied filters as shown below.

<figure><img src="https://1782533751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FazJDZwzHkmWIbkYOetQH%2Fuploads%2FwCGMlthyXY7ddAGMYTJ1%2Fimage.png?alt=media&#x26;token=759a1dbb-8885-48d4-8c7f-00dd5c070299" alt=""><figcaption><p><em>Image: Paths based on URL filters</em></p></figcaption></figure>

**For events Open, Click and Impressions you can filter the paths based on Browser, Segment and engagement as follows. These events were tracked from Lemnisk's** [**Engagement.**](../channels/external-api/create-engagement)

### **Case 2: Event `Engagement_Open`**

In this use case, we select the following event combination to plot the path based on engagement level and filter it in browser level.

1\) **`Engagement_Open`** from the drop-down in **Event 1.**

Click on the **Filter Icon,** select **Add filter** and apply the filters as follows

<figure><img src="https://1782533751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FazJDZwzHkmWIbkYOetQH%2Fuploads%2FxmuzIh7RAk2GrDWe5NRB%2Fimage.png?alt=media&#x26;token=40730415-a379-4d83-b1a5-31a24616b9b1" alt=""><figcaption><p><em>Image: Apply Filters</em> </p></figcaption></figure>

**Property:** Browser&#x20;

**Operator:** Contains&#x20;

**Input:** Chrome&#x20;

The Paths will be plotted as shown below,

<figure><img src="https://1782533751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FazJDZwzHkmWIbkYOetQH%2Fuploads%2Fzknhheli9h9OGVuqZ3Qx%2Fimage.png?alt=media&#x26;token=ee760835-8bd2-404f-87a7-ef7525608b9f" alt=""><figcaption><p><em>Image: Paths</em></p></figcaption></figure>

**Step 3:** Select the window period from **Within the window of**. In this demo, we selected "one day".

For example, if you choose within starting event as `ProductVisited`and **within the window of** "1 day " and the time frame as "Last 90 days" " it will show the actions performed by the user within a day from the selected event in the "Last 90 days".

**Step 4:** Select the time frame in the field **During.** Here we have selected the time frame for the "Last 90 days".

**Step 5:** Select the number of steps that you want to know before any certain event. Here we selected "10 steps". you can choose up to 15 steps.

**Step 6:**  Select the **Other Events threshold**. Here we selected "5%" as the threshold limit. Event threshold helps you to group multiple events with the least traction together that eventually fall under **others**. This grouping supports concentrating on signals rather than noise. you can set the threshold limit which should be at least 5 percent and maximum up to 20 per cent.

**Step 7:** Include and exclude events as per your data requirement.

**Include Events:** This allows you to add events to the path.

**Exclude Events:** Allows you to remove events that are not necessary for your data segregation

<figure><img src="https://1782533751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FazJDZwzHkmWIbkYOetQH%2Fuploads%2FNXJQLcwW2oiLjF9Uh6oQ%2Fimage.png?alt=media&#x26;token=63295bad-b3bf-4c7f-a9cd-8b489d23b9c5" alt=""><figcaption></figcaption></figure>

**Step 8:** Now click **Plot the chart.**

### **Plotting Paths After an Event**

<figure><img src="https://1782533751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FazJDZwzHkmWIbkYOetQH%2Fuploads%2FXAzih3bJeJH9OtkHLJWi%2FLemniskApp-GoogleChrome2024-01-1017-27-012-ezgif.com-censor.gif?alt=media&#x26;token=694b62f7-20ee-424b-8121-5c9b528f6558" alt=""><figcaption><p><em>GIf: Ploting paths After an event</em></p></figcaption></figure>

In the After Event, we show **Drop off** node at each step. This represents users who dropped off after performing the particular event(s) at that step. This gives you a clear understanding of where most of your users are dropping off and you can target them accordingly.

**Hovering over Nodes and Paths**

*   **Nodes:**

    Hovering over each node in **After events** will show the number of dropoffs and the next paths with their counts and percentages.

<figure><img src="https://1782533751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FazJDZwzHkmWIbkYOetQH%2Fuploads%2F4FlkVEhuoQkPwAHAFfwu%2FNode-After%20event%20.png?alt=media&#x26;token=57956d8b-c8c1-4813-8353-3b77bc4a3c9c" alt=""><figcaption><p><em>Image: Node stats</em></p></figcaption></figure>

*   **Paths:**

    Hovering over each path in **After an Event** shows the next steps the user made from one node to another along with dropoffs.

<figure><img src="https://1782533751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FazJDZwzHkmWIbkYOetQH%2Fuploads%2FMd1CwaUMfz7CSaFUNqfH%2Fpath-%20after%20event%20.png?alt=media&#x26;token=a29a4422-3836-41e3-990f-5023dea995b8" alt=""><figcaption><p><em>Image: Path stats</em> </p></figcaption></figure>

### **Plotting Paths Before an Event**&#x20;

<figure><img src="https://1782533751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FazJDZwzHkmWIbkYOetQH%2Fuploads%2F8y1SOZ7e1dOzBNHKkmTR%2FLemniskApp-GoogleChrome2024-01-1017-56-48-ezgif.com-censor%20(1).gif?alt=media&#x26;token=1bb33e26-5e19-42a9-8366-ec9daaf7c6c8" alt=""><figcaption><p><em>Gif: Plotting paths Before an Event</em></p></figcaption></figure>

In the Before Event, we show the **Entry** node at each step. This represents users who directly entered the step instead of traversing from the previous step or path. This helps you understand the different touchpoints from where the users are coming directly instead of the intended path.

**Hovering over Nodes and Paths**

*   **Node:**

    Hovering over each node in **Before an Event** shows the number of entries and the path from the previous steps with its count and percentage.

<figure><img src="https://1782533751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FazJDZwzHkmWIbkYOetQH%2Fuploads%2F4eFOjQ4fILJESnNhmmkN%2FNodes-%20before%20Event%20.png?alt=media&#x26;token=4baef210-5b50-4f40-bae9-a1b195d6ef12" alt=""><figcaption><p><em>Image: Node stats</em> </p></figcaption></figure>

*   **Paths:**

    Hovering over each path in **Before** **an Event** shows steps the user made from one node to another from their entry points along with its count and percentage.

<figure><img src="https://1782533751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FazJDZwzHkmWIbkYOetQH%2Fuploads%2FuIP929V89ktfsCE6T5Vj%2Fpath%20-%20before%20events.png?alt=media&#x26;token=02820426-a293-4f4b-8b25-ae116d8d56b4" alt=""><figcaption><p><em>Image: Path stats</em></p></figcaption></figure>

### **Plotting Paths Between The Events**

<figure><img src="https://1782533751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FazJDZwzHkmWIbkYOetQH%2Fuploads%2FWsjuXvG6ejbBcNZpU8Jp%2FLemniskApp-GoogleChrome2024-01-1018-24-16-ezgif.com-censor.gif?alt=media&#x26;token=643710d7-2d15-4030-b5c5-dbf358293ae2" alt=""><figcaption><p><em>Gif: Plotting paths Between the Events</em></p></figcaption></figure>

In the Between Event, we show the exact path(s) that the user took between the two events, hence there will be no dropoff or entry node present.

**Hovering over Nodes and Paths**

*   **Nodes:**

    Hovering over each node in **Between Events** will show the number of users moved to the next step from any node with its counts and percentage.

<figure><img src="https://1782533751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FazJDZwzHkmWIbkYOetQH%2Fuploads%2FZ0zBVd0KeLoQTXHZn9xS%2FNode-between%20events.png?alt=media&#x26;token=6ef10dee-1051-4fbe-bfdb-c4e145e048c0" alt=""><figcaption><p><em>Image: Node stats</em></p></figcaption></figure>

*   **Paths:**

    Hovering over each path in **Between Events** shows the steps users made from one node to another except the dropoffs, with their counts and percentages.

<figure><img src="https://1782533751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FazJDZwzHkmWIbkYOetQH%2Fuploads%2FByrb3ABitThFdfP9Y8hl%2FPath-%20between%20events%20.png?alt=media&#x26;token=8af33d05-93de-41c7-8389-009935a2bf71" alt=""><figcaption><p><em>Image: Path stats</em></p></figcaption></figure>

{% embed url="https://drive.google.com/file/d/18SE75wqZAPHty-4mii7eFAB1lAEG3ny8/view?usp=sharing" %}
_Demo: Creating Paths_&#x20;
{% endembed %}

{% hint style="info" %}
You can add and remove the steps directly from the chart with the **+** and **-** icons at the top right corner of the window to get a clear view of each step and configure the plot as per your requirements. You cannot add or remove steps from the chart while plotting **between the events.**
{% endhint %}
