All Users, sessions and events can have properties.
name
/ value
pair you add to your events, to describe the event
specifics or give it meaning; Wikipedia describes this concept: name/ value pairs.name
/ value
, the session and user will also have this
property name
/ value
.name
with a
new value
.si
that should be registered and an event property, see below for examples. The engine will generate
the user, sessions and events.If you are using Opentracker's javascript or native app libraries, you automatically collect a wide range of properties.
An example of what can be displayed is demonstrated in the screenshot of the visitor's profile (image displayed above).
Certain properties are reserved properties, these properties are used by the Opentracker engine to
help render specific features or calculate certain reports.
The following properties automatically get updated in the user interface:
Property | Function |
---|---|
browser |
the browser being used for this request (automatically detected from the user agent if not given) |
browserVersion |
the browser version being used for this request (automatically detected from the user agent if not given) |
connection |
the connection for this request, for example Cable or ADSL (automatically detected if not given) |
email |
Email address of a user |
platform |
the platform making this request (Eg Windows/ OS X). If not given, then this is automatically detected from the user agent. |