What properties (entities) I have to make an advanced experiment?

Understand Advanced Experiments

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:

  • Content
  • Traffic Sources
  • Visitor data
  • Visit Time
  • Systems
  • Page Tags

Content

Here you find entities that relate to you sites content (like URL, domain, queries and protocols used)

Page Url

Holds page url of a visit. This entity stores the full URi including transfer protocol, domain, url BUT NO string http://mydomain.com/url_here

Page Url with query string

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

Query string

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

Page Tags

Advanced page tags allow you to target the 4 custom fields

Javascript

Target based on a Javascript defined on the website.

Traffic Sources

Here are entities that can be used to segment visitor sources.

Keyword

The keywords visitor used to reach your website.

Medium

Type of traffic (now only search engine) but you can use UTM variables to fill this.

Source name

The name of the domain your visited came from (eg google.com)

Visitor data

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.

Average time on page

The average time in second an user spends on a page

City

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.

Country

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.

Days since last visit

Number of days elapsed since last visit (if returning visitor).

Language

Visitor's primary language as set up in his browser.

Pages visited

Number of pages visited

Region

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.

Visit duration

Current Visit duration (seconds). A visit is counter from the moment of first page hit to last page hit in session. This option only offers a max. of 24 seconds to measure on one page duration. If a second page is loaded we do count the exact time of previous page visit.

Visitor Cookie

Visitor cookie presence or content

Visitor Type

Visitor type ( eg new, returning)

Visits count

Number of times visitor visited your site (different visits means different sessions)

Tested Visitor

Check if visitor is currently bucketed in an active test. This condition prevents contamination of test results if the tests are testing similar items/topics.

Visit Time

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.

Day of week

The day of the week, Monday to Sunday

Hour of day

The hour of day visitor visited your site (visitor timezone in 24 hours - 00-24)

Minute

The minute of hour visitor visited your site (visitor hour in minutes hours - 00-59)

Project TZ (timezone) - Day of week

The day of the week, Monday to Sunday, in the timezone of your project.

Project TZ (timezone) - Hour of day

The hour of day visitor visited your site (visitor timezone in 24 hours - 00-24), in the timezone of your project.

Project TZ (timezone) - Minute

The minute of hour visitor visited your site (visitor hour in minutes hours - 00-59), in the timezone of your project.

Systems

Here you find some entities that can be used to identify visitor systems from there browser settings.

Browser

The browser used by visitor.

Browser Version

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).

Operating System

Operating system used by visitor.

User Agent

User agent that the browser software has.

Device

Mobile, Tablet and Desktop targeting.

Page Tags

JS condition

The Javascript condition you added to a page.

Custom Tags 1/4

The Javascript inside you added to a page.

Have more questions? Submit a request

Comments