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.
- 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.
- Specify a seed list.
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.
Please refer to our Event Triggered Campaign FAQ on how to avoid duplicate messages
- Welcome series for a new user
- Onboarding customers
- Abandoned browse/search/cart follow-up emails
- Post Purchase up sell/cross sell
- Add To Wishlist/Registry follow ups
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.
Subsequent trigger delays are based off the previous message and not when the event/user entered the segment.
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.
You can also add a trigger that performs an action instead of sending a message.
Note: You can add an action trigger under existing triggers. You cannot add an action trigger directly under a campaign.
Reach us on firstname.lastname@example.org to enable this feature for your account.
Our platform can do different things based on the action that you choose. Here are the options:
- Update the journey
You can add an Update Journey trigger that takes your customer to a specific point in your campaign based on the settings that you specify. For example, you can add a trigger that takes a campaign back to its first step if the customer interacts with the latest message.
You can add this trigger to skip certain campaign steps for your customer or to take the campaign back to a previous step for a customer if certain conditions are met.
When a campaign is rerouted to a specific point in the journey, it does not re-evaluate the filters/conditions in the parent node. The campaign just assumes that all the criteria have been met and the journey continues from that point onward, evaluating all subsequent criteria moving forward.
The maximum iterations field specifies the maximum number of times our platform can reroute a campaign to its previous step for a customer. This ensures that our platform does not get into an endless loop between steps and proceeds with the next steps of the campaign for your customers.
- Exit the journey
Similarly, you can add an Exit Journey trigger, that moves a customer out of the campaign journey based on the conditions you specify. For example, a customer exits the journey if the customer interacts with the latest message.
Once you create the campaign, copy its UUID. You can copy the UUID from the URL of the campaign on the Blueshift app. For example, if you open a campaign in the Blueshift app, its URL looks like
Once you get the campaign UUID, you can ask your developers to set up an API call from your site/app/service to the trigger a campaign endpoint to trigger the campaign when the triggering event occurs (for example, an add_to_cart event).
The link to the trigger a campaign endpoint's documentation provides options to create a sample payload and test it. If you look at its parameters, it requires the campaign UUID and the email of the customer for whom you want to run the campaign. If a triggering event occurs and your site/service/app calls this endpoint with the required parameters, our platform runs the campaign.