Use the Visits dashlet to analyze visits that experience slow response times or errors.
The Visits dashlet is divided into two sections: A visits list and a details section that shows the statistics of a group of selected visits or the click path of a specific visit.
The following table describes the visit metrics:
|User Experience||Shows how users perceive the application performance. Visits fall into three categories: satisfying, tolerating and frustrating.
Users have a frustrating experience if one of the following occurs:
|Apdex||The Apdex rate for the pages that a visitor viewed. Apdex (Application Performance Index) is an open standard that defines a method for reporting and comparing website performance.|
|Visit Duration||The duration of a user activity on the page. You can limit the visit length in General settings section of the System Profile - User experience.|
|User Actions||The number of user actions that are executed, grouped by visitor or client type. Typically, visitors use several user actions, like those listed in Click Path below.|
|Failed Actions||Shows how many user actions are marked as failed. A user action can fail based on error rules.|
|Exit Action Failed||Indicates if the visitor's exit action failed.|
|Bounce Rate||Shows the percentage of visitors who enter the site and leave (bounce), rather than continue to view other pages.|
|Visitor Tag||Shows the primary visit tag. See the Visit tag section below for more information. You can configure the visit tags in General settings section of the System Profile - User experience.|
|Bandwidth||Shows the users network bandwidth. You must enable bandwidth calculation in the System Profile.|
|Converted||Indicates that a visit meets a goal. To see these goals, go to System Profile Preferences > User Experience > application > General. This is important in an e-commerce scenario. A visitor becomes a customer when they complete payment services. However, conversion can mean any condition that is met, like account creation, login, or a search.|
|Converted by||Lists the names of the Measures that converts the visit. The single Measures are separated by a semicolon (;).|
|Streaming||Indicates the types of streaming media that AppMon consumes during a visit. This can be audio, video or audio+video.|
|Stream Count||Indicates the number of streaming media items that AppMon consumes during a visit. This can be audio+video.|
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:
Access the grouping modes from the toolbar. The Visits dashlet provides various structure modes:
- User Experience, User Experience Reason: Groups visits by the categories satisfying, tolerating or frustrating.
- ClientType, ClientFamily: Groups all visits by client family and client type such as desktop browser, mobile browser, or mobile app. It also includes version or device information. For example, a visitor who uses Mozilla Firefox 6 is grouped in Desktop Browser - Firefox - Firefox 6.0.
- Application: Groups visits by applications that the user configures in System Profile.
- Location: Groups visits by their identified geographic location. The groups are hierarchically divided into continent, country, region, and city. For example, North America, United States, California, Los Angeles.
- OS - Operating System: Groups by operating system family and version. For example, OS Family: Windows, Windows 7.
- No Grouping: A flat list of all visits.
Visits Details shows the client statistics for a group of selected visits or the click path of a specific visit.
The Visit dashlet displays two charts at the left. The pie chart displays the available client type distribution. The meter chart, below, displays the user experience distribution. These charts dynamically update if the visit list selection changes.
Click on a piece of the pie chart and two more pie charts appear that display the following:
- Browser or Device: Shows the distribution of recognized browser versions and devices.
- Bandwidth: Shows the measured bandwidth that the user experiences.
If you select a piece of these charts, they display that selection's user experience distribution. For example, you can drill down the user experience of the Firefox 16 browser version.
Configure the chart layout in the Browser Statistics tab of the dashlet properties.
The Click Path view shows all of a specific visit's user actions.
In addition to the visit's user actions it also shows web requests which belong to the visit, but not to user actions. These orphaned web requests are just captured as server-side requests and linked to the visit.
|Server Contribution||The time spent on the server to process requests with an immediate impact on the user action response time.|
|Network Contribution||The estimated time spent to transfer resources with an immediate impact on the user action response time.|
|Failed Actions||Displays the number of server side transactions that were marked as failed.|
The Visits Details section is also included in most report types sych as HTML and PDF, but it is not included in XML reports.
Custom filtering and splitting
To filter and split an expression, click Custom Query on the toolbar. Filter expressions support a Java-like syntax. To split an expression, use a comma-separated properties list. Press CTRL + SPACE for a list of available filter and splitting values. You can store favorite filters and splittings for future use.
Expressions support a Java-like syntax. The following tables describe constants and operators recognized within expressions:
|||, |, or, OR||logic or|
|&&, &, and, AND||logic and|
|!=, <>||not equals|
|<, >, <=, >=||relational operators for smaller, greater, smaller than or equals to, and greater than or equals to|
|=~, ~=||matches a regular expression (right hand side is a regular expression)|
|!=~, !~=, <>~||does not match (right hand side is a regular expression|
|like, LIKE||SQL style string match function using '%' as joker character|
ClientFamily = Firefox and ClientFamilyVersion = %4%: Filters a Firefox browser's user actions with a version string that contains the character 4.
URI = %booking%: Shows only user actions with a URI that contains the phrase booking.
Country, Region, City: Groups user actions by a geographical location hierarchy that begins with the user's country.
OperatingSystem: Groups user actions by the detected operating system.
Find a specific user
Use AppMon to identify visitors and get information about the related pages they visit. Choose Edit > Search in the menu or click User Experience > Customer Complaint Resolution > Search in the Start Center. Use the search dialog box options to search for a specific user. The search result generates the Visits dashlet in a flat structure. Use this to analyze the user's click path. Look at the actions that contain errors or slow response times.