A/B testing Alerts/Limits #2365
Replies: 7 comments
-
Adding the last discussion that we had on this. We will spec out and add support for global variables to potentially solve this.
Also we should check this issue in Rapidpro for some insights on this https://github.com/rapidpro/rapidpro/issues/1017 |
Beta Was this translation helpful? Give feedback.
-
We already have the global variables for flows and some of the NGOs are using it. It's just that those are not exposed in the UI yet. |
Beta Was this translation helpful? Give feedback.
-
@glific/glific-frontend-team can you add a new field in the organization setting to update the organization/global fields. |
Beta Was this translation helpful? Give feedback.
-
We need a writable global field here @pankaj-ag. The usecase is to know how many people passed through a particular node and take action based on that. Right now we have readable global variables which will not help much in this use case. |
Beta Was this translation helpful? Give feedback.
-
Okay @mdshamoon but can't we use collections for this type of use case? Let's connect sometimes and discuss. |
Beta Was this translation helpful? Give feedback.
-
Sure let's connect tomorrow after call and discuss this. |
Beta Was this translation helpful? Give feedback.
-
Is your feature request related to a problem? Please describe.
When a user employs the split randomly node, they do so for an intended sample size, say 500 people. Currently they have no way of knowing when the required sample has successfully run through the test so that they can stop the test, neither does the node stop the test automatically.
Describe the solution you'd like
In an ideal scenario, once the desired sample has run through the A/B testing node, the user gets an alert informing them that the required sample has run through the node and asks them if they would like to redirect users to the default flow. The user should be able to click yes/no and the redirect to the default flow should happen automatically.
Describe alternatives you've considered
The alternative would be just sending the alert, informing that sample has been fulfilled and that they should check their analytics for the test and then alter the flow so that the test is no longer active (ie: send users to the default flow)
Additional context
You can refer to the KEF support channel for further context: https://discord.com/channels/717975833226248303/971657960726081576/1073090925284302930
Beta Was this translation helpful? Give feedback.
All reactions