How does Klaviyo handle boolean fields that aren't set?

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)

 

@KeviSunshine 

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. 

 

>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 @stem is showing: “IS FALSE” OR “IS NOT SET”?

@KeviSunshine  Unfortunately, what @stem  is showing only works on certain fields. It does not work on Boolean fields. When you go to add the boolean profile property, the only options you’ll have are True or False. You can’t say IS NOT SET. 

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. 

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.  

@stem Awesome, good to know - thanks! 

 @KeviSunshine Looks like you have two options here. Either include OR is NOT SET (Telling the condition that it’s a text based field instead of a Boolean) OR look for the true value and send your emails down the NO path.