Evaluating not conditions

When the condition type is set to Exists in Session and is configured to evaluate Is false, you effectively created a not condition. These not conditions are evaluated as did not occur within the specified range of hits or time.

When a not condition is defined as the second event condition, execution of the distance event is delayed to the end of the session, even though an in-session trigger is specified for the event because non-existence of an event cannot be determined until session end.