The General section of the System Profile - User Experience includes settings that affect visit and user action creation.
|Capture the following percentage of visits.||Enter a percentage of visits to be captured. For example, if you enter 10, AppMon captures only each 10th visit to your web site. Typically there is no need to change from the default 100%.|
|Capture all server side||Select this check box to capture server-side PurePaths even when the corresponding visit is not captured.|
|Visit ends after user is inactive for X minutes||Lets you configure the time until a visit times out. Visit-based business transactions are calculated and stored in the performance warehouse only after a visit times out.
A visit ends after 8 hours or if they contain 1000 user actions. New user actions then create a new visit.
|Visit tag||List of measures, used for visit tagging. See the Visit tag section below for more info.|
|Conversion goal||Lets you set conversion goals used to count visits as converted. To define a conversion, use a URI web request matching pattern, a method occurrence, or any measure trigger.
Configuring conversion goals is especially useful with e-commerce business applications where the conversion rate (spectator or buyer ratio) should be calculated. For example, if your web-site calls an
After you define at least one measure, you can use the Visits - Conversion Rate measure (which indicates the conversion rate of any of the conversion measures) and consequently, the conversion count of your visits. There is a separate conversion rate measure created for each measure that is assigned as a conversion measure that only indicates the conversion rate of this specific conversion measure. Default names of these measures are Conversion Rate for <conversion measure name>, but you can rename them as you want.
A visit tag is a specially configured measure, which you can use to mark a certain visit. When the threshold of the measure triggers, the measure value is assigned to the visit.
The tag is set only once per visit, so once a valid tag value is determined, it does not change with the re-occurrence of the measure.
For example, if the user name is stored in a session attribute, you can use a Web Requests - Session Attribute Value measure to tag visits with the username. You can use all measures from the Business Transaction Evaluation/Filter/Grouping Values category.
You can configure any number of visit tags, but one tag must be configured to act as the primary visit tag. It is displayed in the visit name, and in the Visit tag column of the Visits dashlet and the Visits web view. You can also find the visit using the value of this tag. Select the Is primary check box for the required visit tag. All other tags then act as additional tags and can only be viewed in the Visit details web view.
The following visit tags are configured:
The easyTravel Login Backend is capturing the user name on login. It is the primary tag, so the username will appear in the name of the visit.
The Loyalty Status is capturing the loyalty program status of a logged user (if any). This tag is not primary, so it is only visible in visit details.
The visit in the Visits dashlet:
The visit in the Visits web view:
The visit in the Visits details web view:
User Experience Index
Use this section to customize rules that calculate the user experience index of visits.
|Visit is tolerating if number of satisfied actions is less than||If the percentage of satisfied actions in the visit falls below this threshold, then the visit is marked as Tolerating. The default is 50%.|
|Visit is frustrated if number of frustrated actions exceeds||If the percentage of frustrated actions in the visit meets or exceeds this threshold, then the visit is marked as Frustrated. The default is 50%.|
Action groups are a good way to define individual performance baselines for different types of user actions. A new system profile contains six predefined action groups, one for every action type. You can also define custom action groups, such as one that groups all search actions into a custom group defined by a specific threshold. Every user action is assigned to one group by evaluating the action group list from top to bottom.
Action group configuration
- Based on their name.
- Starting or ending on a specific page by title or URL.
- Based on their XMLHttpRequest URL (Ajax Action groups only)
The baseline is the key performance metric used to determine Apdex rating to apply to each action in the each action group. You can set the performance metric for custom action group, or change the performance metric used for any predefined action group.
To do this, select the action group to be configured and click the Edit button in the Action Group button bar. Then in the Action group configuration dialog box, select the desired metric from the list. Only the performance metrics applicable to the action group type appear in the list.
The performance metric displays in the user actions data in both the client and AppMon Web.
As shown in the following images:
- Actions for the Ajax action type can be grouped by XMLHttpRequest URL.
- Actions for the mobile ADK action type can only be grouped by name.
Action group advanced configuration
You can make additional configuration changes that apply across all of the selected profile's defined action groups. See Action groups advanced configuration to learn how.
Using multiple performance baselines in action groups
Action groups and individual baselines appear in the User Action PurePath dashboard details.
On the User Actions dashboard, actions display by action group