Setting up the Segmentation - Omniconvert Knowledgebase

Article sections

The segmentation process stays on the basis of all of your experiments. If you want to study only specific segments of traffic using Omniconvert surveys, you first need to create your segments. Also, if you want to personalize the web experience for specific users that fit into a buyer persona segment, you’ll need to create the segments before. Basically, any experiment idea you want to test needs a segment.

How to create a new Segment

To create segments follow these steps:

From the left side menu, select Advanced to open up the options and and then select Segments.

Then press on the Create new segment button on the right side of the screen. This menu also allows you to Edit, Copy or Delete an already existing Segment.

Name your segment according to your marketing goals and target audience. You can also provide a description for it and if you have multiple websites on your account but only want the Segment to available to a selected few, you can customize that.

For the segment conditions the first customizable option is to either Include or Exclude.

You can use these rule types and make combinations using the OR and AND operators.

AND – both conditions/rules A & B have to be true for the segment to be applied.
Example: Rule A (Include > Country > Is > Romania) and Rule B (Exclude > Returning visitor).

OR – one of the conditions/rules has to be true.
Example: Rule A (Include > New visitor), Rule B (Include > Country > Is > France).

In order to find out more about OR and AND please click here.

Our tool allows you to create any kind of segment based on parameters like in the example below.

Below you will find the description of each parameter used in our segmentation, with examples.

1. Traffic Source

1.1. Referrer type

The Referrer type parameter segments the visitors based on the type of traffic source. The values for this can be:

Direct – writing the website URL directly into the browser
Paid – coming from a paid campaign like Google Ads or Facebook Ads, etc.
Organic – coming from a search engine
Referral – coming from a recommendation website through a referral link

1.2. Referrer URL

Referrer URL segments the visitors based on what was the page they were on, before coming to your website. The conditions for the URL are:

Is – segments the visitors that are coming from the exact link introduced in the Value field.
Contains – segments the visitors that are coming from pages that contains the same value as the one inserted in the Value field.
Start with – segments the visitors that are coming from pages whose URL starts with the same value as inserted in the Value field.
End with – segments the visitors that are coming from pages whose URL ends with the same value as inserted in the Value field.
RegEx – define the links using RegEx.

2. Geolocation

2.1. Country

The Country parameter segments the visitors by the country from where they are accessing your website.

In order for this condition to apply, enter the first 3 letters of the word and then select the name from the list indicated by the platform.

2.2. Region

The Region parameter segments the visitors by the region(including states in the US) from where they are accessing your website.

In order for this condition to apply, enter the first 3 letters of the word and then select the name from the list indicated by the platform.

2.3. City

The City parameter segments the visitors by the city from where they are accessing your website.

In order for this condition to apply, enter the first 3 letters of the word and then select the name from the list indicated by the platform.

2.4. Visitors from EU

The Visitors from EU parameter segments the visitors that are accessing your website from a country which is part of the European Union.

3. Conversions

3.1. Count goal conversions

The Count goal conversions parameter segments the visitors by how many times they completed a certain goal after they were included in an experiment. It can be applied by selecting the Goal and mentioning the number of conversions reached as a limit.

The conditions for the conversions are:

Is – it segments the visitors with the exact number of conversions.
Example: Include -> Count goal conversions – > GoalName -> is – > 10
This segment targets only the visitors who have completed this GoalName 10 times exactly.
Lower than – it segments the visitors with a number of conversions lower than the number set in the ‘Value’ field.
Example: Include -> Count goal conversions – > GoalName -> lower than – > 10
This segment targets only the visitors who have completed this GoalName less than 10 times.
Greater than – it segments the visitors with a number of conversions greater than the number set in the ‘Value’ field.
Example: Include -> Count goal conversions – > GoalName -> greater than – > 10
This segment targets only the visitors who have completed this GoalName more than 10 times.

3.2. Days since last conversion

The Days since last conversion segments the visitors by the number of days since they last made a conversion on the website. It can be applied by selecting the Goal and mentioning the number of days.

The conditions you can use are:

Is – segments the visitors with the exact number of days.
Example: Include -> Days since last conversion – > GoalName -> is – > 1
This segment targets only the visitors who have completed this GoalName 1 day ago.
Lower than – segments the visitors who made a conversion under that number of days set in the Value field.
Example: Include -> Days since last conversion – > GoalName -> lower than – > 2
This segment targets only the visitors who have completed this GoalName less than 2 days ago.
Greater than – segments the visitors who made a conversion above that number of days set in the Value field.
Example: Include -> Count goal conversions – > GoalName -> greater than – > 2
This segment targets only the visitors who have completed this GoalName more than 2 days ago.

3.3. Average revenue

The Average revenue parameter segments visitors by the average revenue they brought to your website. It can be applied by selecting the Goal and mentioning the average revenue value.

The conditions you can use here are:

Is – segments the visitors that have brought to your website the exact average
value introduced in the value field.
Example: Include -> Average revenue – > Sale -> is – > 245
This segment targets only the visitors who have bought an average amount of 245 from your website.
Lower than – segments the visitors that have brought to your website a value lower than the one introduced in the value field.
Example: Include -> Average revenue – > Sale -> lower than – > 245
This segment targets only the visitors who have brought a lower average revenue than 245 to your website.
Greater than – segments the visitors that have brought to your website a value greater than the one introduced in the value field.
Example: Include -> Average revenue – > Sale -> greater than – > 245
This segment targets only the visitors who have brought a greater average revenue than 245 to your website.

Please keep in mind that this segmentation can be applied for Sale goal or for any custom goal that also reports a value to our platform.

3.4. Total revenue

The Total revenue parameter segments the visitors by the total revenue they brought to your website. It can be applied by selecting the Goal and mentioning the total revenue value.

The conditions you can use here are:

Is – segments the visitors that have brought to your website the exact amount introduced in the value field in terms of revenue.
Example: Include -> Total revenue – > Sale -> is – > 300
This segment targets only the visitors who have brought a total amount of 300 in terms of revenue to your website.
Lower than – segments the visitors that have brought to your website a lower amount than the one introduced in the value field in terms of revenue.
Example: Include -> Total revenue – > Sale -> lower than – > 300
This segment targets only the visitors who have brought a total amount lower than 300 in terms of revenue to your website.
Greater than – segments the visitors that have brought to your website a greater amount than the one introduced in the value field in terms of revenue.
Example: Include -> Total revenue – > Sale -> greater than – > 300
This segment targets only the visitors who have brought a total amount greater than 300 in terms of revenue to your website.

Please keep in mind that this segmentation can be applied for Sale goal or for any custom goal that also reports a value to our platform.

4. Behavior

4.1. Returning visitor

The Returning visitor parameter segments the visitors who have been on your website in the past, at least once. This does not take into consideration the users that have visited your website before installing the tracking code.
Example: User lands on your website on 01.01.2018
You install our tracking code on 10.01.2018
User visits your website again on 12.01.2018
This user is not a returning visitor it is a new visitor for our segmentation. If the user comes back again on 18.01.2018 then it becomes a returning visitor.

Please take into consideration that the number of visits on your website for each user is counted from the moment our tracking code is installed on your website.

4.2. New visitor

The New visitor parameter segments the users who are visiting your website for the first time since the Omniconvert tracking code has been installed.
Example: User lands on your website on 01.01.2018
You install our tracking code on 10.01.2018
All the users that access your website after 10.01.2016 for the first time are considered new visitors.

Please take into consideration that visits on your website for each user are counted from the moment our tracking code is installed on your website.

4.3. Days since first visit

The Days since first visit parameter segments visitors by how many days have passed since they have first landed on your website.
Example: User lands on your website on 01.01.2018.
You install our tracking code on 10.01.2018.
User visits your website again on 12.01.2018, which will be considered the first visit.

The conditions you can use here are:

Is – segments the visitors with the exact number of days that have passed since they have first landed on your website.
Example: Include -> Days since first visit – > is – > 5
This segment targets only the visitors who had their first visit on the website exactly 5 days ago.
Lower than – segments the visitors with the number of days that have passed since they have first landed on your website is lower than the one from the value field.
Example: Include -> Days since first visit – > lower than – > 10
This segment targets only the visitors who had their first visit on the website less than 10 days ago.
Greater than – segments the visitors with the number of days that have passed since they have first landed on your website is greater than the one from the value field.
Example: Include -> Days since first visit – > greater than – > 2
This segment targets only the visitors who had their first visit on the website more than 2 days ago.

Please take into consideration that visits on your website for each user are counted from the moment our tracking code is installed on your website.

4.4. Days since previous visit

The Days since previous visit parameter segments visitors by how many days have passed since their last visit on your website.
Example: User lands on your website on 01.01.2018
You install our tracking code on 10.01.2018
User visits your website again on 12.01.2018, which will be considered the first visit.
User visits your website again on 14.01.2018, which will be considered their last/previous visit.

The conditions you can use here are:

Is – segments the visitors with the exact number of days that have passed since their last visit on your website.
Example: Include -> Days since previous visit – > is – > 5
This segment targets only the visitors who had their previous visit on the website exactly 5 days ago.
Lower than – segments the visitors whose number of days that have passed since their last visit on your website is lower than the one introduced in the value field.
Example: Include -> Days since previous visit – > lower than – > 10
This segment targets only the visitors who had their first visit on the website less than 10 days ago.
Greater than – segments the visitors whose number of days that have passed since their last visit on your website is greater than the one introduced in the value field.
Example: Include -> Days since previous visit – > greater than – > 2
This segment targets only the visitors who had their first visit on the website more than 2 days ago.

Please take into consideration that visits on your website for each user are counted from the moment our tracking code is installed on your website.

4.5. Count visits

The Count visits parameter segments users by the number of times they have visited your website.
Example: User lands on your website on 01.01.2018
You install our tracking code on 10.01.2018
User visits your website again on 12.01.2018, which will be considered their first counted visit.

The conditions you can use here are:

Is – segments the visitors who have visited your website with the exact number of times.
Example: Include -> Count visits – > is – > 3
This segment targets only the visitors who have exactly 3 visits on your website.
Lower than – segments the visitors who have visited your website lower than that number of times introduced in the value field.
Example: Include -> Count visits – > lower than – > 5
This segment targets only the visitors who have less than 5 visits on your website.
Greater than – segments the visitors who have visited your website greater than that number of times introduced in the value field.
Example: Include -> Count visits – > greater than – > 2
This segment targets only the visitors who have more than 2 visits on your website.

Please take into consideration that visits on your website for each user are counted from the moment our tracking code is installed on your website.

4.6. Count pageviews in current session

The Count pageviews in current session parameter segments visitors by the number of pages visited on your website in the current session. The session starts at the moment they’ve landed on your website.

The conditions are:

Is – segments the visitors with the exact number of pages visited on your website in the current session, included the one where you want to apply your experiment.
Example: Include -> Count pageviews in current session – > is – > 3
The experiment will apply on the third page that user reached if that page is included in the ‘Audience’ tab condition.
Lower than – segments the visitors whose number of pages visited on your website in the current session is lower than the one introduced in the value field.
Example: Include -> Count pageviews in current session – > lower than – > 5
The experiment will apply on the first 4th pages that user reached if those pages are included in the ‘Audience’ tab condition.
Greater than – it segments the visitors whose number of pages visited on your website in the current session is greater than the one introduced in the value field.
Example: Include -> Count pageviews in current session – > greater than – > 2
The experiment will apply from the third page that user reached if that page is/those pages are included in the ‘Audience’ tab condition.

4.7. URL visited in current session

The URL visited in current session parameter segments visitors by a certain page that they have visited on your website in the current session.

For the below examples, let’s say you want to include this link in the segmentation:
https://www.omniconvert.com/case-studies

The conditions for the URL are:

Is – segments the visitors whose URL visited in the current session is identical with the one introduced in the value field.
Example: Include -> URLs visited in current session – > is – > https://www.omniconvert.com/case-studies
The experiment will apply only for the visitors who have been on this exact URL during their current session.
Contains – segments the visitors whose URL visited in the current session contains the value that was introduced in the value field.
Example: Include -> URLs visited in current session – > contains – > case
The experiment will apply only for the visitors who have been on an URL containing the aforementioned snippet their current session.
Start with – segments the visitors whose URL visited in current session starts with the same value as the one introduced in the value field.
Example: Include -> URLs visited in current session – > start with – > https://www.omniconvert
The experiment will apply only for the visitors who have been on an URL starting with the aforementioned snippet their current session.
End with – segments the visitors whose URL visited in current session ends with the same value as the one introduced in the value field.
Example: Include -> URLs visited in current session – > end with – > case-studies
The experiment will apply only for the visitors who have been on an URL ending with the aforementioned snippet their current session.
RegEx – define with RegEx the pages.

4.8. Time on site in current session

The Time on site in current session parameter segments visitors based on the amount of time, in seconds, they are spending in the current session on your website.

The conditions you can use here are:

Is – segments the visitors whose time on site is the exact seconds introduced in the value field.
Example: Include -> Time on current session – > is – > 20
The experiment will apply only for the visitors who have been on the current session for exactly 20 seconds.
Lower than – segments the visitors whose time on site is lower than the seconds introduced in the value field.
Example: Include -> Time on current session – > lower than – > 30
The experiment will apply only for the visitors who have been on the current session for less than 30 seconds.
Greater than – segments the visitors whose time on site is greater than the seconds introduced in the value field.
Example: Include -> Time on current session – > greater than – > 10
The experiment will apply only for the visitors who have been on the current session for more than 10 seconds.

4.9. Landing page in current session

The Landing page in current session parameter segments the visitors by the page they have first landed on when they’ve accessed the website.

For the below examples, let’s say you want to include this link in the segmentation:
https://www.omniconvert.com/case-studies

The conditions for the URL are:

Is – segments the visitors whose landing page URL in the current session is identical to the one introduced in the value field.
Example: Include -> URLs visited in current session – > is – > https://www.omniconvert.com/case-studies
The experiment will apply only for the visitors who have landed on this exact URL during their current session.
Contains – segments the visitors whose landing page URL in the current session contains the value that was introduced in the value field.
Example: Include -> URLs visited in current session – > contains – > case
The experiment will apply only for the visitors who have landed on an URL containing the aforementioned snippet their current session.
Start with – segments the visitors whose landing page URL in the current session starts with the same value as the one introduced in the value field.
Example: Include -> URLs visited in current session – > start with – > https://www.omniconvert
The experiment will apply only for the visitors who have landed on an URL starting with the aforementioned snippet their current session.
End with – segments the visitors whose landing page URL in the current session ends with the same value as the one introduced in the value field.
Example: Include -> URLs visited in current session – > end with – > case-studies
The experiment will apply only for the visitors who have landed on an URL ending with the aforementioned snippet their current session.
RegEx – define with RegEx the pages.

4.10. Viewed variation

The Viewed variation segments visitors by the Variation seen in a previously A/B test experiment. In order to use this parameter, you must have or have had an active A/B Test at some point that collected data.

Once you click on the Variation field, it will open the Variation selector. Here you can either press the Filter by button to show a dropdown with all the experiments on your account. Or you can type the name of the experiment in the Search field.

Once an experiment has been selected, it will show all the Variations within it, allowing you to select one of them to be included in the segmentation.

If you want multiple Variations to be included you cand use the AND condition and repeat the steps above for each Variation.

You also can segment the users that saw a particular Control by excluding the Variation of the same experiment.

4.11. Online visitors on the current page

The Online visitors on the current page parameter segments visitors by the number of online people on the current page of the website.

The conditions you can use here are:

Is – segments the exact number of online visitors like the one introduced in the value field.
Example: Include -> Online visitors on the current page – > is – > 5
The experiment will apply when there are exactly 5 visitors on the current page.
Lower than – segments the number of online visitors whose lower than the one introduced in the value field )
Example: Include -> Online visitors on the current page – > lower than – > 8
The experiment will apply when there are less than 8 visitors on the current page.
Greater than – segments the number of online visitors whose grater than the one introduced in the value field )
Example: Include -> Online visitors on the current page – > greater than – > 3
The experiment will apply when there are more than 3 visitors on the current page.

5. UTM parameters

If you are looking to learn more about what UTM parameters are, you can click here.

5.1. Utm_source

The utm_source parameter segments visitors that came from a specific source. It is used to describe where the traffic is coming from, for example, the name of the website displaying your adverts or the newsletter name.

Let’s say you have a campaign with this URL:
https://www.omniconvert.com/?utm_source=Google%20Addwords&utm_medium=banner%2025&utm_term=example%201&
utm_content=test%202&utm_campaign=Segmentation%20article

The conditions we can use here are:

Is – segments the visitors that are coming from the campaign whose source is identical to the one introduced in the value field.
Example: Include -> Utm_source – > is – > Google Adwords
The experiment will apply only for the visitors coming from a campaign with this exact source.
contains – segments the visitors that are coming from the campaign whose source contains the value introduced in the value field.
Example: Include -> Utm_source – > contains – > Google
The experiment will apply only for the visitors coming from a campaign which has a source containing the aforementioned snippet.
start with – segments the visitors that are coming from the campaign whose source starts with the value introduced in the value field.
Example: Include -> Utm_source – > start with – > Google
The experiment will apply only for the visitors coming from a campaign which has a source starting with the aforementioned snippet.
end with – segments the visitors that are coming from the campaign whose source ends with the value introduced in the value field.
Example: Include -> Utm_source – > end with – > Addwords
The experiment will apply only for the visitors coming from a campaign which has a source ending with the aforementioned snippet.
RegEx – define with RegEx the campaign’s source.

5.2. Utm_medium

The utm_medium parameter segments visitors that came from a specific campaign. It is used to describe the advertising or marketing medium, for example: CPC, banner, email etc.

The conditions we can use here are:

Is – segments the visitors that are coming from the campaign whose medium is identical to the one introduced in the value field.
Example: Include -> Utm_medium – > is – > banner 25
The experiment will apply only for the visitors with a medium identical with the snippet.
Contains – segments the visitors that are coming from the campaign whose medium contains the value introduced in the value field.
Example: Include -> Utm_medium – > contains – > banner
The experiment will apply only for the visitors with a medium containing the aforementioned snippet.
Start with – segments the visitors that are coming from the campaign whose medium starts with the value introduced in the value field.
Example: Include -> Utm_medium – > start with – > banner
The experiment will apply only for the visitors with a medium starting with the aforementioned snippet.
End with – segments the visitors that are coming from the campaign whose source ends with the value introduced in the value field.
Example: Include -> Utm_medium – > end with – > 25
The experiment will apply only for the visitors with a medium ending with the aforementioned snippet.
RegEx – define with RegEx the campaigns source.

5.3. Utm_term

The utm_term parameter segments visitors that came from a specific campaign. This is used to specify the keyword that you want to manually tag in paid campaigns. For example, a google adwords campaign for the term SEO services would be tagged utm_term=seo_services.

The conditions we can use here are:

Is – segments the visitors that are coming from the campaign whose term is identical to the one introduced in the value field.
Example: Include -> Utm_term – > is – > example
The experiment will apply only for the visitors with a term identical with the snippet.
Contains – segments the visitors that are coming from the campaign whose term contains the value introduced in the value field.
Example: Include -> Utm_term – > contains – > example
The experiment will apply only for the visitors with a term containing the aforementioned snippet.
Start with – segments the visitors that are coming from the campaign whose term starts with the value introduced in the value field.
Example: Include -> Utm_term – > start with – > example
The experiment will apply only for the visitors with a term starting with the aforementioned snippet.
End with – segments the visitors that are coming from the campaign whose term ends with the value introduced in the value field.
Example: Include -> Utm_term – > end with – > 1
The experiment will apply only for the visitors with a term ending with 1.
RegEx – define with RegEx the campaigns source.

5.4. Utm_content

The utm_content parameter segments visitors that came from a specific element on your ad or promotion that was clicked. This is often used for optimization purposes.

Used to identify the exact element on your ad or promotion that was clicked. This is often used for optimization purposes. If you have, for example, two different calls to action in one piece of content, you can use this tag to differentiate between the two of them, like video_ad and text_ad.

Let’s say you have a campaign with this URL:
https://www.omniconvert.com/?utm_source=Google%20Addwords&utm_medium=banner%2025&utm_term=example%201&utm_content=video%20ad&utm_campaign=Segmentation%20article

The conditions we can use here are:

Is – segments the visitors that are coming from the campaign whose content is identical to the one introduced in the value field.
Example: Include -> Utm_content – > is – > video
The experiment will apply only for the visitors with a content identical with the snippet.
Contains – segments the visitors that are coming from the campaign whose content contains the value introduced in the value field.
Example: Include -> Utm_content – > contains – > ad
The experiment will apply only for the visitors with a content containing the aforementioned snippet.
Start with – segments the visitors that are coming from the campaign whose content starts with the value introduced in the value field.
Example: Include -> Utm_content – > start with – > video
The experiment will apply only for the visitors with a content starting with the aforementioned snippet.
End with – segments the visitors that are coming from the campaign whose campaign end with the value introduced in the value field.
Example: Include -> Utm_content – > end with – > ad
The experiment will apply only for the visitors with a content ending with the aforementioned snippet.
RegEx – define with RegEx the campaigns source.

5.5. Utm_campaign

The utm_campaign parameter segments visitors that came from a specific campaign. This refers to the overall campaign you are running. For example, if the new campaign you are launching is for a new phone (e.g. the K00z) then your campaign may be called K00z_launch.

The conditions we can use here are:

Is – segments the visitors that are coming from the campaign whose campaign is identical to the one introduced in the value field.
Example: Include -> Utm_campaign – > is – > Segmentation article
The experiment will apply only for the visitors with a campaign identical with the snippet.
Contains – segments the visitors that are coming from the campaign whose campaign contains the value introduced in the value field.
Example: Include -> Utm_campaign – > contains – > Segmentation
The experiment will apply only for the visitors with a campaign containing the aforementioned snippet.
Start with – segments the visitors that are coming from the campaign whose campaign starts with the value introduced in the value field.
Example: Include -> Utm_campaign – > start with – > Segmentation
The experiment will apply only for the visitors with a campaign starting with the aforementioned snippet.
End with – segments the visitors that are coming from the campaign whose campaign end with the value introduced in the value field.
Example: Include -> Utm_campaign – > end with – > article
The experiment will apply only for the visitors with a campaign ending with the aforementioned snippet.
RegEx – define with RegEx the campaigns source.

6. Custom

6.1. Cookies

The Cookies parameter segments visitors by their cookies. In order to use this segmentation, you must set the cookie for the user when he visits your website. Its value can be a number or a text.

Let’s say you have implemented a cookie that added user this value in their browser: 1254

The conditions we can use here are:

Is – segments the visitors whose value of the cookie is identical to the one inserted in the value field.
Example: Include -> Cookie – > Cookie name – > is – > 1254
The experiment will apply only for the visitors whose cookie value is exactly 1254.
Contains – segments the visitors whose value of the cookie contains the one introduced in the value field.
Example: Include -> Cookie – > Cookie name – > contains – > 25
The experiment will apply only for the visitors whose cookie value contains 25.
Start with – segments the visitors whose value of the cookie starts with the one introduced in the value field.
Example: Include -> Cookie – > Cookie name – >start with – > 12
The experiment will apply only for the visitors whose cookie value is starting with 12.
End with – segments the visitors whose value of the cookie ends with the one introduced in the value field.
Example: Include -> Cookie – > Cookie name – > end with – > 54
The experiment will apply only for the visitors whose cookie value is ending with 54.
Lower than – segments the visitors whose value of the cookie is lower than the one introduced in the value field.
Example: Include -> Cookie – > Cookie name – > lower than – > 1255
The experiment will apply only for the visitors whose cookie value is lower than 1255.
Greater than – segments the visitors whose value of the cookie is greater than the one introduced in the value field.
Example: Include -> Cookie – > Cookie name – > greater than- > 1253
The experiment will apply only for the visitors whose cookie value is higher than 1253.
RegEx – define with RegEx the value.

In order to find out more about cookie and what it does click here.

6.2. Custom attribute

The Custom attribute is data you store in your own database and want to share it with Omniconvert in order to segment your visitors in a more advanced manner.

This parameter segments visitors by data you store about them in your own database and share it with our platform. In order to use it, the website must have a custom variable(given by us) placed inside your website’s code that pushes data in your Omniconvert account database when a new visitor lands on your website.

Let’s say that your data is pushing the age of the visitors from the database.

The conditions we can use here are are:

Is – segments the visitors whose value of the custom attribute from the database is identical to the one inserted in the value field.
Ex. Include -> Custom attribute – > Custom attribute name – > is – > 20
This segment targets only the visitors, registered in your database, that have 20 years old.
Contains – segments the visitors whose value of the custom attribute from database contains the one inserted in the value field.
Ex. Include -> Custom attribute – > Custom attribute name – > contains – > 2
This segment targets only the visitors, registered in your database, that have 2 included in their age.
Start with – segments the visitors whose value of the custom attribute from database starts with the one inserted in the value field.
Ex. Include -> Custom attribute – > Custom attribute name – > start with – > 2
This segment targets only the visitors, registered in your database, whose age stars with 2.
End with – segments the visitors whose value of the custom attribute from database ends with the one inserted in the value field.
Ex. Include -> Custom attribute – > Custom attribute name – > end with – > 2
This segment targets only the visitors, registered in your database, whose age ends with 2.
Lower than – segments the visitors whose value of the custom attribute from the database is lower than the one inserted in the value field.
Ex. Include -> Custom attribute – > Custom attribute name – > start with – > 30
This segment targets only the visitors, registered in your database, whose age is under 30.
Greater than – segments the visitors whose value of the custom attribute from the database is greater than the one inserted in the value field.
Ex. Include -> Custom attribute – > Custom attribute name – > start with – > 19
This segment targets only the visitors, registered in your database, whose age is above 19.
RegEx – define with RegEx the value.

6.3. onPage variable

The onPage variable parameter segments visitors by the variable that was defined in Optimization – OnPage Variables.

Let’s say that you declared the total of the cart, your onPage variable.

The conditions we can use here are:

Is – segments the visitors whose value of the variable from the website is identical to the one inserted in the value field.
Example: Include -> onPage Variable – > onPage Variable name – > is – > 200
This segment targets only the visitors that have 200 in their cart.
Contains – segments the visitors whose value of the variable from website contains the one inserted in the value field.
Example: Include -> onPage Variable – > onPage Variable name – > contains – > 200
This segment targets the visitors whose cart contains 200.
Start with – segments the visitors whose value of the variable from the website starts with the one inserted in the value field.
Example: Include -> onPage Variable – > onPage Variable name – > start with – > 200
This segment targets the visitors whose cart start with 200.
End with – segments the visitors whose value of the variable from website ends with the one inserted in the value field.
Example: Include -> onPage Variable – > onPage Variable name – > end with – > 200
This segment targets the visitors whose cart ends with 200.
Lower than – segments the visitors whose value of the variable from the website is lower than the one inserted in the value field.
Example: Include -> onPage Variable – > onPage Variable name – > lower than – > 200
This segment targets the visitors whose cart is lower than 200.
Greater than – segments the visitors whose value of the variable from the website is greater than the one inserted in the value field.
Example: Include -> onPage Variable – > onPage Variable name – > greater than – > 200
This segment targets the visitors whose cart is greater than 200.
RegEx – define with RegEx the value.

If you want to know how to created an onPage variable, you can follow this article.

6.4 GTM dataLayer variable

The GTM dataLayer variable parameter segments visitors by the variable that is defined and pushed from the website database using Google Tag Manager dataLayer.

Let’s say that your datalayer is pushing the age of the visitors from the database.

The conditions we can use are:

Is – segments the visitors whose value of the dataLayer, from website database, is identical to the one introduced in the value field.
Example: Include -> GTM datalayer variable – > datalayer variable name – > is – > 20
This segment targets only the visitors, registered in your database, who have 20 years old.
Contains – segments the visitors whose value of the dataLayer, from website database, contains the one introduced in the value field.
Example: Include -> GTM datalayer variable – > datalayer variable name – > contains – > 2
This segment targets only the visitors, registered in your database, that have 2 included in their age.
Start with – segments the visitors whose value of the dataLayer, from website database, starts with the one introduced in the value field.
Example: Include -> GTM datalayer variable – > datalayer variable name – > start with – > 2
This segment targets only the visitors, registered in your database, whose age stars with 2.
End with – segments the visitors whose value of the dataLayer, from website database, ends with the one introduced in the value field.
Example: Include ->GTM datalayer variable – > datalayer variable name – > end with – > 2
This segment targets only the visitors, registered in your database, whose age ends with 2.
Lower than – segments the visitors whose value of the dataLayer, from website database, is lower than the one introduced in the value field.
Example: Include -> GTM datalayer variable – > datalayer variable name – > start with – > 30
This segment targets only the visitors, registered in your database, whose age is under 30.
Greater than – segments the visitors whose value of the dataLayer, from website database, is greater than the one introduced in the value field.
Example: Include -> GTM datalayer variable – > datalayer variable name – > start with – > 19
This segment targets only the visitors, registered in your database, whose age are upper than 19.
RegEx – define with RegEx the value.

Please ensure that dataLayer is populated with the values needed for segmentation before the Omniconvert code loads.

6.5 GTM dataLayer event

The GTM dataLayer event parameter segments visitors by a certain event is received from Google Tag Manager dataLayer. This segmentation check if the events registered in the dataLayer global variable and if it matches the one specified in Explore than the experiment will apply.

Let’s say that your datalayer event being pushed to an user after they register, and the event is new_subscriber.

The conditions we can use are:

Is – segments the visitors who have been pushed the specific event which has the value of the snippet used.
Example: Include -> GTM datalayer event – > is – > new_subscriber
This segment targets only the visitors who registered and have been pushed the event ‘new_subscriber’.
Contains – segments the visitors who have been pushed any event which contains the snippet.
Example: Include -> GTM datalayer attribute – > contains – > subscriber
This segment targets only the visitors who have been pushed any event which has ‘subscriber’ in the value composition.
Start with – segments the visitors who have been pushed any event which is starting with the snippet.
Example: Include -> GTM datalayer event – > start with – > subscriber
This segment targets only the visitors who have been pushed any event which is starting with ‘subscriber’ in the value composition.
End with – segments the visitors who have been pushed any event which is ending with the snippet.
Example: Include ->GTM datalayer event – > end with – > subscriber
This segment targets only the visitors who have been pushed any event which is ending with ‘subscriber’ in the value composition.
RegEx – define with RegEx the value.

Please ensure that dataLayer is populated with the values needed for segmentation before the Omniconvert code loads.

7. Technology

7.1. IP address

The IP address parameter segments visitors by their IP address.

The conditions are:

Is – segments the visitors whose IP address is identical to the one introduced in the value field.
Example: Include -> IP address – > is – > 19.896.567
This segment targets only the visitors with this exact IP address – 19.896.567.
Contains – segments the visitors whose IP address contains the one introduced in the value field.
Example: Include -> IP address – > contains – > 896
This segment targets only the visitors with an IP address containing 896.
Start with – it segments the visitors whose IP address starts with the one introduced in the value field.
Example: Include -> IP address – > start with – > 19
This segment targets only the visitors with an IP address starting with 19.
End with – segments the visitors whose IP address ends with the one introduced in the value field.
Example: Include -> IP address – > end with – > 567
This segment targets only the visitors with an IP addresse ending with 567.
RegEx – define with RegEx the value.

In order to find out your IP address, click here.

7.2. Device type

The device type parameter segments the visitors based on which device they’re using when they are accessing your website.

The options here are:

Desktop.
Phone.
Tablet.

7.3. Operating system

The operating system parameter segments visitors by their device operating system when they are accessing your website.

The options here are:

Windows.
MacOS.
Linux.
iOS.
Android.

7.4. Browser name

The browser name parameter segments visitors by the browser they’re using to access your website.

The options here are:

Chrome.
Firefox.
Opera.
Safari.
Internet Explorer.
Edge.

7.5. Browser version

Thee browser version parameter segments visitors by the version of the browser used to access your website.

The conditions are:

Is – segments the visitors whose browser version is identical to the one introduced in the value field.
Example: Include -> Browser version – > is – > 10.2
The experiment will only apply to visitors with a browser version of 10.2.
Lower than – segments the visitors whose browser version is lower than the one introduced in the value field.
Example: Include -> Browser version – > Lower than – > 9.8
The experiment will only apply to visitors with a browser version older than 11.5.
Greater than – segments the visitors whose browser version is greater than the one introduced in the value field.
Example: Include -> Browser version – > Greater than – > 11.5
The experiment will only apply to visitors with a browser version newer than 11.5.

7.6. Browser language

The browser language parameter segments visitors by the language set up into the browser at the moment they are accessing your website.

7.7. Page Loaded In Iframe

The page loaded in Iframe parameter segments visitors based on if the website was loaded in an iframe. It can be used to create experiments for clients who see the website in an iframe or not.

7.8. Screen width

The screen width parameter segments visitors by their device screen width(number of pixels).

The conditions are:

Is – segments the visitors whose screen width is identical to the one introduced in the value field.
Example: Include -> Screen width – > is – > 1000
The experiment will only apply to visitors with a 1000 pixels wide screen.
Lower than – segments the visitors whose screen width is lower than the one introduced in the value field.
Example: Include -> Screen width – > lower than – > 1000
The experiment will only apply to visitors a less than 1000 pixels wide screen.
Greater than – segments the visitors whose screen width is greater than the one introduced in the value field.
Example: Include -> Screen width – > greater than – > 600
The experiment will only apply to visitors a higher than 600 pixels wide screen.

7.9. Screen height

The screen height parameter segments visitors by their device screen height(number of pixels).

The conditions are:

Is – segments the visitors whose screen height is identical to the one introduced in the value field.
Example: Include -> Screen height – > is – > 1000
The experiment will only apply to visitors with a 1000 pixels screen height.
Lower than – segments the visitors whose screen height is lower than the one introduced in the value field.
Example: Include -> Screen height – > lower than – > 1000
The experiment will only apply to visitors a less than 1000 pixels screen height.
Greater than – segments the visitors whose screen height is greater than the one introduced in the value field.
Example: Include -> Screen height – > greater than – > 600
The experiment will only apply to visitors a higher than 600 pixels screen height.

7.10. Javascript variable

The javascript variable segments visitors by the data the variable returns. It can be a value generated dynamically on spot or some value about the user that you’ve recorded into your database. In order to use it, you must have implemented a Javascript variable defined in the source code of your website that returns the data you wish in order for Omniconvert to read it.

Let’s say that is a variable that pushes the total of the cart.

The conditions we can use here are:

Is – segments the visitors whose value of the javascript variable is identical to the one inserted in the value field.
Example: Include -> Javascript variable – > Javascript variable name – > is – > 200
This segment targets only the visitors that have 200 in their cart.
Contains – segments the visitors whose value of the javascript variable contains the one inserted in the value field.
Example: Include -> Javascript variable – > Javascript variable name – > contains – > 200
This segment targets the visitors whose cart contains 200.
Start with – segments the visitors whose value of the javascript variable starts with the one inserted in the value field.
Example: Include -> Javascript variable – > Javascript variable name – > start with – > 200
This segment targets the visitors whose cart start with 200.
End with – segments the visitors whose value of the javascript variable ends with the one inserted in the value field.
Example: Include -> Javascript variable – > Javascript variable name – > end with – > 200
This segment targets the visitors whose cart ends with 200.
Lower than – segments the visitors whose value of the javascript variable is lower than the one inserted in the value field.
Example: Include -> Javascript variable – > Javascript variable name – > lower than – > 200
This segment targets the visitors whose cart is lower than 200.
Greater than – segments the visitors whose value of the javascript variable is greater than the one inserted in the value field.
Example: Include -> Javascript variable – > Javascript variable name – > greater than – > 200
This segment targets the visitors whose cart is greater than 200.
RegEx – define with RegEx the value.

JavaScript variables are expected to return a string or a number as their value. If you have a variable which returns a boolean, you need to add .toString() to it.

7.11. Javascript callback

The javascript callback segments visitors by a custom segmentation created via javascript. The user needs to define an evalSegment function that will return true if the segmentation has passed and the experiments needs to be applied, otherwise it will return false.

Pressing on the </> Edit callback code will open a new screen where you will be able to write your code.

7.12. Internet Service Provider

The internet service provider parameter segments visitors based on the Internet service provider they are using.

Let’s say you are using Vodafone on your mobile device and you have mobile data on it.
If you access a website where an Omniconvert experiment is running and he has a segmentation with a condition like the one above, you will be able to see the experiment.

The conditions you can use are:

Is ( it segments the visitors whose ISP is identical to the one inserted in the value field )
Example: Include -> Internet service provider – > is – > VODAFONE
This segment targets only the visitors that are using the internet from Vodafone.
Contains ( it segments the visitors whose ISP name contains the part in the value field )
Example: Include -> Internet service provider – > contains – > DAFONE
This segment targets the visitors whose ISP name contains DAFONE.
Start with ( it segments the visitors whose ISP name starts with what has been inserted in the value field )
Example: Include -> Internet service provider – > start with- > VODA
This segment targets the visitors whose ISP name start with VODA(Vodafone, Vodanet, VodaLan, etc).
End with ( it segments the visitors whose ISP name ends with the one inserted in the value field )
Example: Include -> Internet service provider – > start with- > FONE
This segment targets the visitors whose ISP name end with FONE(Vodafone, Panafone, Intelfone, etc).
RegEx ( define with RegEx the value )

You can search directly using provider’s name, but you can narrow down the results by adding the 2-letter country prefix. (Example: US: AT&T)

8. Previous Surveys

The previous survey parameter segments visitors by the answers they gave to a certain Survey that is/was active. In the parameter list you will be able to see all the active Surveys and you can select one as your parameter.

The next step is to select which question you want the system to check. The answer for: field will show the questions from the Survey.

The conditions you can use here are:

Is – segments the visitors whose value of the parameter is identical to the one inserted in the value field.
Contains – segments the visitors whose value of the parameter contains the one inserted in the value field.
Start with – segments the visitors whose value of the parameter starts with the one inserted in the value field.
End with – segments the visitors whose value of the parameter ends with the one inserted in the value field.
RegEx – define with RegEx the value.

9. External Data

9.1. Woopra Label

The Woopra label parameter segments visitors based on their Woopra code. It needs Woopra to be installed on your website and the segmentation passes if the provided label can be found in the window.woopra.labels object.

This segmentation can be applied only if you have this software installed on the same website with our tracking code. Pleasure bear in mind that the Value field is case sensitive.

10. E-commerce Platform – Magento

This are used for VTex integration. These parameters are defined as Javascript variables in the VTex shop and can be used in Explore to create segmentations based on it. The values of these variables are calculated by Omniconvert Reveal and pushed into the VTex shop from there.

10.1. Magento Group

The Magento group parameter segments visitors by the group that they belong to(user must be logged in).

Logged out users will have the value _none as group name.

If you need to target logged out users also, please use Magento Last Known Group parameter.

10.2. Magento Last Known Group

The Magento group parameter segments visitors by the group that they belong to(if the user is currently logged in) or the last time when they were logged in(if the user is not currently logged in).

If you need to target only logged out users, consider adding a condition for Magento Group to match _none.

11. E-commerce Platform – Shopify

11.1. RFM Group

The RFM group parameter segments visitors by the Reveal RFM group that they belong to(user must be logged in).

Not logged in users will not have the value for the RFM Group set.

11.2. RFM Score

The RFM score parameter segments visitors by the Reveal RFM score that they have(user must be logged in).

Not logged in users will not have the value for the RFM Score set.

11.3. Last Know RFM Group

The last know RFM group parameter segments visitors by the Reveal RFM Group to which they belong to(if the user is currently logged in) or belonged to last time when they were logged in(if the user is not currently logged in).

If you need to target only logged out users, consider adding a condition for RFM Group to match an empty value.