I´m currently creating a Journey, which contains the following specifics:
Use case: as soon as a booking in category "1" was done yesterday by a customer, this booking should be injected into the journey, sending them emails to book again. It is possible, that the customer did 2 or more bookings yesterday, one in category "1", and another in category "2". The journey is following different paths per category. Now, if the customer books again in category "1", this record should exit the journey, whereas the booking from category "2" should remain and go on.
Entry Event is an Automation Studio Audience, sending this filtered Data Extension into the Journey (all bookings of yesterday without future bookings). This works fine, the wished records are filtered and are injected.
My issue now is that the Goal criteria are to have the record for category "1" exit the journey once on a related Data Extension (the booking table that is not filtered, but updated daily, so it can be used to check the goal criteria), a field is not null. This somehow works, but what happens is, that both records are marked as "journey goal reached", even if only one of them actually met the criteria, so it looks to me like the journey is not checking whether the individual booking records have reached the goal, but whether any booking of the customer did, and hence exits all records of this customer.
Does anyone have a clue why and whether there is a way to solve my issue?