How can we help?

Set priority across multiple Podium Orchestrations

Overview

You can use delay times with trigger events to set priority in your Podium Orchestrations. This can be useful when interacting with customers at different points in the conversion funnel.

Trigger and delay states

Automation: BrowseAbandon

  • If browse, restart timer: Assuming the user's session is still active, continue to delay a re-engagement message until the session has ended.
  • If add_to_cart, cancel: Assume the user has qualified for a higher priority event trigger.
  • If order, cancel: Assume the user has completed the goal of all automated/triggered campaigns and converted. 

Automation: CartAbandon

  • If order, cancel: Assume the user has completed the goal of all automated/triggered campaigns and converted. 

Set delay times according to priority

The main idea in this strategy is that lower priority campaigns have longer delay times, with each new browse and cart event resetting the timer (keeping the session active). Actions of higher importance disqualify the customer from lower priority automations. You can then layer in message tags for suppression across multiple campaigns.

Customer journey

As an example of implementing this strategy, we'll use the following event sequence.

1. A customer completes browse.

2. This qualifies them forBrowseAbandon because browse is the trigger for that message. The user is now in the delay state of the BrowseAbandon campaign.

3. During the delay timer of BrowseAbandon, the same customer completes addtocart event.

4. This even now qualifies the customer for CartAbandon since it's the trigger of that event-triggered message, also disqualifying them from BrowseAbandon because it's set to the delay-cancel action of BrowseAbandon.

Priority strategy

Here's an example priority strategy for the customer journey above.

CartAbandon, being higher in the conversion funnel, has the shortest delay.

P1 - Cart Abandon
Trigger Event: cart
Delay Reset: cart, browse, search
Delay Cancel: order
Trigger Delay: 2 hours
Sending Cadence
How Many Touch Points Total Duration: 7 days (abandon_1 suppress for 7 days)

P2 - Browse Abandon
Trigger Event: browse
Delay Reset: browse, search
Delay Cancel: order, cart
Trigger Delay: 3 hours
Sending Cadence
How Many Touch Points Total Duration: 7 days (abandon_1 suppress for 7 days)

P3 - Search Abandon
Trigger Event: search
Delay Reset: search
Delay Cancel: order, cart, browse
Trigger Delay: 4 hours
Sending Cadence
How Many Touch Points Total Duration: 7 days (abandon_1 suppress for 7 days)

For assistance with implementing this strategy, contact your CSM. 

Comments

0 comments

Please sign in to leave a comment.