User Path User Guide
Follow
Learn about the User Path Report feature
User Path is a feature that allows you to analyze user journeys to discover the optimal path to specific events.
Through User Path, you can gain various insights such as the following.
- What are the key touchpoints during the user's journey?
- When does a user abandon their cart, transaction, or payment?
- What does the user do after installing the app or after opening the app?
- What does the user do before making a purchase?
Preparing to use the User Path feature
The actions required to check the User Path report are as follows.
[[Quote:Information:Small]] App Developer
*
DFINERY
Android
SDK 2.1.3.0
version and above can be analyzed. [
Integrate with the latest Android
]
* DFINERY
iOS
SDK 2.0.0.0
version and above can be analyzed. [
Integrate with the latest iOS
]
[[Quote:Guide:Small]] Data analysis is possible from the point when the SDK version specified above has been updated or later.
Create User Path Report
1. Click the Create New Report button at the top right of the Analytics > Data Explorer menu.
2. When the DFINERY Report creation screen is displayed, select User Path under the Analytics section.
View User Path Report
Standard Event
* Select the event to be used as a reference.
* You can check the users journey by setting the steps before and after the selected event.
Item | Content | Note |
Reference event | Select the event that will serve as the standard. | |
Step Setting |
Set the number of steps before and after the reference event.
|
|
Set detailed analysis conditions | Applies only to the standard event. | |
(1) Analysis Conditions | Set conditions to exclude or include in the baseline event. | |
(2) Profile Conditions |
Set profile conditions to exclude or include in the reference event. (※ Custom profiles are available with Add-on) |
|
(3) In-App Attributions Conditions | It will be activated if the campaign-level conditions are set in the baseline event analysis conditions. |
Exclusion event
* You can exclude specific events within the user pass chart for analysis.
* When an event is excluded, the value of that event is not summed as Other or Drop-Off, but is summed with the event converted after the excluded event .
Additional Settings
Item | Content | Note |
Conversion calculation method |
Unique - Even if a specific user enters the inflow path multiple times during that period, it is counted only once. |
|
Total - If a specific user enters the inflow path multiple times during that period, all instances are counted. |
||
Event Detail Property | Analyze by segmenting into events/properties. | Maximum setting: 5 |
Datetime Conditions | Set period | |
Generic Conditions | The set condition applies to all events, including Standard Event. | Maximum setting: 5 |
※ Conversion Calculation Method
There are Unique and Total methods for calculating conversions between events.
-
Unique :
Even if a specific user enters the referral path multiple times during that period, it is
counted only once
.
(In case of multiple entries, only the first session entered is counted .) - Total: If a user enters the referral path multiple times during the period, all sessions are counted .
If a specific user enters twice with the entry journey of Session 1, Session 2 within the set period as specified above, the unique calculation method and the total calculation method are as follows.
* Unique calculation method
-
Only count the first session entry
.
(Even if there are multiple entries, only the first session entry is counted.) - Count the events before ( e0 ) and after ( e1 ) the baseline s(0) event as 0 Step .
* Calculation method for Total
- If you run a session more than once, it counts all session entries .
-
Count the first entry
that triggers
session 1
.
-> Count before ( e0 ) and after ( e1 ) based on the s(0) event.
-
Second Entry
is triggered in
Session 2
and counted based on
the reference event
s(1)
.
-> Count the events before ( e2 ) and after ( e3 ), and s(2) , ( e4 ) based on the s(1) event.
-
3. Second Entry
is counted based on
Session 2
which triggered the
reference event
s(2)
.
-> Count is based on the s(2) event: before ( e2 ), s(1) , ( e3 ) and after ( e4 )
(4) Data Visualization
Item | Content |
Number of step-by-step event notations |
Set the maximum number of events displayed on the screen step by step.
(This excludes Other Events and Drop-Off.) |
Chart colors | Set the default color of the chart. |
Connection line transparency |
Set the transparency of the line connecting between events. |
Drop-Off Color | Set the color for Drop-Off. |
Top Path Highlights |
The highest conversion rate in the chart is highlighted by default. |
Top Path Highlight Color |
Set the color of the Top Path separately. |
Constraints
Item | Value |
SDK version |
- Android : Version 2.1.3.0 or higher - iOS : Version 2.0.0.0 or higher |
Reference Event | Select one |
Step Setting | Previous, Next: Up to 10 each can be set |
Profile Conditions | Custom profiles are available when using Add-on |
Number of events per step | Up to 10 settings can be configured |
Event Detail Property | Up to 5 settings can be configured |
Maximum rows displayable in the chart | Up to 100,000 lines |
Is there anything in the guide that you don't understand?
Please feel free to contact the Definery Customer Success Team (
dfn.tw_csm@igaworks.com
) :)