How can we help?

Orchestration fork and skip action

Overview

The Podium fork component gives you the ability to create multi-path forks within an Orchestration and then choose which path contacts should follow based on qualifying criteria. You have the ability to skip the action component in any of the forked paths, so contacts who don't meet message criteria can remain in the Orchestration and continue through an alternative Orchestration path. 

Additional features Notable exceptions
  • Prioritize paths for contacts who qualify for more than one.
  • Create as many paths as needed within a single fork.
  • Forks converge on a merge node from which additional automations can be created.
  • Experiments do not support forked paths but a fork component can be added underneath experiment results of a winning variant.
  • Forks cannot be nested.
  • Forked paths cannot be added directly underneath Recurring and Date or timestamp triggers.

Example

This example will recreate the cart abandonment Podium Orchestration, but this time, using a fork to configure three distinct paths. The qualifying criteria for each path will be based on the total value of an abandoned cart.

To get started, we created a new Podium Orchestration using the cart custom event as the contact’s real-time behavior trigger. You can add the fork component by hovering over the plus icon directly underneath the trigger and selecting Add fork.

Forks can also be added underneath action components.

Fork settings

1. After clicking Add fork, the fork settings pane will appear for you to provide the fork name as well as add, configure, and prioritize paths.

A valid fork consists of at least two paths, each with a unique name and at least one audience rule.

2. From within the dropdown menu for each path, click Add Audience to configure audience rules to set the qualifying criteria contacts must meet to enter the path.

You can prioritize paths by dragging them up or down in the stack. This is also the order in which paths will appear in the Orchestration view from left to right. The topmost path will receive highest priority. Contacts who qualify for more than one path at the same time will be assigned the one that ranks highest.

Path audience rules

We configured two of our paths with an email action to send discount coupons when a contact's abandoned cart reaches the specified total value. The third path does not offer a coupon and will skip the message action altogether. You can add a new automation underneath the skipped action and give those contacts an alternative path forward.

Our path rules

20_coupon: for contacts with an abandoned cart valued at more than $99, offering a 20% off coupon
10_coupon: for contacts with an abandoned cart valued between $50 and $99, offering a 10% off coupon
No_coupon: for contacts with an abandoned cart valued at less than $50, offering no coupon

Here is a look at our 20_coupon path audience rule. The Cart audience rule lets us specify total cart value thresholds. All three paths use the same Purchases audience rule to exclude contacts who made a purchase within a set number of days (10 days in this case).

Skip an action

1. After configuring your fork settings, your paths will be mapped in the Orchestration view. From here, you can edit the Wait Until, Delay, Filter, and Action components for each path as needed. You can also set a delay directly above the fork component.

2. To skip an action, click the action component and choose Skip Action.

Skipped action component stats will report the number of contacts processed. These contacts can continue through a new automation inside the existing fork or after the end-of-fork merge node.

When a draft Orchestration is published, existing Podium insights will not be affected, unless the Orchestration contains an experiment or fork component, in which case, the republished version insights will be reset. Aggregate insights are unaffected.

Comments

0 comments

Please sign in to leave a comment.