You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The SplitView has a number of useful fields including the name, treatment, and configs, but there is no way to access the tags. Can we have that field exposed?
The text was updated successfully, but these errors were encountered:
Hi @maplealmond, thanks for the inquiry, I would need to submit a feature request on your behalf, could you provide which company you work for if any, and business case to use tags?
Our business case is as follows: We have a large library of conversational snippets used in a chatbot. Often, we want to AB test one specific bit of language. We have been doing this by matching up the split name to the message ID, which allows us to dynamically run a test without having engineering define the split as talking to the question.
However approach this has two downsides. The split can only apply to a single question and sometimes we'd like to show/not show a bunch of items together. Additionally, the question IS is not an ideal name for a split, and looks awkward.
Being able to match up tags to question IDs would let our content creators run experiments with clear names and also to attach it to various elements without engineering needing to hook it up.
The SplitView has a number of useful fields including the name, treatment, and configs, but there is no way to access the tags. Can we have that field exposed?
The text was updated successfully, but these errors were encountered: