Optional Trait evaluation in a Segment

[dariomncs]

Hello!
I was trying to implement a Segment with a "% Split" excluding users with a specific trait, and as it is a new trait, few users have it.

What I found is that apparently the condition "doesn't match !=" implies a "trait exists", as all the users are appearing excluded when i add the AND condition, and re-included (following the other condition) when I remove it.

I'm doing something bad? There is a way to include users that doesn't have a specific trait, consider a trait optional or setup a trait value by default?

[dabeeeenster]

Hi @dario1985 - we don't currently have any rules that operate on the existence of a trait value. So what you are seeing is intended behaviour, but I can appreciate it doesn't work for your use case.

We do have this outstanding #1145 which we will try and get to!