Setting up a MultiPass for Automated Campaigns

Learn how to easily build a MultiPass option directly into your automated campaigns in Listrak Conductor.

Support avatar
Written by Support
Updated over a week ago

The MultiPass, which allows you to send an additional message to non-openers, can be used in many different ways to create effective marketing strategies. You can use this tactic in any type of automated campaign, such as Post Purchase, Shopping Cart Abandonment, Browse Abandonment, and more. Below, we'll walk through the steps to add MultiPass threads to a Post Purchase "Thank You" campaign.

Openers vs Non Openers

For this example, a MultiPass thread will be added to a Post Purchase "Thank You" campaign. Using this strategy, you can send an additional message only to non-openers because we're saying "thank you," and really don't need to get that message across more than once. Follow these steps to set up the MultiPass in Listrak Conductor.

  1. Navigate to Authoring > Conductor Conversations

  2. Select the conversation you'd like to add a MultiPass to by clicking on the name. 

  3. In the Listrak Conductor conversation ensure you're using the working version by selecting if from the drop-down menu.

  4. Click the Add Child Thread (plus sign) icon underneath the Wait Step after the message a contact should open.

  5. . Click the Trigger Step in the new thread.

  6. Override the default name to to a relevant name.

  7. Click the tab that says Message from the Available Events list.

    💡 Message events are more general actions while link events can target contacts who engage with a specific link.

  8. Select Message Opened from the Available Events list.

  9. Click Update.

Now, if a customer opens Thank You 1, they'll be sent down to the new thread. You can add additional steps to this thread or if no steps are added they will be terminated from the conversation.

In this example, contacts are exited from the conversation if they have opened message 1 in the two days before message 2 is sent or if they opened message 2 in the two days before message 3 is sent. They are exited because no additional steps are included in the child thread.

Skipping Wait Steps

Depending on the type of campaign you're sending, you might want to allow your customers to skip the wait time in between your message series. This is particularly effective for educational or instructional message series.

Let's say you're a company that sells kitchen and baking products and you're promoting a famous chef's tips through an automated message series. Each message contains a recipe with insider tips from your celebrity chef. Susie is a big fan of your products and the chef. She's also a stay-at-home mom. She loved the first message and wants to know more. Give her the option to receive Message 2 instantly by adding a "Receive Next Tip Now!" link in your email. Contacts are routed down a child thread as soon as they complete the specified action.

  1. In the Listrak Conductor conversation ensure you're using the working version by selecting if from the drop-down menu.

  2. In this example, the conversation contains three messages. Messages one and two contain links that say "Receive Next Tip Now!" Click the Add Child Thread (plus sign) icon underneath the first Wait Step.

  3. Click the Trigger Step in the new thread.

    1. Override the default name to something relevant.

    2. Click the tab that says Link from the Available Events list.

    3. Select the link a contact should click on to be eligible to receive the child thread.

      💡 Text links will be available if you have added links to the plain text while HTML links reflect links in a Composer or HTML message.

    4. Click Update

  4. Add a Goto Step after the Trigger Step.

    1. Override the default name if desired.

    2. Select the next message as the target destination.

    3. You do not need to update the segment filter as all contacts should go to message 2.

    4. Click Update

  5. You can include child threads after additional messages, if desired.

Did this answer your question?