Conflict avoidance for multiple Journeys (Spam protection)
When using many different Automations in parallel (e.g., welcome sequence, Abandoned Cart, reactivation), there is a risk of overlap. A Recipient already active in a Journey must not be overloaded by the start of another Journey. While an important sequence is running, other Triggers for this person can be paused or ignored to avoid clogging the inbox.
Logical checks within a Journey (Relevance check)
Circumstances can change between the start and end of a Journey.
Example: UWG-7 customers. Before each Email, verify the Opt-in still exists. A Condition checks the current Status shortly before sending and stops the automatic dispatch if consent has been withdrawn.
Procedure in JUNE
Conflict avoidance between multiple Journeys
At the start of a Journey, assign a Tag as one of the Services in the triggering Automation (e.g., Tag: Welcome-J). Upon completion, remove this Tag via a Service in the final step (removing the Tag tag).
To exclude a user from a new Journey if they are active in another, use Tags in the Conditions. Add a Custom Segmentation. Rule: Tags - is not - [Tag of the other Journey].
The Condition prevents activation if the user already carries the specified Tag.
Logical checks within a Journey
The Automation is triggered by an Order (Trigger: data item places order). This triggers the assignment of the Tag UWG-7 (adding the Tag tag "UWG-7"). If a customer objects, the Tag must be removed from the data item.
Before every communication step in the Journey, verify the Tag is still assigned. Add a Custom Segmentation as a Condition to each step. Rule: Tags - is "UWG-7". The Service only activates if the Recipient has not revoked consent.