This article applies to Nelio A/B testing versions prior to 5.0.

If you are looking for documentation for our newest version, please bookmark

In Nelio A/B Testing there are two types of A/B experiments:

  1. Experiments that modify a certain page or post, and whose alternatives only affect that very same page or post.
  2. Experiments that have a global impact on your website, such as:
  • CSS or Theme experiments, which modify the look and feel of your website,
  • Menu or Theme experiments, which modify elements that are common to several pages,
  • or Headline experiments, where Headline alternatives are shown anywhere on your site.

Let's consider an example of the first type: a new A/B Test for Posts. When creating alternative versions of a post, you can modify the title, the featured image, the post content, the excerpt, and several meta options of that post. Some of these changes (for instance, the title or the featured image) do not only affect the post itself, but also other pages. Thus, for instance, any widget that contains a reference to that post or the Latest Posts page could be showing its title and featured image... but which one? The original version or the appropriate alternative?

Using the previous option under Nelio's Settings, you can select how the plugin should behave:
  • Force Consistency All Along the Site. All pages will request an alternative version, so that if they contain a reference to a tested element, the appropriate alternative of that element is shown. This setting might be a little bit slower (all pages trigger a "load alternative" request), but all the elements in your website will be consistent and the user experience will be better.
  • Load Alternative Content for Tested Element Only. If consistency is not forced, alternative content will only be loaded when accessing a tested page or post. This setting might be faster (for the vast majority of pages/posts in your website, an alternative loading request will not be necessary).