You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@unomi.apache.org by "romain.gauthier (Jira)" <ji...@apache.org> on 2022/10/19 17:50:00 UTC

[jira] [Created] (UNOMI-690) Control groups dont work

romain.gauthier created UNOMI-690:
-------------------------------------

             Summary: Control groups dont work
                 Key: UNOMI-690
                 URL: https://issues.apache.org/jira/browse/UNOMI-690
             Project: Apache Unomi
          Issue Type: Bug
            Reporter: romain.gauthier
             Fix For: unomi-1.6.2, unomi-2.1.0


In short: I think visitors that are not in the control group can fall into it every time a variant is displayed, which means that if you're not in a control group, you just have to refresh the page until you fall into it (except if the traffic allocation for the control group is 0%)

h3. Steps to reproduce 
- Create a content personalization with variant A (fallback, no condition) and variant b (page views > 2) 
- Set control group to 25%, save & publish 
- Open anonymous browser, refresh, refresh, refresh, refresh - close browser 
- Open anonymous browser, refresh, refresh, refresh, refresh - close browser 
- Open anonymous browser, refresh, refresh, refresh, refresh - close browser 

h3. Observed behavior
After a 5-10 refresh, the visitor will always see the default variant. If you look in network, you'll see that the visitor is in the control group, always.
It looks like the control group calculation is done for every variant decisioning and that we dont store the fact that a visitor is NOT in a control group.

h3. Expected behaviours
- Visitors profiles that are in the control group for the personalization should stay in the control group - OK 
- Visitor profiles that are NOT in the control group for the personalization should stay out of it - KO 

Looking at the class 
https://github.com/apache/unomi/blob/master/services/src/main/java/org/apache/unomi/services/impl/personalization/PersonalizationServiceImpl.java
the problem is pretty obvious. 





--
This message was sent by Atlassian Jira
(v8.20.10#820010)