The list below covers data points collected automatically by the tracking code.
Interactive Events (Type E)
Interactive Event syntax:
key.value
Supported segmentation queries include full wildcards for key and value and partial wildcards for key:
*.value key.* k*y.value
The following user interactions with page elements are tracked automatically.
type | key | value | tracked on | can be used as a trigger |
E | HTML element selector | mouseover div[1]#basket/button[3].primary.mouseover |
on mouse pointer moved over a page element | Yes |
E | HTML element selector | touchstart div[1]#basket/button[3].primary.touchstart |
on touch of a page element (see mousedown for desktop equivalent) | Yes |
E | HTML element selector | touchmove div[1]#basket/button[3].primary.touchmove |
on finger movement after a touch of a page element (no equivalent event on desktop) | Yes |
E | HTML element selector | mousedown div[1]#basket/button[3].primary.mousedown |
on left mouse button press of a page element (see touchstart for mobile equivalent) | Yes |
E | HTML element selector | mouseup div[1]#basket/button[3].primary.mouseup |
on release of left mouse button (see touchend for mobile equivalent) | Yes |
E | HTML element selector | touchend div[1]#basket/button[3].primary.touchend |
on release of a finger (see mouseup for mobile equivalent) | Yes |
E | HTML element selector | click div[1]#basket/button[3].primary.click |
on left mouse button or touch release over the same page element on which the most recent mousedown or touchstart event occurred | Yes |
E | HTML element selector | focus input[1]#name.required.focus |
typically, after a mousedown or touchstart on interactive elements – form fields and links – followed by a click event but can also be invoked by switching focus between any elements using a TAB key | Yes |
E | HTML element selector | change input[1]#name.required.change |
on change of a value of a form field element | Yes |
E | _uJS | Scroll _uJS.Scroll |
on window scroll; | No |
Meta Events (Type M)
The following meta events are automatically tracked during a visit. As tracking of meta can be customised, the list below describes the default setup only.
Meta Event syntax:
key=value
Supported segmentation queries include partial wildcards for key and value, full wildcard for value and numeric relational operators:
key=value key=* k*=value k*=val* key>value ke*<=value
type | key | value | tracked on | can be used as a trigger |
M | URL URL=https://mywebsite.com/?utm_source=google.com |
full URL of a current page including search parameters and hash | when a page is loaded | YES |
M | Section Section=Home Section=Register |
part of a URL after “/” that follows a domain without search parameters (‘?abc=123′) but including hash; “Home” if URL is the same as the domain. | when a page is loaded or hash in URL is changed | Yes |
M | Time in {{Section}} Time in Home=31 |
time in seconds from a Section event to a next Section event or end of a visit. | before a new Section event or at the end of a visit | Yes |
M | Total time in {{Section}} Total time in Pricing=233 |
sum of “Time in” values in seconds for a Section. | at the end of a visit | No |
M | Action Action=Submitted form: #register |
Submitted form: {{form element selector}}. | when a form is submitted using a standard form submit method to a URL specified in forms’s action attribute. | Yes |
M | Time to {{Action}} Time to Submitted form: #register=320 |
time in seconds from a start of a visit to Action event | immediately after an Action event | Yes |
M | Triggered Triggered=Chat Invites/Show Message/T123456789 |
Response identifier using the following naming convention: {{report}}/{{response name}}/{{trigger id}} | immediately after a trigger criteria are met; if a user is in the sample, the response is then triggered for execution. | Yes |
The following predefined meta events require custom setup, either using uDash.saveMeta(key,value) JavaScript method or Triggers with Data Collection Responses. The list below describes the latter scenario.
type | key | value | tracked on | can be used as a trigger |
M | Error Error=Invalid phone number on #phoneNum |
if “Save Page Content As Errors” Response is used, the value is formed using the following convention: {{element text content}} on #{{id of the closest element with #id}} | upon execution of a response as specified in a trigger, usually after field change or button click interactive events and/or Section or Action meta events. | Yes |
Visit Attributes (Type A)
The following visit attributes are automatically tracked during a visit. As tracking of attributes can be customised, the list below describes the default setup only.
Attribute syntax:
key=value
Supported segmentation queries include full and partial wildcards for value and numeric relational operators:
key=value key=* key>value key<=value
type | key | value | tracked on | can be used as a trigger |
A | userAgentString userAgentString=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.98 Safari/537.36 |
information about browser and OS system as returned by browser’s navigator.userAgent | at the beginning of a visit | Yes |
A | userID userID=96516088 |
randomly assigned ID at the moment of a user’s first visit and stored in browser’s LocalStorage | at the beginning of a visit | Yes |
A | userVisit userVisit=3 |
visit number stored in browser’s local storage and incremented with each new visit | at the beginning of a visit | Yes |
A | firstVisit firstVisit=2016-08-31 21:00 |
date of user’s first visit retrieved from LocalStorage in a format YYYY-MM-DD HH:MM. Segmentation using numeric relational operators (greater than, equal or smaller than) is supported. | at the beginning of a visit | Yes |
A | version version=uDash JS 3.0.03 |
version of UseItBetter JavaScript tracking code (uDash) | at the beginning of a visit | Yes |
A | localDateTime localDateTime=Sun Dec 4 01:30:29 GMT+0100 2016 |
A string containing users local date and time as reported by user’s browser in format {{Day of Week}} {Month} {{Day of Month}} {{HH}}:{{MM}}:{{SS}} GMT+{{HHMM}} {{YYYY}} | at the beginning of a visit | Yes |
A | timezoneOffset timezoneOffset=-60 |
Time difference in minutes between user’s local timezone and UTC as reported by user’s browser. | at the beginning of a visit | Yes |
A | referrer referrer=https://google.com referrer=none |
Full URL of a referring page based on document.referrer. If document.referrer is empty, which may happen if user is coming from an email client, a bookmark or by typing in address in URL bar, then the value is set to “none” | at the beginning of a visit | Yes |
A | entryUrl entryUrl=http://mywebsite.com/pricing?utm_source=google.com |
Full URL of a page on which visit was started. | at the beginning of a visit | Yes |
A | interface interface=mouse interface=touch |
if a browser supports touch events and document.ontouchstart exists the value is set to “touch”; otherwise is set to “mouse”. | at the beginning of a visit | Yes |
A | path path=^^Home^Register^Submitted form: #register^Thank you^^ |
A chain of values of Section and Action event starting and ending with double caret (^^) and seprated with single caret (^). | formed in UseItBetter backend after a visit is completed; its temporary value is stored in SessionStorage and updated after each Section or Action event | Yes |
A | Country Country=Jamaica |
Name of a country in which user is located based on user’s IP | formed in UseItBetter backend after a visit is completed | No |
A | Browser Browser=Firefox 55 |
Name and version of user’s browser based on userAgentString | formed in UseItBetter backend after a visit is completed | No |
A | Platform Platform=Windows 10 |
Name and version of user’s operating system based on userAgentString | formed in UseItBetter backend after a visit is completed | No |
A | Device Device=Desktop Device=Mobile Phone |
Name and version of user’s browser based on userAgentString | formed in UseItBetter backend after a visit is completed | No |
A | Actions Actions=2 |
Total number of Action events tracked in a visit | formed in UseItBetter backend after a visit is completed | No |
A | Errors Errors=5 |
Total number of Error events tracked in a visit | formed in UseItBetter backend after a visit is completed | No |
A | Sections Sections=12 |
Total number of Sections events tracked in a visit | formed in UseItBetter backend after a visit is completed | No |
A | Events Events=234 |
Total number of events tracked in a visit | formed in UseItBetter backend after a visit is completed | No |
The following attributes are saved for each defined Trigger:
type | key | value | tracked on | can be used as a trigger |
A | {{Trigger ID}} T123456789=Control T123456789=Chat Invites/Show Message |
If a user is assigned to Trigger’s control group the value is set to “Control”, otherwise to “{{Report Name}}/{{Response Name}}” | at the beginning of a visit | Yes |
The following predefined attributes require custom setup, either using uDash.saveAttribute(key,value) JavaScript method or Triggers.
type | key | value | tracked on | can be used as a trigger |
A | appID appID=XYZ123456789 |
non-random string or number that identifies a user (registered account ID, hash of an email address) | custom setup | Yes |