Visual Automations Conditions
Send the Right Subscribers to the Right Place
Like Actions, Conditions are also polite, waiting until the previous step has completed. But, there is a very cool difference between a Condition and an Action.
Conditions ask a Yes or No question, and then direct the subscriber down the appropriate path, based on their answer. Pretty neat, right?
Conditions steps are indicated by a purple color, but it’s just a nice color, no hidden meaning.
The 2 Types of Conditions
The first way to use a condition step would be to check to see if the subscriber has a specific Tag.
- Does the subscriber have a Tag?
2. Does the subscriber have a Custom Field? Two sub-questions here:
a. Does the custom field exist?
b. Does the field content match the value provided?
Example 1: A subscriber completes a sequence, and you want to direct them different ways based on a tag or custom field. If a subscriber clicked a link in an email to buy your product, and you Tag them based on that click, but they did not purchase, you could send them a follow-up sequence, based on that “interest” tag.
Takeaway: Conditions are also patient, but then ask a question and directs the reader based on the answer. Basically “one of these two things can happen”.
Example 2: You attend a conference. Once you have your badge, you notice a purple dot on it. When you go to find a seat, the usher looks at it and says, “Oh, you have a purple dot! Please go sit in the front row, there is a seat there for you!”. Think of the purple dot like a tag, and the condition is asking, “If the subscriber has the Tag ‘purple dot’, then do this”.
You can use conditions a number of different ways, to switch subscribers through different Sequences based on Tags they have as a result of Link Triggers, Purchases, custom fields, and much more.
Example 3: You are hosting a webinar, and want to deliver a follow-up sequence, based on whether or not the subscriber has the tag, “Attended Webinar”. Create a condition that asks, “If the subscriber has the tag 'Attended Webinar', then do this." “This" could be delivering a specific sequence for attendees, while those without the tag are sent a separate sequence, or have a delay added, or nothing.
- Conditions are polite, waiting for the previous step to be completed (just like actions).
- Conditions ask a question that defines the next step.
- Conditions can be defined based on the presence of a tag or custom field, and if the custom field matches the value entered.
Up Next: Visual Automations FAQ! Click to Read