Fairly basic scenario. In Sales Cloud, a custom record is created or updated (boolean field equals TRUE) it will inject the related Contact to the Journey and that's that. This specific Journey allows multiple entries.
What is the most sensible way to Exit a Contact from a Journey if same example record is changed in Sales Cloud, so that the boolean field now equals FALSE?
It seems that the Exit Criteria is fairly limited, by allowing to check only Contact Data path which means it's not usable for Journies allowing multiple entries for the same Contacts.
Same with Decision Split activity with Attribute-to-Attribute comparison, as this does not allow to check nullable fields.
Similar question was raised in February about using SF source based entries and Exit Criterias but recieved no attention.
Any suggestions?
Best Answer
While using decision split, you don't need to perform attribute-to-attribute comparison as the use case here is to check a value from Sales Cloud. Also, if your journey has waits before the decision split, then this method would work as if a value is changed in Sales Cloud, in order to get it synchronized into Marketing Cloud and update the DE, it will take some time(min. 15 minutes). Then in order to get the updated value, you need to create Attribute group in Data designer to link your DE. In Decision Split you need to use Contact Data instead of journey data to check if that particular field is true or false. If false, then exit the journey.
We had this exact scenario in our implementation and this method worked absolutely fine.