Jeff Wallace
Dec 30, 2009
  5238
(1 votes)

CMO LPO “Visitors Included in the Test” Setting Explained (based on CMO 1.0)

CMO allows the user to configure the percent of users included in an LPO test via the “Visitors Included in the Test” setting.  One of the main reasons for this configuration is because some customers, especially those with high traffic sites, may not want all of their traffic to be included in the test.  Questions have arisen regarding how this works so I thought it might be useful to post some of the details in a blog.  The information below represents my understanding.  If anyone disagrees or has additional feedback feel free to add your input.

The visitors included in the test can be up configured to a value of up to 100%. That configurable amount of traffic included in the test will then be divided equally amongst the number of pages included in the actual test.  This means that if two pages are included in the test the traffic division will be split 50%/50% for the percentage of visitors included in the test.  If there are three pages included in the test the traffic division will be roughly 33%/33%/33% for the percentage of visitors included in the test.   In both of the previous sentences I highlighted “percentage of visitors included in the test” mainly because there is an entirely different bucket of visitors which is those visitors NOT included in the test.

In order to help clarify I will provide an example of one possible configuration:

If you specify 20% of visitors to be included in the test and have two page variants, the original which I’ll call ORIGINAL PAGE and a variant which I’ll call TEST PAGE A, the end result will be that 10% will be included in the test and see ORIGINAL PAGE, another 10% will be included in the test and see TEST PAGE A, and 80% will still see the ORIGINAL PAGE but will NOT be included in test.  The 10% for ORIGINAL PAGE and the 10% for TEST PAGE A total the 20% that was configured to be included in the test.  The image below represents this distribution:

image

Additional details on this configuration setting can be found in the EPiServer CMO User Guide.  I hope this helps.

Dec 30, 2009

Comments

Please login to comment.
Latest blogs
Optimizely CMS 13: Why Search & Navigation Now Means Graph Migration

Optimizely CMS 13 makes Graph a required part of the platform. Here is what that means in practice for teams moving from Search & Navigation, with ...

Wojciech Seweryn | Apr 8, 2026 |

Jhoose Security Module V3.0.0 – Site-Level Security Configuration for Optimizely

Jhoose Security Module updated for Optimizely CMS 13, introducing separate packages for CMS 12 and 13 with ongoing support and enhancements.

Andrew Markham | Apr 6, 2026 |

Searchable settings page

In my current project which has been actively developed for quite some time we have a big classic settings page. Unfortunately the placement and...

Per Nergård (MVP) | Apr 6, 2026

Using Azure Devops Pipelines in Optimizely SAAS (Configured) Commerce

Introduction When working with SAAS Commerce build service v2 your currently need to use a github repo with configured branches to start deployment...

Mark Hall | Apr 4, 2026 |

Forcing Lowercase URLs in Optimizely CMS During Auto-Translation

Learn how to fix uppercase and punctuation issues in Optimizely CMS 12 URL segments caused by LanguageManager auto-translation using a custom...

Stuart | Apr 2, 2026 |

Stott Robots Handler v7 for Optimizely CMS 13

Stott Robots Handler version 7 is now available for  Optimizely PaaS CMS 13 . This is includes updates to support the switch from a Site based...

Mark Stott | Apr 2, 2026