Skip to main content

How can we help?

Understanding the Conditional Branch node when building Subscription Experiences

Shopify Checkout integration Recharge Checkout on Shopify
Sections

The Conditional Branch node allows you to create multiple branches in a flow where customers are assigned to a specific branch depending on your specified condition(s).

This guide explains how you can leverage conditions in the Conditional Branch node for specific experiences, use cases, and considerations.

Platform:
  • Recharge Checkout on Shopify
  • Shopify Checkout Integration

How it works

The Conditional Branch node allows you to create multiple branches, each based on specific conditions. Customers who meet these conditions are directed to the corresponding branch. This setup enables you to move beyond simple IF and ELSE logic, allowing for more complex and tailored customer interactions.

Each branch is evaluated sequentially, with only the first branch that meets the customer's conditions being executed. If none of the conditions are met, an ELSE statement ensures that the customer still receives a tailored response. This system empowers businesses to craft personalized customer journeys that align with their goals and strategies.

2024-08-19 14-52-56.gif

You must set at least two branches, with a maximum of 15 branches allowed per flow. Branches are executed in order from top to bottom, and you can adjust their sequence when configuring the flow.

Additionally, you can get granular with conditions by using AND or OR logic. You can use up to 10 OR logic blocks within a Conditional Branch node and 5 AND logic blocks within an OR block:

  • Use AND logic to ensure all of the specified conditions are met.
  • Use OR logic to ensure any of the specified conditions are met.

Available conditions

Review the chart below for a full understanding of the available options you can use to build your conditions:

Condition category

Condition

Purpose
Customer

Number of active subscriptions

Target customers based on the total number of active subscriptions they have.
Customer

Subscription AOV

Target customers based on their Average Order Value across all orders in Recharge.

Recharge uses the total subscription spend divided by the number of orders to calculate the Average Order Value for Subscription Experiences.

Recharge calculates the total subscription spend by taking the price of the line items, subtracting any discounts, and then adding taxes and shipping. Refunds are not taken into account for this calculation.
Customer Total subscription spend

Target customers based on their total spend amount on all orders in Recharge.
Customer

Number of subscription orders processed

Target customers based on how many total orders in Recharge they have successfully processed, including both checkout and recurring orders.
Customer

Segment

Target a specific segment to have the Subscription Experience apply to select customers or keep a specific segment of customers from entering the experience.
Customer Streak count for subscription orders

Target customers based on where they are in their current subscription journey. This number represents how many recent orders a customer has had in sequence without any cancellations.
Line Item Variant

Target or exclude customers subscribed to a specific subscription product.

Orders only enter a Subscription Experience if they contain the subscription version of a product, even if the product can be purchased as both a subscription and one-time. If a processed order contains the one-time version of a product, it will not pass the line-item condition, despite having the same variant ID as the subscription version.
Line Item Collection

Target or exclude customers subscribed to an item(s) in a specified Collection. 

Orders only enter a Subscription Experience if they contain the subscription version of a product. The product can be purchased as both a subscription and one-time, but if a processed order contains the one-time version of a product, it will not pass the line-item condition, despite having the same variant ID as the subscription version.

Shipping address

 Country

Target or exclude customers based on the shipping country provided.
Shipping address Zip code

Target or exclude customers based on the zip code provided.
Note: Each condition has a variety of operators you can choose from, allowing you to get specific using the equals or does not equal to operators, or target a range of customers with the greater than and less than operators.

Number of subscription orders processed vs. streak count for subscription orders

Warning: It is extremely risky to use the number of subscription orders processed condition or streak count for subscription orders condition if you are setting the operators to is greater than one. All orders satisfy these conditions, and the experience will apply to every order that Recharge processes. This is not recommended unless you have flow run count limits set to prevent customers from receiving the incentive multiple times. See flow settings for additional details.

Both the number of subscription orders processed and the streak count for subscription orders conditions refer to the number of orders a customer has made across all of their subscriptions. The conditions are different, however, in how the experience handles customers who have cancelled and then reactivated their subscriptions. If all subscriptions belonging to a customer are cancelled by either the customer or an admin at any time:

  • The streak count for subscription orders resets to 1 on the next fulfilled recurring order
  • The number of subscription orders processed remains unaffected and does not reset

The example below outlines the difference between the two conditions: 

Step in the customer journey:

Checkout order processed

Recurring order #1 processed

Customer cancels all subscriptions

Customer reactivates their subscription, Recurring order #2 processed

Recurring order #3 processed

Number of subscription orders processed:

 1 2 2 3 4

Streak count for subscription orders:

 1 2 0 1 2
Tip: Use the number of subscription orders processed condition for experience that refer to a customer's entire history with your store, or the streak count for subscription orders condition to reflect the customer's current and continuous journey.

Use cases

Check out some of the most popular conditions other merchants are using when utilizing the Conditional Branch node, and how they’ve configured their conditions:

Use case

Branch configuration

Customers subscribed to specific products in a certain collection will receive an offer.

 

Remove the AB Test node and replace it with a Conditional Branch node using the A/B test new reward offering:

Branch conditions:

  • Line Item
  • Collection
  • Equals
  • Choose the collection

Add an Incentive node in the first branch to choose what incentive (discount or free gift) customers with subscriptions to products in the collection will receive (ie. a free sample of a related product).


All customers who don’t meet the initial criteria will go into the “Else” branch where no incentive is offered. 

Aim to reward customers who reach a streak order of 2 and consider their total subscription spend.

Set the Conditional Branch conditions as follows when creating a rewards offering:

Branch 1:

  • Customer
  • Total subscription spend
  • Is less than or equal to
  • $50 USD

Offer a low-level incentive tailored to this branch or no incentive. The subsequent branches focus on customers who have a total subscription spend higher than 50 dollars.

Branch 2:

  • Customer
  • Total subscription spend
  • Is greater than
  • $50 USD

AND

  • Customer
  • Total subscription spend
  • Is less than or equal to
  • $100 USD

Use this branch to create a range between $50 -100 total subscription spend. Offer a better incentive than the prior branch tailored to customers with a mid-range total subscription spend. 

The remaining customers fall into the “Else” branch, where you can choose to offer an incentive to reward their loyalty, as the remaining customers will all have greater than $100 total subscription spend.

 

Was this article helpful?
0 out of 0 found this helpful

Related articles

Didn’t find what you’re looking for?

Contact us