Behavior of filtering by "Event is not"

[zepfietje]

Filtering by Event is not foo does not work the way I'd expect it to work.

I'm not quite sure how it currently works.
But it seems that if you have two events (foo and bar), and filter for Event is not foo, this yields the same results as filtering by Event is bar.

What I expect when filtering by Event is not foo, is to see all visitors who have not triggered the event foo.
This is different from the current behavior, and as far as I know there is no way to work around this at the moment.

@Kugelschieber could you explain the current/designed behavior, and elaborate on the possibility of supporting my expected behavior?

[Kugelschieber]

Events are their own thing right now. When you create an event, it will be stored in a separate table. So inverting the event filter does indeed show all other events.

[zepfietje]

Thanks for your explanation! Seems totally logical from a technical point of view.

However, I do think there is a huge use case for viewing visitors who have not completed a certain event.
Totally understand if this is beyond scope for now, but might be an idea for the future.

Also, since events are separate from page views at the moment, it's not possible to view entry/exit pages for visitors who triggered a certain event. This is something Plausible does support.

[Kugelschieber]

Plausible also has separate tables for events and page views. I don't know how they do it right now, but I will put it on our list.