Branching using filters

By using filters in triggers, you can create different branches in your campaign. For example, during a promotional campaign, you might offer a certain discount to regular customers and a higher discount to premium customers.

For event triggered campaigns that are triggered by the API, you can use only a Liquid expression as the filter in the trigger.

To configure the triggers, simply click the journey component. On the Filter tab, specify the criteria to determine which customers qualify for the trigger.

The following filters are available for you to use in your triggers:

Filter	Campaign
Conditions	All campaigns
Engagement filters	All campaigns - 2nd level trigger onwards
Device Platform	All campaigns - In app and Push channels only
Conditions using Liquid expression	Event triggered by API endpoint. This is the only filter available for this type of campaign.

Condition based filters

Blueshift provides various condition based filters for you to use in the triggers. You can set the conditions as follows:

• Match All
• Match None
• Match Any

The following conditions are available for you to use in the filters.

Filter type	Description	Availability
Catalog Activity	Blueshift makes it easy to segment by customer interactions with various parts of your product or content catalog for up to last 6 months. In addition to the filters available in the Recent Activity tab, you can also filter based on catalog/content attributes. Please refer to Catalog Activity for more information on the setup. Note: SKU ID is the same as item ID or product ID in catalog.	Segment triggered campaigns Event triggered campaigns
Demographic	Blueshift expands your raw data to enable easy demographic segmentation. You can either directly pass demographic information into Blueshift or leverage Blueshift’s data expansion. You can filter based on Gender, Location, and timezone.	One time Recurring Segment triggered campaigns Event triggered campaigns
Interests	Filter based on interest alert topics.	Segment triggered campaigns Event triggered campaigns
Lifetime Activity	Blueshift automatically computes aggregate statistics on visits, purchases, revenue, referrals, message sends etc during an entire customer journey. You can create conditions related to these aggregates under "Lifetime Activity".	One time Recurring Segment triggered campaigns Event triggered campaigns
Messaging attributes	Filter customers based on their interactions with an earlier message. For example, if the customer was sent a message, if they opened it, if they clicked it and so on. This will allow you to create a different flow for customers who engaged with your message than those who did not. For email messages, you can further filter down to the specific link inside the email a customer clicked on. You could use clicks as proxies for customers’ interests and thus have a different flow for customers who are interested in a certain item (e.g. ice creams) than that for customers who are interested in another item (e.g. salads).	Segment triggered campaigns Event triggered campaigns
Predictive Scores	With Blueshift, you can not only segment by a customer’s past behavior, but also by various predictive scores. Blueshift’s predictive scores can help you find customers with a high or low likelihood of completing various actions in the conversion funnel and the user lifecycle.	One time Recurring Segment triggered campaigns Event triggered campaigns
Recent Activity	Build conditions based on customer behavior on your website and apps in the past 31 days. Data in this section gets populated from your event stream. The following features are available: Boolean conditions on behaviors Timeline filtering Filter by event attributes Frequency	Segment triggered campaigns Event triggered campaigns
Traffic Source	Blueshift stores the traffic source information on all your web traffic. With this, you can easily segment customers by the source of traffic.	One time Recurring Segment triggered campaigns Event triggered campaigns
Transactions	You can use the transactions feature to chain related events/activities and segment customers on different states across their journey. The transaction based segmentation empowers you to find users based on their transaction status. For instance, you could find all orders that were placed last week, but not shipped yet.	Segment triggered campaigns Event triggered campaigns
Triggering Event Attributes	You can filter based on the attributes of triggering events.	Event triggered campaigns
User Affinity	If your website or app has a large catalog of products or content, you will often find that customers have affinities towards different sections of the catalog. Blueshift computes customer affinities based on behavioral & transactional data and keeps the affinity scores updated in near real-time. Marketers can easily use affinity data in creating their segments.	One time Recurring Segment triggered campaigns Event triggered campaigns
User Attributes	You can segment by any of the CRM attributes that you pass into Blueshift through the Identify event, User API or by uploading Customer Attributes through the dashboard.	One time Recurring Segment triggered campaigns Event triggered campaigns

Engagement filters

Blueshift offers several engagement based filters for you to use. With these engagement filters, you can tailor your campaign based on customer actions. The filters are available only from the 2nd level trigger onwards.

The engagement actions that you can use are as follows:

User has viewed previous message.	User has viewed the message sent out via the preceding trigger in the same branch of the journey.
User has clicked on previous message.	User has clicked the message sent out via the preceding trigger in the same branch of the journey.
User has transacted since previous message.	User has purchased an item/product that can be attributed to this campaign in the time since a message was sent out via the preceding trigger in the same branch of the journey.
User has not viewed previous message.	User has not viewed the message sent out via the preceding trigger in the same branch of the journey.
User has not clicked on previous message.	User has not clicked the message sent out via the preceding trigger in the same branch of the journey.
User has not transacted since previous message.	User has not purchased an item/product that can be attributed to this campaign in the time since a message was sent out via the preceding trigger in the same branch of the journey.

Note: In the engagement actions, a previous message refers to the message sent out via the preceding trigger in the same branch of the journey.

Examples

Some examples where you might use the engagement filters:

• If a customer did not view an email that you sent to notify them about an upcoming sale, you might want to send them an SMS.
• A customer has not visited your site in the last month so you sent a message recommending some products. The customer viewed the messages but has still not visited the site. You might want to send a message offering a promotional discount.
• A customer has viewed a message that you sent, so you might not want to send another message immediately.

Device platform

If you are sending an in-app message or sending a push notification, you can specify that it be sent to Any Platform, iOS only, or Android only.

Liquid expressions

For event triggered campaigns that are triggered by the API, you can use only a Liquid expression as the filter in the trigger.

For example:

{% if user.extended_attributes.email_optout_all == true %} 
false 
{% elsif user.extended_attributes.email_optout_personalized_marketplace == true %} 
false 
{% else %} 
true 
{% endif %}