Matching logic for multiple conditional steps
The Automation platform is constantly checking new and modified contacts to see if they match condition(s) for any workflows. Once a contact matches your first condition block and is successfully enrolled into the Automation workflow, how they continue to qualify for the workflow when multiple conditional steps exist depends on the matching logic you define.
While a contact may initially qualify and enroll into an Automation Workflow, a contact can also be removed before the workflow is completed. Either manually by an administrator or workflow owner, or logically based on the rules of your workflow. If an enrolled target no longer matches the matching rules for your workflow, they can be automatically removed.
The matching logic defines the rules for how multiple conditions blocks are treated as a contact navigates through the linear journey through the automation.
| Smart |
Smart workflows are exactly that, smart. The first condition block must ALWAYS continue to match for future actions to take place as a contact continues through the workflow. Smart logic allow you to create intelligent, goal-driven workflows that will enable you to target contacts as long as they continue to meet a specific profile (as defined by the first condition block), up until that profile changes. Use case: If you select Smart logic with a Tag condition that requires a specific Tag assignment, and include that condition into the first condition(s) block, then the contact MUST continue to be assigned that tag in order to continue qualifying for the workflow. If the tag assigned to the contact is ever removed, then the workflow immediately ends for that contact. |
| Current Condition |
By selecting Current Condition matching logic, then the Automation workflow will only consider the current Condition block that a contact has reached. The logical engine will not check to see if any previous condition rules are still true. In effect, any previously matched conditions are irrelevant and all that matters is the path ahead. Use case: A contact has been enrolled into an Automation workflow based on their lead score reaching a specific threshold, but that lead score subsequently changes. The contact will continue to qualify for actions that followed the first condition block and the contact will be considered for additional condition block(s) that are contained in the linear journey of the workflow. The Automation Workflow will not automatically end for this contact. |
| Current and Previous Conditions |
Current and Past Condition matching requires that all previous conditions that a contact matched in an Automation Workflow must continue to be true. Before any additional actions trigger, the logic engine will re-check all previous conditions to ensure that every previously matched condition in their journey is still true. Current and Previous Condition logic is similar to Smart logic, except that Smart logic will only re-check the first condition block to validate that it's still true. |
Comments
0 comments
Please sign in to leave a comment.