Available Options For Configuring Custom Segments in VWO

Source

• Landing Page URL: this is the page that the user is currently on. This would be helpful in case you are running tests on multiple pages and wish to include the user in a test only when they visit a specific page.
  Select this option to track visitors who land first on a specific URL before landing on the test page. For example, you can select this option to track only the visitors who first land on the homepage of your site. For running a site-wide test using a URL pattern, you can specify the landing page URL as the home page URL in a segment condition, to collect data of visitors who first land on the home page.

  NOTE: This URL must be part of the Campaign URL pattern.

• Referring URL: Referral traffic comprises of the visitors who land on the test page through referral websites, and in this case, document.referrer has a value. In the context of an A/B test, this is the previous page URL. 
• Search Keywords: Select this option for visitors who use certain search keywords to land on the test page. The Search Keywords condition applies for both organic and paid search traffic from search engines.
  

  NOTE: Segmentation does not work for the search engines that are on 
  HTTPS because the search engines on HTTPS encrypt the search keywords.

• Traffic Source: Use this option to segment the report based on the source that the visitor has come from. The following traffic source options are available in VWO:
   
  • Direct: This option refers to the traffic that directly lands on the test page and when document.referrer in visitor information is empty.
  • Email: This type contains utm_medium=email as the query parameter.
  • Referral: This option refers to the paid ad traffic, when document.referrer in visitor information has a value. It contains utm_medium query parameters such as cpc, ppc, cpa, cpm, cpv, or cpp.
  • Social: It comprises of the visitors who come from social media platforms like Facebook, Quora, Reddit, Imgur, Disqus, 9gag, Tumblr, Google Plus, Stumbleupon, Twitter, Linkedin, Technorati, Digg, Hootsuite, Myspace, Tinyurl, Youtube, Flickr, Pinterest, and so on.
  • Search Organic: This option refers to the unpaid ad traffic, when document.referrer in visitor information has a value. It includes organic traffic from a search medium but does not contain utm_medium query parameters such as cpc, ppc, cap, cpm, cpv, or cop.
  • Search Inorganic: This option refers to the paid traffic. It refers to users who enter your website through paid Internet advertising. Google AdWords is the most used paid advertising network.
• Query Parameter: Select this option if segments are based on the value of the query parameter in the URL (used for test variables). For example, http://example.com?_utm_campaign=brandNew. The query parameter in the example is _utm_campaign, and the value is brandNew.

Behavior

Adding in-session behavior to activate a segment allows you to define visitor action on the website for which the targeting conditions are evaluated. For example, you can add the targeting condition as “visitors landing on your website through Facebook + US Region + iOS users + Click Buy Now CTA button”. Here, the visitor is included in the segment only after the visitor clicks the Buy Now button.

After the click event, VWO checks all the target conditions and includes or excludes visitors into segments accordingly. Please note that behavior targeting options are not available for split URL test and form analysis.

When you select Behavior as a target condition, the elements on which changes have been applied in the test are not hidden. If an element is visible to the visitor, they can see a flicker effect. It is advisable to take this into consideration while using behavior. To change this option, click Configuring the Segment Settings in VWO.

• Click on Element: Displays the changes when visitors click a predefined element on a page. If the element happens to be a hyperlink that redirects to another page, make sure that the redirected-to page is also a part of the test. You can use this option when trying to test items that appear on the page after any user action.
• Time Spent on Page: Selecting this option triggers the changes when a visitor spends “x” seconds on a single page. For example, if you have defined the time for the trigger as 10 seconds, the changes initialize when the visitor spends 10 seconds or more on a page.
• User Is Trying to Close the Page: Displays the segment changes when visitors attempt to close the test page. So when the cursor moves outside the browser viewport, VWO executes this trigger. You can use this option if you are trying different designs/content on the exit-intent popup on your website.
• Page Scroll Is More Than: Displays the changes when a visitor has scrolled the page for more than the defined percentage or pixels in this section. This option is helpful if you are trying to test changes on elements that are placed at the bottom of the page or only want to include the visitors that scroll to a certain section of the page.
• Custom Trigger: Displays the changes when the executeTrigger() function is executed. Users can add their own custom code, and then call the executeTrigger() function. This way, the custom trigger condition is fulfilled and the campaign is displayed. For example, When a visitor hovers over a section of the webpage / When a certain element is available on the webpage / After a visitor performs some action which closes a pop-up that appears on page load, etc..

Technology

• Operating System: Create segments based on the operating systems used by visitors. The example includes segmenting only for Mac OS users.
• Browser: Create segments based on the browsers used by visitors to access the test page.
• User Agent: Assign User Agent (UA) as a string to identify the browser or device used by a visitor to access the test page.
• Device Type: Create segments based on the devices used by visitors to access the test page like Desktop, mobile phones, and tablets.
  NOTE: VWO uses an open-source UA-parser library to detect visitor devices. The parser library categorizes the devices based on their types, and the library is regularly updated for new devices. The same library is used in the segmentation feature to target visitors based on their operating systems. You can access the source code here, and then use this regex to locate the code.
• Screen Resolution: [For Reports Segmentation only] Segment reports based on the screen resolution used by the visitors to access your website. Example: 1280 x 768.
• Document Encoding: [For Reports Segmentation only] Filter visitor data based on the character encoding technology used by the visitor’s system. Examples include US-ASCII, UTF-8, and so on.

Time

• Day of Week: Run your test for visitors who access your test page on specific days.
• Hour of the Day: Run your test for visitors who access your test page within specific hours. VWO considers the visitor’s local time zone and runs the test accordingly. If you set Hour of the Day is equal to 10, the test will run from 10:00–10:59 a.m.

Visitors

• Visitor Type: Select this option to create different segments for returning visitors and new visitors. VWO places a tracking cookie to determine if a visitor is new or returning. A visitor who is already a part of one of the tests running on the domain is classified as a returning visitor for a test.
• New Visitor: A visitor who is part of any test on the domain for the first time.
• Returning Visitor: A visitor who has already been part of another test running on the same domain.
• Location: Create segments based on visitor geography. The location of visitors is identified by using Maxmind to track their IP addresses.
• Visitor Language: [For Reports Segmentation only] Filter visitor data based on the language used by the visitors in their browser settings.
• Visitor ID: [For Reports Segmentation only] Filter visitor data based on their unique ID.

Others

• Cookie value: Create segments based on whether or not a user has a cookie from your website. Select this condition and then type the cookie value. VWO determines if a user qualifies for the test, based on the cookie value you have set. Please note that this condition works only if the cookie is accessible using JavaScript. VWO can read server-side cookies too, provided they are not restricted to be read by JS only.
• JavaScript Variable: Create your own custom Javascript condition to define a visitor segment. The test runs only if a user passes through the JavaScript condition while loading the pages.
  PRO-TIP: Ensure that the JS variable is available before the VWO tracking code executes so that the segmentation condition can be successfully checked.
• IP Address: This option allows you to target visitors, based on their IP addresses.
• Custom Dimension:[For Reports Segmentation only] This option allows you to categorize and differentiate visitors on your website. For example, if you are a SaaS company, you may want to categorize users based on their subscription plans or a travel agency that recently ran promotional offers may want to view conversion by age-group. To know how to create a custom dimension in VWO, refer to Creating a Custom Dimension in VWO.

NOTE: You can apply the cookie value, JavaScript value, or IP address 
parameters to target a test but not to filter reports for these segments.

 Select a Condition Match Type for The segment

• Enter details for the selected segment condition such as URL details, query parameters, or location, and so on.
• To create a complex visitor segment, use brackets and AND and OR operators to define your conditions.
  

  NOTE: To avoid a repeat of the task, you can create and save your
  custom segments. This way, you can reuse them in other features of 
  VWO again. To know about saved segments, refer to Saved Segments in VWO.