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 columns in the visits pane of the Visits dashlet. Column names marked with ** are not displayed by default.
|Visit||Shows visits grouped according to the current grouping type. For each visit, the column shows any visit tag created for the visit, location (city and country) and device used to access the application. the name of the group of visits.|
|Count||The number of visits in the group. This number changes based on how visits are currently grouped in the dashlet.|
Users have a satisfying experience if one of the following occurs:
|User Experience Reason**||The reason why the user experience was assigned to this visit.|
|UE Index||The user experience index for each visit. Only shown for each current group.|
|User Actions||The number of end user actions performed a visit, or the total number of user actions in all visits in a group. Typically, visitors use several user actions, like those listed in Click Path below.|
|Application||The application associated with the visit.|
|Client Family**||Browser for web applications, and device name for mobile applications.|
|Client IP**||The IP address of the client.|
|Continent||The continent of the visit (either based on IP-address or on GPS-coordinates).|
|Country||The country of the visit (either based on IP-address or on GPS-coordinates).|
|Region||Either the state of the visit (for USA) or the name of the provincial area where the visit originated, based on the country's regional designations (either based on IP-address or on GPS-coordinates).|
|City||The city or nearest recognized city where the visit originated (either based on IP-address or on GPS-coordinates).|
|Start Time||The start time of the first user action.|
|End Time||The time when the visit ended due to either configured inactivity time or by an endVisit ADK call. Visit measures and business transactions are calculated and written to performance warehouse at this time.|
|Last Modified||The end time of the last user action or web request for the visit.|
|Visit Duration||The duration of the visit is measured from the start time of the first user action to the end time of the last user action or web request in minutes and seconds. An average value is displayed if visits are grouped. You can limit the visit length in the General settings section of the System Profile - User experience.|
|Failed Actions||Shows the percentage of frustrated (failed) actions versus the total number of actions in a visit, or in a group of visits, and the total number of frustrated actions (in parentheses). A user action can fail based on error rules.|
|Exit Action Failed||Indicates if the visitor's exit action failed. For visit groups, this shows the number of failed exit actions for the group (in parentheses), and the percentage of failed exit actions of the total failed exit actions.|
|Bounce Rate||Shows the percentage of visitors who enter the site and leave (bounce), rather than continue to view other pages.|
|OS Family||The type of the operating system on the device used for the visit, for example Windows, iOS, or Android).|
|OS Name||The specific name and exact version of the operating system on the device used for the visit.|
|Visit 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.|
|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.|
|Device Name**||The actual name of the device used to access the application during the visit.|
|App Name**||The application associated with the visit. This is typically the same data as the data in the Application column, however some mobile versions of applications may be named differently to distinguish from the version of the same application used on other devices.|
|Screen Resoution**||Pixel dimensions of the screen on the device used for the visit.|
|Manufacturer**||The manufacturer of the mobile device. Available only for mobile devices.|
|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.|
|Audio Stream Count**||Indicates the number of audio streaming media items that AppMon consumes during a visit. This can be audio+video.|
|Video Stream Count**||Indicates the number of video streaming media items that AppMon consumes during a visit. This can be audio+video.|
|Build**||The value taken from
|Converted by**||Lists the names of the Measures that converts the visit. The single measures are separated by a semicolon (;).
|ADK Version**||The ADK version. Listed for mobile applications only, empty for web applications.|
|Carrier/ISP**||For mobile applications, the carrier name as read from the SIM card of the mobile device. For web applications, the name if the Internet Service Provider.|
|GPS Coordinates**||Any discoverable land coordinates from the device used for the visit, at the time the visit was initiated.|
|Model ID**||The model number of the device used for the visit.|
|CPU**||The manufacturer's assigned name for the central processing unit in the device used for the visit. Processing speed is often used as part of the manufacturer's naming of CPUs.|
|rooted/Jailbroken**||For smartphone devices only. Lists one of three values to indicate whether restrictions on the smartphone's operating system have been removed and operating system features have been tweaked. rooted means the OS restrictions have been removed (Android smartphones). jailbroken means the OS restrictions have been removed (iOS smartphones). genuine means the smartphone's operating system restrictions have not been removed.|
|Crashed||For individual visits, this shows yes or no to indicate whether the visit has a crash reported. For a group of visits, this shows the percentage of visits within a total number of visits for that group that have a crash reported.|
|Landing Page Title||The title on the first page accessed in the application during the visit, as taken from the page metadata.|
|Landing Page Response Time||The page load response time of the first page the user visited.|
|Landing Page Response Time||The page load response time of the first page the user visited.|
|Landing Page Failed||Indicates if the first page the user visited failed (yes, no).|
|Exit Page Title||The title on the last page accessed in the application during the visit, as taken from the page metadata.|
|Exit Page Response Time||The page load response time of the last page the user visited.|
|Exit Page Failed||Indicates if the last page the user visited failed (yes, no).|
|Additional Tags**||Any additional measures that are associated with this visit.|
|End reason**||Shows the reason for ending a visit.|
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.