Summary / TL:DR: This article outlines the campaign setup for Exit Gauntlets in Blueshift.

Overview

Exit Gauntlets are used to attempt to capture customers who have not engaged (click, open) with a marketing email over a period of time. The goal is to send mailings to customers to encourage them to interact with an email before the Corporate Backstop cleans them from the list.

Segment Setup

Transaction Type	Lists
list_code	List Code
email_active	Equal to true
is_deleted	equal to false OR not equal to true
User Attribute: `last_click_at`	Timeframe to capture users. It’s recommended to not exceed 180 days due to the Corp. Backstop cleaning them after that time. Ex: From PAST 180 days to PAST 50 days
User Attribute: `historical_affiliate_last_click`	Use ONLY if the instance has been migrated less than 180 days from the time of setup. Timeframe to capture users. It’s recommended to not exceed 180 days due to the Corp. Backstop cleaning them after that time. Ex: From PAST 180 days to PAST 50 days

Campaign Setup

In the example below we have 3 Journeys that start on different days that the customer hasn’t clicked in the past 50, 60 or 70 days. If the customer has not clicked in the past 50 days, they will follow that Journey and receive the 50 day email. If the customer still hasn’t clicked after 10 days, they will receive the 60 day email, and so on and so forth. This pattern follows for the remaining triggers to the right, however the Journey will get shorter as the engagement timeframe gets closer to 180 days.

It is important to add both a 10 day delay and the list_last_click and historical_affiliate_last_click attributes to the triggers. Doing this ensures that the triggers are evaluated 10 days after the last trigger sent and that the customer hasn’t clicked in that timeframe.

Campaign Type	Segment Triggered
Decision Split	Use this to filter out the specific day start for each journey
Email Triggers w/ Filters	Use the `last_click_at` and `historical_affiliate_last_click` attributes to target specific days