Event Triggered

Event Triggered campaigns are based on a specific event (e.g., sign_up, purchase, etc.) and it triggers a series of messages that are spread out over time (days, weeks, etc.). You can also choose to trigger these campaigns with our API instead of specifying an event.

Screen_Shot_2018-02-28_at_4.05.22_PM.png   Screen_Shot_2018-02-28_at_4.06.16_PM.png


Campaign Settings

Trigger Settings 

  • Journey limits to control the number of times users experience an event-triggered campaign (once in their lifetime, once at any time, multiple times concurrently)
  • Create multi-step, multi-channel journeys with complex conditional filters (messaging attributes, recent activity, event specific attributes, user attributes)
  • Set delays (minutes, day, hour, week) based on event, event properties and/or previous triggers
  • Send emails with attachments (Blueshift & Sendgrid only)

Global Campaign Filters

  • Global campaign filters are applied to every trigger within the campaign
  • These filters appear on the campaign itself and can be based on the triggering event or information directly tied to users.
  • They can't be applied if the campaign is triggered when the api endpoint is called.



Avoiding Duplicate Messages

Please refer to our Event Triggered Campaign FAQ on how to avoid duplicate messages


Example event-triggered campaigns:


Welcome series

A welcome series allows you to introduce your brand to your subscribers. It creates trust and helps you establish a relationship with your customer.

Here's an example of a multi-channel, multi-series welcome email that uses our advanced filtering and branching capabilities.




Step 1: Identify the event that would trigger the campaign. Also, since there will only be one email from this campaign, use the "Once in their lifetime" journey control. You will also want to ignore the user messaging limit for this campaign.


Step 2: Create multi-channel journeys

Using Blueshift's branching and event filter capabilities, we can reach users based on their registration source. So in this example, email users who signed up from web, but send a push notification for mobile app sign ups.



You can also send a follow-up to users if they have not made a purchase 7 days after they first signed_up.

**Trigger Delays

Subsequent trigger delays are based off the previous message and not when the event/user entered the segment.




Abandon Cart

A cart abandonment occurs when a user/visitor adds item(s) to their cart, but does not follow through on the purchase. The overall intent here is to bring them back to your site to finish the purchase.



If you would like to control the number of abandon carts per day, you can honor the messaging limits and/or set this up as a segment triggered campaign



Step 1: Select the Add_to_cart event to trigger the campaign. For the Journey limit, you can choose to use Once at Anytime or Multiple Times Concurrently. You may also want to ignore the user messaging limit for this campaign. 


Step 2: Create the first trigger in the abandon cart flow. In this scenario, we are targeting users who added an item to the cart but haven't made a purchase in the past two hours. Additionally, we are testing two sets of email templates for this initial trigger.


Step 3: Create additional triggers in the abandon cart flow. For this example, we are splitting the audience into two groups based on their interaction and purchase activity.


Was this article helpful?
2 out of 2 found this helpful