Dennis van der Heijden
posted this on September 19, 2009 14:39
When making rules for segments and actions entities are used to define the rule items. These entities can be dragged from the left menus and used to create a rule. There over thirty entities that can be selected so create actions and segments to improve visitor experiences.
We placed entities into four groups:
Here you find entities that relate to you sites content (like URL, domain, queries and protocols used)
This is used to create a rule that refers to a visitor action : clicked on an external link. By external link, we mean any link under a domain that is not added in your project.
The page visitor entered your website. This entity stores the full URi including transfer protocol, domain, url and string. This page path refers to the last stored landing page (last session)
URi of the page (bold) http://mydomain.com/url_here?var1=val1&var2=val2
Holds page url of a visit. This entity stores the full URi including transfer protocol, domain, url and string (bold) http://mydomain.com/url_here?var1=val1&var2=val2
This holds the query string in an URL. eg, what's after question mark in url (bold). http://mydomain.com/url_here?var1=val1&var2=val2
Domain visitor used to reach your website(site url) it can be domain.com, www.domain.com, testing.domain.com, testing1.testing.domain.com, etc.
This holds the transfer protocol of a visits! Said so anyone knows what this is about, it's http or https etc.
Here you find some entities that can be used to identify visitor systems from there browser settings.
The browser used by visitor.
The version of browser used by visitor, for example 3.5.7 (note that this is a string not numerical so that's why greater than comparisons do not work here).
Flash support capabilities of the visitor.
Java support capabilities of the visitor.
Operating system used by visitor.
Screen color depth of visitor (eg 24 (bits))
Screen resolution of your visitor. It's represented line WIDTHxHEIGHT. eg. 1024x768
Here are entities that can be used to segement visitor sources.
The keywords visitor used to reach your website.
The path of the referral (everything after domain).
The type of referral ( eg direct visit, search engine, internal)
The name of the domain your visited came from (eg google.com)
We grouped some other visitor data in this group, one of which is very important "Visitor segment" allows segments in segments and segments in actions.
The average time in second an user spends on a page
The city of visitor based on his IP. Although IP addresses are not stored in the system at the time of collecting the data a lookup is done on a geo-service and the geo information is entered in the system.
Visitor's country based on IP. Although IP addresses are not stored in the system at the time of collecting the data a lookup is done on a geo-service and the geo information is entered in the system.
Number of days elapsed since last visit (if returning visitor).
The hour of day visitor visited your site (visitor timezone in 24 hours - 00-24)
Visitor's primary language as set up in his browser.
Number of pages visited
Visitor's region based on IP. Although IP addresses are not stored in the system at the time of collecting the data a lookup is done on a geo-service and the geo information is entered in the system.
The time in second a user spends on a page
Current Visit duration (seconds). A visit is counter from the moment of first page hit to last page hit in session.
Visitor type ( eg new, returning).
Users are placed into segments within the software. This one represents all the segments the user is placed in at a certain time.
Number of times visitor visited your site (different visits means different sessions)