Try our conversational search powered by Generative AI!
AI OnAI Off
A/B Testing ClientScript Inserting
Hi A\B Testing uses cookies to determine who is in the test and should be counted as a view, and subsequently who should be converted after they have been counted as a view. Tests themselves have a participation percentage that determines what percent of users should even be counted as a view, which defaults to 10%. So if the participation perctent is left at default and 100 people visit a page under test only 10 will be counted as a view, and those 10 have the chance to convert given your client script.
From your description of behavior it seems to be the most likely cause for some page visitors not triggering the client conversion. For testing of KPIs we create tests with 100% participation so that all users visiting the A\B tested page will be included as test participants and so we can see right away if the expected conversion conditions actually generate results for the test.
Jun 20, 2017 17:12
This topic was created over six months ago and has been resolved. If you have a similar question, please create a new topic and refer to this one.
Hi all,
I have a question about A/B testing. We created custom KPI with client script, tested this script, its works correctly. But when we tried to start test, it not counting our users and EpiServer don't insert client code to the page.
Could anyone provide more details about how it works?
How does it know, that user already existing or already passed test?
Because most of users don't get any client scripts for a/b testing. We tried from different browsers, we cleared all session data with cookies and etc. No results.
As I could understand after my investigation, if you already pass one test and start another, its already counting you as existing user. Also after you just pass the test, EpiServer stops inserting a/b testing code to client page.