Workflow Conditions

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

At a Glance

• Introduction
• Examples of Differentiation (Segments vs. Workflow Conditions)
• Default Conditions
  • Visitor History
  • Commerce / Cart
  • Channel / Origin
  • Locale / Language
  • Device Type
• Important Note on ALL OF vs. ANY OF

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 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 (Segments vs. Workflow Conditions)

1. “New Visitors on the website”

• Segment:
  Cannot represent a “new visitor in the current session,” because the visitor’s session = 1 and segments do not update in real time.
• Workflow Condition:
  Logic is represented as “visitors whose all-time sessions = 1.”

2. “Cart Abandoners”

• Segment (Dynamic)
  • Logic: “Anyone who left the site with items in their cart in their previous session.”
  • Note: Once a person purchases, they are no longer a cart abandoner but a customer.
• Workflow Condition
  • Logic: “Include anyone who, in their current session, is leaving items in their cart and attempting to (or has) exited the site.”

3. “Has submitted form”

• Segment vs. Workflow Condition
  • Both rely on the profile property “email address” being known.
  • Workflow can specify whether the email address was updated “in this workflow,” while a Segment simply checks if the property is known (regardless of workflow).

4. “Email click-through visitors”

• Segment (Dynamic)
  • Logic: “Visitor has landed on a URL containing utm_medium=email in any (first, recent, or all) past sessions.”
• Workflow Condition
  • Logic: “A visitor who, in their current session, has landed on a URL containing utm_medium=email.”

Default Conditions (Organized by Category)

These conditions are populated in every website account once the account is created. All users can access them by selecting the “popular conditions” category within a workflow If/Then branch, an enrollment trigger, or the segment conditions section.

Visitor History

1. All Visitors

   • Logic: website behavior > sessions > is any amount > all time
   • Description: Includes all visitors to a website.
   • Use Case: Ideal for broad targeting where no specific segmentation is needed.

2. New Visitors

   • Logic: website behavior > sessions > is equal to '1' > all time
   • Description: Includes first-time visitors to a website.
   • Use Case: Great for a first-visit welcome promotion or onboarding.

3. Return Visitors

   • Logic: website behavior > sessions > is at least '2' > all time
   • Description: Includes visitors with at least one previous session.
   • Use Case: Offer different promotions or experiences to returning users.

4. Unidentified Visitors

   • Logic:
     events & audiences > profile properties > email address > is unknown
AND
events & audiences > profile properties > SMS number > is unknown

   • Description: Includes all visitors whose email and phone are unknown.
   • Use Case: Useful for encouraging visitors to sign up or provide their contact info.

5. 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 visitors who have submitted an email address or phone number in this workflow.
   • Use Case: Immediately follow up with a thank-you or confirmation step in the same workflow.

6. Visitors Whose Email Address Is Unknown

   • Logic: events & audiences > profile properties > email address > is unknown
   • Description: Includes visitors whose email address property is unknown.
   • Use Case: Prompt them to provide an email (e.g., “Sign up for our newsletter!”).

7. Visitors Whose SMS Is Unknown

   • Logic: events & audiences > profile properties > SMS number > is unknown
   • Description: Includes visitors whose mobile phone property is unknown.
   • Use Case: Encourage visitors to opt into SMS marketing if that’s part of your strategy.

8. 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.
   • Use Case: Show a loyalty offer or cross-sell to repeat purchasers.

Commerce / Cart

1. Returning Visitors with Items in Cart (Previous Session)

   • Logic (Suggested):
     commerce > items in cart > last session > is at least '1'

     (This logic was not specified in the original text, so adjust as needed.)
   • Description: Includes visitors returning to a website with at least one item left in their cart from a prior session.
   • Use Case: Perfect for re-engaging potential buyers who didn’t complete a purchase.

2. 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.
   • Use Case: Trigger a reminder or special offer to convert active shoppers.

3. Visitors with at Least $50 in Their Cart

   • Logic: commerce > cart total > subtotal > is at least '$50'
   • Description: Includes visitors with at least $50 in their cart.
   • Use Case: Encourage a upsell (e.g., “Spend $75 and get free shipping!”).

4. 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 visitors with under $50 in their cart.
   • Use Case: Offer an incentive to raise their cart total (e.g., “Add $10 more for a discount”).

Channel / Origin

1. 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 site or via an organic search (no paid content).
   • Use Case: Show a general first-visit offer or welcome message for organically acquired users.

2. 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 arriving from social media links.
   • Use Case: Present a social-specific promotion or gather UGC (User Generated Content).

3. 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 from paid ads or affiliate links.
   • Use Case: Tailor content to reflect the ad messaging or a special discount for paid ad traffic.

4. 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 returning visitors who clicked an email link to reach your site.
   • Use Case: Present a returning customer discount or highlight new product lines via email campaigns.

Locale / Language

1. 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.
   • Use Case: Provide region-specific offers or show currency options.

2. Visitor's Browser Language Is Spanish

   • Logic: locale & demographics > language > 'Spanish'
   • Description: Includes visitors whose browser language is set to Spanish.
   • Use Case: Display Spanish-language offers or bilingual content.

Device Type

1. Mobile Visitors

   • Logic: Technology > device type > is equal to 'mobile'
   • Description: Includes visitors using a smartphone.
   • Use Case: Serve mobile-optimized promos or reduce form length for phone users.

2. Desktop or Tablet Visitors

   • Logic: Technology > device type > is not equal to 'mobile'
   • Description: Includes visitors on a desktop or tablet device.
   • Use Case: Use layouts designed for larger screens or offer downloads (like PDFs).