Logic in filters/audience

[fghfghfghfghfgh]

Hello. I'm building a filter in CJA, that is for an aborted application. Meaning, has entered a process, but no receipt.

I'd like to know why the following logic does not work.

But this does.

To clarify, the second in both of these is receipt step.

When I test the first one, I get users with receipts, but not the second one. I've tried different versions of the first one, exclude etc. It seems logical, and would be much easier for people if they could build it that way. Difficult to explain to people that they have to put uniqe visitior container in an event container.

[MandyGeorge · Accepted solution]

So there's a difference between "does not equal" and "exclude" when it comes to segment logic. You've got a segment at a visitor level, so the segment is going to look at every hit for that visitor and compare it to the conditions in your statement. So it looks at a hit and says "does not equal X", if it matches that it brings it in. So if your visitor has one hit that does not equal those steps and one hit that does, because one of those hits matches the condition it's going to bring in the entire visitor. On the other hand, the exclude removes the entire visitor. It looks for the condition and if any hit in the visitor matches, it excludes the entire visitor. 

This article does a great job of explaining in more detail the difference between does not equal and exclude. The magic behind the curtain: Complex segments: excludes, containers, and attribution

[Jennifer_Dungan]

Yep...As Mandy said, "does not equal" is very different from "exclude" (particularly at visitor scope)