[
https://issues.apache.org/jira/browse/UNOMI-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevan Jahanshahi resolved UNOMI-681.
------------------------------------
Resolution: Fixed
> JavaScript rendered personalization fallback not working (control group)
> ------------------------------------------------------------------------
>
> Key: UNOMI-681
> URL: https://issues.apache.org/jira/browse/UNOMI-681
> Project: Apache Unomi
> Issue Type: Bug
> Affects Versions: unomi-tracker-1.0.1
> Reporter: Kevan Jahanshahi
> Assignee: Kevan Jahanshahi
> Priority: Major
> Fix For: unomi-tracker-1.1.0
>
>
> h3. Steps to reproduce
> Add a personalization on a content
> Keep the display strategy to "First content matching conditions"
> Variant A - condition = has seen 2 pages (or any other condition)
> Variant B - no condition - fallback
> Set control group to 100% for the personalization
> publish
> h3. Observed behavior
> Variant A is displayed
> h3. Expected behavior
> Variant B should be displayed:
> if the session or profile is in control Group then the fallback should be
> displayed
> h2. Dev note:
> in the tracker personalization callback, in case we detect a control group we
> should use the fallback available in the strategy options.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
