[
https://issues.apache.org/jira/browse/UNOMI-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18095506#comment-18095506
]
Serge Huber commented on UNOMI-697:
-----------------------------------
h2. Re-targeted to unomi-3.2.0
Moved fixVersion from {{unomi-3.1.0}} to {{unomi-3.2.0}}.
Scope-level *global* control group (fixed percentage at profile creation,
stored on scope) is new product behaviour. Unomi already supports control
groups at *personalization* time via {{ControlGroupPersonalizationStrategy}}
and {{controlGroup}} strategy options — that is a different model from this
ticket.
Implementing scope-level global control group needs scope schema changes,
profile-creation hook, and AB-test interaction design. Not required for 3.1.0
GA.
h2. Workaround for 3.1
Use per-personalization {{controlGroup}} configuration in strategy options (see
personalization docs and {{ControlGroupPersonalizationStrategy}}).
> Control group by scope
> ----------------------
>
> Key: UNOMI-697
> URL: https://issues.apache.org/jira/browse/UNOMI-697
> Project: Apache Unomi
> Issue Type: New Feature
> Reporter: romain.gauthier
> Priority: Major
> Fix For: unomi-3.2.0
>
>
> Some organizations need to exclude a percentage of their audience from all
> personalizations (and eventually AB Tests).
> In Unomi 2, there is a new object for scope, it could be used to store the
> percentage of visitors that should be excluded from all personalizations.
> Then, when a profile is created, the service would first look into the scope,
> and associate the profile with the presence or the absence of the global
> control group
> To keep in mind: we dont want to associate the profile and the global control
> group every time a personalization is resolved, otherwise too many profiles
> would end up in the global control group.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
