This document is an introduction to Quick Tracking and technical integration and is not used as a sales basis. For specific products and technical services purchased by an enterprise, the commercial purchase contract shall prevail.
Overview
A path refers to a series of behavior sequences of users using a product.
Path analysis presents the user's usage path in the product with a Sanji diagram to show the user's traffic trend in event triggers and page flows. Path analysis can help enterprises verify product operation strategies and optimize product design ideas. After the path analysis query, you can save it as a report and add it to the self-made dashboard for display.
Retaining: refers to continuing to access other steps (events) backward from this step (event)
Churn: refers to leaving the application after the step (event) from
Applied scenarios
Path analysis can solve
Visualize user log data and mine the paths frequently accessed by users during product usage.
Verify operational thinking and see where users are actually going after deviating from the intended path
Take 「View the Main Path Destination after the User Opens the Application」 as an example
Select All Events as the analysis event range.
Select Start Event as 「Application Startup」
Click 「Start Analysis」
4. In the analysis icon, click 「Time Range」 to select the time range to query.

Actions guide
Page composition
The path analysis function, which mainly consists of the following parts


Information configuration area: the user can define the path, and time selection operation selection.
Interface composition analysis result area: users can view the visualization chart after analysis results.
Actions guide
Define analysis scope and path

1. Select the analysis scope
「Filter or Group」 to filter attributes after selecting the analysis scope
2. Choose an event as the 「Start (or End) Event」, Start is selected by default.
3. The user path is based on the session period set by the user, and a series of user behaviors that occur on the product during the session period.
Add global filter

4. Session interval: You can customize the session gap. If the interval between the newly reported event and the previous event exceeds the set session interval, the previous session is ended and a new session is created. The newly reported event is the first event of the new session, and the previous event is the last event of the previous session.
Different filter symbols are supported based on different types of attributes.
Attribute type | Filter symbol | Symbol definition | Example |
String | Equal to | Represents equal to one or more specific values | The device brand is equal to Huawei or Apple |
Not equal to | Identifies the exclusion of one or more specific values | Device brand excludes Huawei or Apple | |
Contains | Find values that contain certain characters in an attribute value | The character Huawei is included in the device brand | |
Does not contain | Exclude values with certain characters in attribute value | The character Huawei is not included in the device brand. | |
Empty | Find data with no property value | with device brand attribute value | |
Not empty | Find data with property values | No device brand attribute value | |
Numeric types | Equal to | Equal to a specific data | Order amount equals 1000 |
Not equal to | Not equal to a specific value | Order amount not equal to 1000 | |
Greater than | Greater than a specific value | Order amount not equal to 1000 | |
Smaller than | Less than a specific value | Order amount less than 1000 | |
In... with... | Between two specific values | Order amount between 1000 and 5000 |
2.3 Select time range

You can select the time range and time granularity as required. You can select a time range in the 「Relative Period」 or 「Fixed Period」 mode. In the Relative Period mode, the default time is set to the past seven days and is displayed by day.
The 「Relative Period」 of time is based on the date range pushed forward or backward by an anchor point, which will change with time. There are three dimensions of the past X days, weeks, and months. You can also customize the time filter conditions for the past X days, weeks, and months. The day is a complete natural day, and the week is selected from Monday to Sunday, and the month is the natural month (from the 1st to the last day of each month)
The following list describes the rules:
A. Past n days: Push forward the complete n days based on the current time.
B. Past n weeks: Push forward n complete weeks based on the current time. If the current time is the last day of the week, the past n weeks include the week in which the current time is located. Example: If the current time is the 7.20 (Tuesday), then the past week is 7.12-7.18 (Monday to Sunday). If the current time is the 7.18 (Sunday), then the past week is 7.12-7.18.
C. Past n Months: Push forward n complete months based on the current time. If the current time is the last day of the month, then the past n months include the month in which the current time is located. Example: If the current time is 7.20, then the past month is 6.1-6.30; If the current time is 6.30, then the past month is 6.01-6.30.
「Fixed Period」 You can directly select the start date in the calendar box, and click OK to select the current time range for data analysis (there is no time range limit for a fixed period).
View analysis charts

The analysis results are displayed in the Sankey graph format. You can view the follow-up /pre-path based on the specified start and end events. At the same time, you can hover a specific node to view the flow of a node event in detail. Click 「View Details」 to pop up the data details page. You can view the detailed data of the number of visits, retention, and loss of each event /page. The top 5 pages are displayed by default in the subsequent /preceding steps. To see more, click Other. Currently, only four steps are supported. A maximum of 10 nodes can be displayed at each layer. You can customize nodes.
Computing logic
Path analysis supports custom session interval calculation within 1 to 2880 minutes. From the beginning of the session interval to the end of the session interval, the events triggered by the user are sorted by local time, and the obtained behavior sequence is the complete path of the user within the session interval. For example, we set the session interval to 30 minutes: Xiao Ming's chronological sequence in a session interval is A- >B->C->D->E->C, Xiao hong's chronological sequence in a session interval is A- >F->E->C->E, then we can obtain the user's complete path data of the application as follows:
The actual user behavior path is much more complex than the above schematic diagram, often with multiple starting points and multiple ending points. We can easily get lost in the analysis and cannot obtain useful information. The regular analysis idea is generally to fix the starting point, explore the user's follow-up path, optimize the distribution efficiency of the starting point, or fixed the end point, explore the user's pre-order path, optimize the efficiency of the end point. Still according to the above example, we want to know to take c as the starting point to view the user's behavior path, then Xiao Ming's path is C- >D->E->C, Xiao hong's path is C- >E, and the obtained path diagram is as follows:

The actual user behavior path is much more complex than the above schematic diagram, often with multiple starting points and multiple ending points. We can easily get lost in the analysis and cannot obtain useful information. The regular analysis idea is generally to fix the starting point, explore the user's follow-up path, optimize the distribution efficiency of the starting point, or fixed the end point, explore the user's pre-order path, optimize the efficiency of the end point. Still according to the above example, we want to know to take c as the starting point to view the user's behavior path, then Xiao Ming's path is C- >D->E->C, Xiao hong's path is C- >E, and the obtained path diagram is as follows:

Sometimes, in order to focus more on the important nodes we care about, we will eliminate some interfering nodes. In the above example, node E is only a background event. This node has no substantive significance to my analysis. Therefore, we eliminate it. The path diagram obtained after eliminating node E is as follows:
