This website works best with JavaScript enabled. Learn how to enable JavaScript.

Segment Settings and How to Configure Them

Last updated

Segment Settings allows you to configure how VWO segmentation and targeting conditions apply to a test and how visitors are evaluated to be eligible for a specific segment. By using the Settings option, you can manage the following:

  • Set up how VWO should check visitor’s segment condition.
  • Decide when to display the modified elements.
  • Until when should VWO look for the specific changes in the code.

For example, VWO stores information when a visitor becomes a part of any test. The information is stored when the visitor qualifies for a segment and becomes a part of a test for the first time. From there on, when the visitor lands again on the test pages, VWO will look for the cookie rather than checking the segment conditions every time. With the new settings option, you can configure how you would want to check the segment conditions of the visitors.

Check Targeting Conditions for a Visitor

Under this section, you can select how you would require VWO to check for targeting conditions for your website visitors. By default, the option Once is selected, which means the visitor segment condition is only checked once and the same variation is served to the visitor on every subsequent visit.

If you select Always, the visitor is evaluated against the segment condition on every visit to the website (every page reload). When this option is selected, the visitor is evaluated for the segment conditions on all goal pages as well. It means that when visitors clicks a button or visit a page defined as a goal in your test, they must satisfy the segment conditions for their conversion to be recorded.

For example, you create a personalization campaign that shows particular content to all visitors landing on your website from a Google ad. You want to ensure that visitors who do not come from this ad are not shown this content at all. For such cases, select Always to check visitor eligibility on every page they visit, to make sure that the changes are implemented and displayed only when the visitor qualifies for the segment. This will ensure that the campaign goal is triggered only after a visitor qualifies and will collect accurate report data.

Note: If your targeting condition contains Behavior options, the visitors are evaluated for all conditions excluding the defined behavior (like click on an element). The changes are displayed to the visitors only after they fulfil all other conditions and become eligible for the test.

Make modified elements visible when

When you make any changes by using VWO’s visual editor, VWO tracks all the elements that are changed. When a visitor lands on the test page, VWO first hides all the changes during page load, fetches the changes made to the element, applies those changes, and then displays the modified elements to the visitors. This ensures that there is no flickering effect on the page when VWO is loading the changes for the visitor.

You can use this section to specify when to show the modified elements to the visitors by using one of the following options:

  • Campaign executes – Display the changed elements as soon as VWO evaluates the eligibility of the visitors for the segment. This is the default option when the segment does not involve behavioral conditions.
  • DOM Ready – Elements are displayed when the HTML is loaded fully and parsed. To learn more about DOM Ready, click here.
  • Custom Event – You can define a custom event according to which the changes load. For example, you may want to display the elements only after a visitor performs an action on the page, or after a certain time gap, and so on.
  • Always (elements are not hidden) – The modified elements are not hidden during page load. On selecting this option, visitors may experience a flickering effect on the page reload when the original content is updated. This is the default option if the segment involves any Behavior condition (like click on an element, or user is trying to close the page).

Note: By default, elements are not hidden for Behavior targeting options (like click on an element). This is is because VWO doesn’t know when the website visitor will click that defined element or try to exit the page. So, the elements are not hidden on the page by default. You can change this option per your test requirements.

Poll until (applies to javascript variable and cookie value)

If you are using a JavaScript variable or a cookie value for setting targeting conditions, VWO will check the segment condition until DOM Ready. This ensures that all variables/cookies are initialized on the page.

Note: The Poll until option is disabled if you are not using a cookie or JavaScript value for segment conditions.

You can configure when to stop polling for a variable/cookie by using these options:

  • Polling Disabled – You can use this option to disable polling for a JavaScript variable and a Cookie value. It means that VWO will not wait for all the variables/cookies to initialize and will evaluate the visitor segment condition as soon as VWO smart code executes on the page. You may find this condition selected for tests created before this feature was launched.
  • DOM Ready: This is the default selection where polling ends only when the HTML is loaded fully and parsed. To learn more about DOM Ready, click here.
  • Custom Event – You can define a custom event till which the polling should run. For example, you may want to continue polling until your CRM variables are loaded on the page.
  • Condition is true – The polling runs until the specified JavaScript variable/Cookie value conditions are met for the visitor. When this option is selected, the condition is periodically evaluated for an infinite time; therefore, it should be used with discretion.

Was this article helpful?

Thanks for your feedback!
Please email us at to tell us what you were looking for. We'll send the answer to your inbox.

Contact Us / Login