This post describes how to use Episerver A/B testing and Episerver Visitor Groups to test an entire customer journey against a Episerver A/B test KPI.
Why would you want to personalise based on a running A/B test?
Sometimes A/B testing an individual piece of content isn’t enough to really prove an outcome. A simple example could be does the text “Continue” or “Next” work best on a button on a checkout path. The button exists on multiple content items so would need to be changed in multiple places. By using Episerver Visitor Groups it should be possible to test multiple pieces of content on a site using visitor groups based on a running A/B test.
Episerver Digital Experience Cloud service (DXC-S) can host multiple customer sites in a single Episerver instance running on a single codebase. This is run on the cloud as a managed service delivered by Episerver and costed on a consumption based model. This is a good approach for organisations that want to share the consumption and managed service offered by DXC-S across brands/sites/countries/anything they wish. However it's not always possible to migrate multiple sites to Episerver Digital Experience Cloud Service (DXC-S) in one go and customers often may need or want to take a phased approach. It may not also be possible to run all sites off a single codebase. So this post describes some approaches when migrating to DXC-S.
Using Episerver Commerce it’s possible to offer discounts to customers using the built in discount engine. Discounts can also have a coupon code associated meaning only customers who know that code can get the discount. However, it’s not possible to assign individual coupon codes for customers using Episerver Commerce alone. On the other hand Episerver Campaign can create, allocate and distribute unique coupon codes to customers.
Episerver approval sequences are a great way of controlling how editors get their content signed off by visually defining a set of approval steps that content must go through before it’s considered approved. In organisations that have compliance requirements a common requirement is that editors should not be able to publish their own content. This has already been covered here: Adding custom logic to your publishing step.
Tags: Episerver 10 Oct 06, 2017