expand the attribute split to go beyond just "known" and "unknown"

Essentially there is no way to split traffic based on collected attribute other than known vs. unknown. The use case I've seen come up a number of times is a client has a screen that other screens later within the experience will be split to feature different q/answers- i.e. I ask what event a customer is shopping for in the experience and want to ask different questions and provide different potential responses later on in the experience dependent on this one response. The challenge is there's no way to split via the attribute you collected and it ends up being simpler to branch however this involves reworking the structure of the full experience or deal with excessive branching throughout the entire experience to keep the screen order as is.