Activity Tracking is used to define the expected action pattern required to perform some Activity within the host application. For example, to complete a simple login, a user performs a set of actions. Once the login page is loaded, a user typically:
1. Types in an email or user name in the Username field
2. Types in a password into the Password field.
3. Clicks the Login button.
To "remember" the course of a seemingly simple procedure the following data should be collected:
- Each user action is considered to be a system event,
- Each element a user interacts with passes various properties to Apty with the aim of identifying each element in a unique way (ID, class, relationship with other page elements, etc.)
In essence, Activity is a combination of a user's step-by-step actions in the host application, which are registered by tracking events and properties identifying the elements that a user interacts with. This article covers types of events and attributes collected by Apty to record an Activity with Activity Tracking.
Types of Events being captured
To register certain actions performed by a user in the host application, Apty looks for specific types of events to be performed. Only two types of events are registered:
- On change: The "onchange" attribute fires the moment when the value of an element is changed. For example, when a user starts typing in a value in the input field, changes selection of a drop-down list, or marks a check-box to activate, or deactivate, a preference defined in the context of the page.
Types of Element Attributes being collected
Once the event fires, Apty stores information about the element that a user interacted with (clicked, provided input, or changed selection). The following element properties are captured by Apty:
|Gets the name of the operating system from which the hosting application has been accessed.
|Defines the browser used to access application.
|Detects current language of the browser.
|Detects the name of a device from which the hosing application is accessed.
|States the version number of the browser that sent the current request.
|The name of a device from which the hosting application has been accessed.
|Specifies the time zone offset from UTC, in minutes, to use for the current session.
|Width and height properties of the screen.
|Event Details: general information about user actions relevant to the hosting application.
|A field that identifies the address of the webpage (i.e. the URI or IRI) which is linked to the resource being requested.
|Defines the document's title that is shown in a browser's title bar or a page's tab.
|A boolean defining whether the event happened within the iFrame.
|Represents user actions:
|Represents the location of the actioned web element within the application’s DOM (document object model).
|Element Details: general information about an element a user interacted with.
|Uniquely identifies an element on the page.
|timestamp / timezone
|Date and time when a user interacted with an element.
|Attributes assigned to this element. The list of these attributes may vary depending on which of them were defined for this element.
|Define the position of the element in relation to others. For example, the "children" array will list all the elements that are nested in the given one.
|The tagName read-only property of the element interface returns the tag name of the element on which it's called. For example, if the element is an <img>, its tagName property is "img".
|If a given element has a label attached to it, it is going to be defined here.
|A path used to access this element.
Types of KPIs
The following Key Performance Indicators are collected and processed to be further displayed within the Insights Dashboard.
Error trend Widget
Top activity Completion Widget
Usage per Segment Widget