To define which set of visitors should become part of a campaign while setting up a test, you can configure segments. Now, when a visitor lands on test pages, VWO verifies if the visitor is eligible for the test, applies changes you have implemented, and then starts collecting data.
Using the Settings option, you can now customize when to check for segment conditions, specify when the modified elements should be visible to users, or until when to look for changes in the code.
Check targeting conditions for a visitor
Select how you would like VWO to check for targeting conditions for your website visitors. By default, the option Once is selected and VWO checks for visitor settings only once and serves the same variation to the visitor on their subsequent visits. If you select Always, the visitor is evaluated against the segment condition on every visit to your website, that is, during every page reload.
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 campaign goal are triggered only after a visitor qualifies and collect accurate report data.
Note: By default, most A/B tests run when the page gets loaded. However, if you add a behavior action, the tests run only after users perform the defined action on the page. The changes are displayed to the visitors only after they fulfil the conditions and become eligible for a test. When a visitor triggers a goal, all targeting conditions except behavior are reevaluated.
Make modified elements visible when
When you make any changes by using VWO’s visual editor, VWO keeps a track of 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 modifications made to the element, applies those changes, and then displays the changes to the element for the visitor. This ensures that there is no flickering effect on the page when VWO is loading the changes for the visitor.
By default, elements are not hidden for Behavior targeting options. The modified elements are displayed to visitors as soon as the campaign executes. For behavior targeting, we do not hide the elements and change this setting to Always. The reason we do this is that VWO doesn’t know when the website visitor will click that defined element or try to exit the page. So by default, we don’t hide any elements on the page.
You can specify when to display changes to target visitors:
- Campaign executes – This is the default option when segments applying to the test does not involve behavior conditions. The changed elements are displayed as soon as VWO evaluates a visitor and determines if it is eligible for the segment or not.
- 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 takes an action on the page, or after a certain time gap, and so on.
- Always (elements are not hidden) – This is the default option if the segment applied for the test involves a behavior condition. The modified elements are not hidden during page load. Visitors who are a part of variation may experience a flickering effect on the page.
You can configure how you want to implement the polling mechanism by using these options:
- Polling Disabled – This is an option created for your currently running test. For all your existing tests, you will have this option selected by default. This is done to ensure that your current tests behave in the same way as they did before this feature was launched. You can also use this option to disable polling for any reason.
- DOM Ready: This is the default behavior where the polling ends when the HTML is loaded fully and parsed. To learn more about DOM Ready, click here.
- Custom Event – You can define a custom event until which the polling should run. For example, you may want to continue polling until the visitor clicks an element on the page.