...
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 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 days | is_deleted |
OR not equal to true |
...
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.
...
Campaign Type | Segment Triggered |
|---|---|
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
...
Full Campaign
...
...
| Tip |
|---|
Wrap upYou should now be able to create an Exit Gauntlet campaign in Blueshift. |
...