Summary / TL:DR: This article outlines the recommended campaign setup for Exit Gauntlets in Blueshift.
...
Segment Setup
Transaction Type | Lists | ||
|---|---|---|---|
list_code | List Code | ||
email_active | Equal to true | ||
is_deleted |
OR
| ||
User Attribute: | Timeframe to capture users.
Ex: From PAST 180 days to PAST 50 30 days | ||
User Attribute: | Use ONLY if the instance has been migrated less than 180 days from the time of setup. Timeframe to capture users.
Ex: From PAST 180 days to PAST 50 30 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 30, 45 or 46 days. If the customer has not clicked in the past 30 days, they will follow that Journey and receive the 30 day email. If the customer still hasn’t clicked after 10 days, they will receive the 45 day email, and so on and so forth. If the customer does not qualify for the first trigger (30 day), Blueshift will move them to the next trigger to the left (in this case, 45 day). Let’s say the customer qualifies for that trigger, they would receive that trigger and then, if they haven’t clicked in 1 day, they would be merged to the trigger in the first journey for the 46 day email.
| Note |
|---|
It is important to add both a 10 day delay and the |
| Info |
|---|
Click Here to learn more about Campaign Flow Controls in Blueshift. |
Campaign Type | Segment Triggered |
|---|---|
Journey Re-qualification | Re-qualify users after 1 day |
Decision Split | Use this to filter out the specific day start for each journey |
Email Triggers w/ Filters | Use the |
Decision Split Criteria
...
Trigger Filter Criteria and Merge Journey Trigger
...
Full Campaign
...
...
| Tip |
|---|
Wrap upYou should now be able to create an Exit Gauntlet campaign in Blueshift. |
...