+7
Hey all,
If we have a boolean profile property and it’s not set, does that evaluate to false?
If I wanted to create a conditional split in my flow for anyone where the boolean field is false or not set, do I need to add both “is false” and “is not set” or will “is false” suffice?
In dev terms, is “is false” a strict check (“===”) or a loose falsy check (“==”)
Let me know.
Thank you.
Best answer by KeviSunshine
View original
+5
I’ve not run into this issue with a boolean yet, but I definitely add the appropriate “is not set” check for various numeric fields (some of which are effectively being used as T/F bits)
+18
Profile properties don’t exist on all profiles, only the ones that it gets added to. So unless you’re actively updating users with False on that property, it just won’t exist.
If memory serves, there isn’t actually a NOT SET option for boolean fields, so you’ll have to do the opposite. Look for the TRUE value on the split and then send the rest down the NO path.
+7
>If memory serves, there isn’t actually a NOT SET option for boolean fields,
That is correct.
So I will need to do something like
+18
So Instead, you’ll want your conditional split to say Boolean Field is TRUE.
Then the emails you intend to send to the False group would be added to the NO path of the conditional split.
+5
I get around the lack of “is not set” for other data types by checking as if it were TEXT. You can see that in my example. My segments are riddled with this. Seems to work for date fields as well. Check against the dates that exist and then pretend it’s a TEXT and check “is not set”
In my mind the TEXT:IS NOT SET is used in contexts where I’d use IS NULL as a distinct check from NOT EQUAL.
+7
Based on this convo, I believe it is necessary and that Klaviyo treats boolean checks as strict checks.
+18
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.