UBA (User Behavior Analysis)
* On-Premise only
Last updated
* On-Premise only
Last updated
IMQA MPM User behavior analysis can be tracked and queried how specific app users used the app. Through user information (identification information) linked to performance data, you can track the screen flow from the execution of the app to the end of the app of a specific user. Additionally, you can identify the cause of the problem in detail through detailed performance analysis based on the screen where the problem occurred. After entering user information, you can select a specific date and time zone to analyze user behavior flow based on the user's app start time.
For behavior analysis, you can analyze the behavior flow based on the user's app start time by entering user information and selecting a specific date and time zone.
The IMQA MPM UBA page consists of the following:
❶ User Information / Timeline ❷ User Behavior Flow ❸ Screen Flow
User Information
You can select the user information and date you want to view. View user behavior data by selected date and criteria.
❶ Select the user information you want to search. By default, it is set to 'User ID', and you can select 'User Email' or 'User Name'. In the SDK, you can set user identification information to identify specific app users. ❷ Select the date you want to search. ❸ When you click [Search], the data will be viewed as the entire app version with the selected date and user information.
For user information settings, refer to 'Android > Setting Crash SDK > Registering a custom user ID'
Timeline will be displayed if there is behavior data based on the selected date and user information for the entire app version.
❶ Change user information Change the user information you want to analyze. When selected, you will return to the ‘Behavior Analysis’ initial screen.
❷ Timeline You can change the date and time (in 30-minute increments) you want to analyze. View user behavior flows collected upon change.
❸ Date Click [<] [>] to change the inquiry date.
❹ Selected time zone Displays the selected time zone. You can change to a different time zone.
❺ Legend Displays color according to the presence or absence of behavior data for each time zone.
Based on the app start time of the selected user, it displays a screen flow from app start to app end. Refresh the user behavior flow by changing the app start time criteria.
❶ App Start Time By default, it is set to the ‘fastest start time’ among the user behavior data collected in the selected 30-minute time period. If the app has been launched multiple times within a 30-minute window, you can change the search criteria in the list. Show route summary when changes are made, and update the screen flow.
❷ Path Summary View Shows a summary of the selected user behavior flow. Displayed as App Start > Screen 1 > Screen 2 > … > App End,” and clicking [Screen Name] lets you view quickly where a certain screen is in the screen flow below.
Displays behavior data for the selected user as a screen flow. You can see the movement path of the native and webview screens that the user moved to, view Performance Information for each screen, and drill down into the cause of the issue with Detailed Analytics for each performance metric.
The screen flow is configured as follows:
❶ Screen Units Displays the native and webview screen units visited by app users. Shows step information, page visit time, and screen name. Long screen names can be shown in a tooltip that appears when you hover over it.
❷ Screen Type Icons are displayed according to the native, webview screen type.
❸ Show/Hide Performance in Screen Card Shows the performance metrics area when the screen card is clicked. Hides the performance metrics area when clicked again.
View performance metrics for several screens at the same time, allowing for before-and-after performance comparison analysis.
You can view the screen load time and min/max response time, and compare them with other screens for each screen visited by a user. Clicking each performance figure opens the Detailed Performance Analytics popup.
Rendering time: Displays the loading time of an N-th page in the screen flow. It will be marked with a red color if it is above a threshold.
Response time: Displays the min. and max. response times collected on an N-th page in the screen flow. It will be marked with a red color if it is above a threshold.
CPU: Displays the min. and max. CPU usage collected on an N-th page in the screen flow. It will be marked with a red color if it is above a threshold.
Memory: Displays the min. and max. memory usage collected on an N-th page in the screen flow. It will be marked with a red color if it is above a threshold.
| index | period | value | Merge method | unit |
|---|---|---|---|---|
UI Rendering Time | Specific screen | Native / Webview UI Rendering Time | Eigenvalue | ms |
Response Time | Specific screen | Native / Webview UI Response Time | Minimum, Maximum | ms |
CPU | Specific screen | CPU usage | Minimum, Maximum | % |
Memory | Specific screen | Memory usage | Minimum, Maximum | MB |
Through the behavior analysis function, you can check which performance problems a specific app user collected during operation experienced at what stage while using the app, and reproduce the user's movement path. Additionally, after checking the context based on the problem screen, you can use the ‘Detailed Performance Analysis’ function to identify the cause of the problem in detail.
Reverse Behavior Analytics can track a user on the selected device in the Detailed Performance Analytics popup in association with a flow of how they interacted with your application. You can access the performance information of devices that have experienced performance degradation and identify the route cause before and after the degradation. Click [User Behavior Analytics] to track a screen flow from the app start to app end of the user on the specific device through the “Behavior Analytics” page.
