A/B Testing Feature Beta
The Episerver A/B testing feature is now officially in beta and is available on the Episerver NuGet feed. Current support is for the CMS and a single KPI (page or block winner). Commerce support and more KPI's are in development and will be available in beta soon. The new User Guide which includes a section on A/B testing will be available shortly as well - In the mean time you can access the beta doc here: A/B Testing Beta Doc Give it a try and let us know what you think.
Oct 17, 2016
This is nice! btw, typo: first sentence -"om".
ommm :) glad to hear!
Great!!
Will Conversion goal be extendable in future release (expanding the scope to commerce, where conversion goal can be product added into cart)?
Will A/B testing be available at IContent level (expanding the scope to commerce/blocks)?
Will we be able to specify visitor percentage for A or B?
Wow .. this is cool .. is that possible to define custom target .. for exmple clicking on each item in menu is our target!? So find which version of menu is attract more people to click!?
@Khurram
It already supports blocks, I believe commerce products is next. Not sure about the rest!
@Aria
I believe this is in the roadmap.
There will be technical session in Ascend Europe and Ascend Nordics about this. So register if you haven't already and you can ask more questions there :)!
A question: How much would the A/B testing be dependant on having Session activated? If so, is it possible to change where the information should be stored (such as cookies?)
This looks good, a few questions and comments from me also:
Will this deprecate the self optimizing block for instance or do you still see a future for this?
I am guessing that CMO will finally be killed of right?
I wold also prefer that you do not rely on any session storage as that kills this functionality in load balanced environments(friends do not let friends use sticky load balancing) not to mention kills performance in general because of locks.
Also, could all the internal EPiServer solution architects please align on what data access strategy to use, some EPiServer addons use DDS while others use Entity Framework, it really is a mess. Decide on one and go with that. DDS is easy to use but has serious performance issues when you need to save/retrieve even simple object graphs and EntityFramework has its own issues but works for better in for example Azure because of the retrying capabilities.
@Alf, we are using cookies to do storage so LB scenario shouldnt matter.
@Thomas, we use DDS for simple storage and configurations but we are using other forms of storage for other things. We often look at aligning our future technology choices and appreciate your feedback. As you are stating there are advantages to either method and for AB testing we are currently using this architecture.
Hi Sterry
Is it possible to link two separate AB Page Testing together?
Regards,
Vincent
The current implementation is for a single A - B test. We may extend to do multi-variant in the future but it's not part of the product now.
A nice read, unfortunatly the link to the PDF document is broken.
@Daniel Sandberg, A/B testing is no longer in Beta and the official documentation can be found here: http://webhelp.episerver.com/latest/cms-edit/ab-testing.htm.