Conditions
      Back to home
      1. Knowledge Base
      2. Experiences
      3. Conditions

      Workflow Conditions

      In this Justuno Support Article, we will cover how to use Workflow Conditions

      At a glance:
      Introduction
      Conditions

      Last update: 9/22/2022

      Introduction

      Workflow conditions are used in both the enrollment trigger (there is no "else" branch, the visitor is simply not enrolled) and subsequent if/then branches inside of a workflow. While segments can be used to build workflow conditions, the main differentiator is that conditions can look at real-time behavior of a visitors and change their path in the workflow. Therefore, a workflow condition can target a current event or behavior, while a segment can only target a past event or behavior.
      Examples of differentiation
      1. "New Visitors on the website"
        1. Segment: this cannot be represented in segments, because the visitors's current session is equal to 1 and segments do not update in real time.
        2. Workflow Condition: the logic is represented as "visitors whose all time sessions equal 1"
      2. "Cart abandoners"
        1. Segment (dynamic): the logic is represented as "anyone who left the site with items remaining in their cart in their previous session". Note: once the person purchases, however, they no longer a cart abandoner, but a customer.
        2. Workflow Condition: the logic is represented as "include anyone in their current session who is leaving items in their cart and attempting to or has exited the site"
      3. "Has submitted form"
        1. in this case, both the segment and the workflow condition would be represented by the same logic, since they both rely on the profile property for "email address" to be known, and has already happened in the past.
          1. In a workflow, you can specify whether the email address profile property has been updated "in this workflow", whereas a segment will rely on the profile property to be already known, regardless of workflow.
      4. "Email click through visitors" (this is just one possible variation of a use case that can be built in both workflow conditions and segments)
        1. Segment (dynamic): the logic is represented as "visitor has landed on a URL containing 'utm_medium=email" in their first session, recent session, or any session"
        2. Workflow Condition: the logic can be represented as "a visitor who, in their current session, has landed on a URL containing "utm_medium=email".
      Below are the default conditions populated in every website account once the account is created. All users will have access to these conditions by selecting the "popular conditions" category within a workflow If/Then branch, or Enrollment trigger, as well as the segment conditions section.

       Conditions

      • All visitors
        • Logic: "website behavior > sessions > is any amount > all time"
        • Description: Includes all visitors to a website.
      • New visitors
        • Logic: "website behavior > sessions > is equal to '1' > all time"
        • Description: Includes first time visitors to a website.
      • Return visitors
        • Logic: "website behavior > sessions > Is at least '2' > all time"
        • Description: Includes website visitors with at least one previous session in the past.
      • Unidentified visitors
        • Logic: "events & audiences > profile properties > email address > is unknown <AND> events & audiences > profile properties > SMS number > is unknown"
        • Description: Includes all visitors to a website whose email address and phone number is unknown.
      • Visitors who have submitted a form in this workflow
        • Logic: "events & audiences > profile properties > email address > has been updated > in this workflow <OR> events & audiences > profile properties > SMS number > has been updated > in this workflow "
        • Description: Includes only visitors whose email address or phone number have been submitted in this workflow.
      • Visitors whose email address is unknown
        • Logic: "events & audiences > profile properties > email address > is unknown"
        • Description: Includes visitors whose email address property is unknown.
      • Visitors whose SMS is unknown
        • Logic: "events & audiences > profile properties > email address > is unknown"
        • Description: Includes visitors whose mobile phone property is unknown.
        • Description: Includes visitors returning to a website with at least one item left in their cart in the previous session.
      • Returning customers
        • Logic: "commerce > items purchased > any items purchased > last session"
        • Description: Includes visitors returning to a website after completing a purchase in a previous session.
      • New direct or organic visitors
        • Logic: "website behavior > channel > is one of > 'direct' > this session <OR> website behavior > channel > is one of > 'organic' > this session <AND> website behavior > sessions > is equal to '1' > all time"
        • Description: Includes new visitors coming directly to the website without clicking through from paid content.
      • New visitors clicking through from social media
        • Logic: "website behavior > channel > is one of > 'social media' > this session <AND> website behavior > sessions > is equal to '1' > all time"
        • Description: Includes new visitors coming to the website by clicking through from paid social content.
      • New visitors clicking through from paid channels
        • Logic: "website behavior > channel > is one of > 'paid' > this session <AND> website behavior > sessions > is equal to '1' > all time"
        • Description: Includes new visitors coming to the website by clicking through from paid media content, i.e. ads or affiliate channels.
      • Returning visitors clicking through from an email
        • Logic: "website behavior > channel > is one of > 'email' > this session <AND> website behavior > sessions > is at least '2' > all time"
        • Description: Includes website visitors with at least one previous session in the past coming to the site by clicking through from an email.
      • Visitors with at least one item in their cart
        • Logic: "commerce > cart total > item quantity > is at least '1'"
        • Description: Includes website visitors with at least one item in their cart.
      • Visitors with at least $50 in their cart
        • Logic: "commerce > cart total > subtotal > is at least '$50'"
        • Description: Includes website visitors with at least $50 in their cart
      • Visitors with less than $50 in their cart
        • Logic: "commerce > cart total > subtotal > is at least '$1' <AND> commerce > cart total > subtotal > is at most '$49'"
        • Description: Includes website visitors with under $50 in their cart.
      • Visitors from outside of the USA
        • Logic: "locale & demographics > country > is not equal to 'USA'"
        • Description: Includes website visitors whose browser location is outside the United States.
      • Visitor's browser language is Spanish
        • Logic: "locale & demographics > language > 'Spanish'"
        • Description: Includes website visitors whose browser language is set to Spanish.
      • Mobile visitors
        • Logic: "Technology > device type > is equal to 'mobile'"
        • Description: Includes website visitors on a smartphone.
      • Desktop or tablet visitors
        • Logic: "Technology > device type > is not equal to 'mobile'"
        • Description: Includes website visitors on a desktop or tablet device.

      IMPORTANT NOTE: 

      When building workflow conditions, it is also important to recognize the distinction between ALL OF versus ANY OF clauses.

      ALL OF requires that all of the stated inputs be present for the condition to be true.

      ANY OF requires that any one of the stated inputs be present for the condition to be true.