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

To configure the triggers, simply click the journey component. On the Filter tab, specify the criteria to determine which users 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.

Conditions 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

jb_triggerfilter_matchcondition.png

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

jb_triggerfilter_condition.png

Filter type Description Availability
Catalog Activity Blueshift makes it easy to segment by user 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.
  • 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 Segmenting users by their responsiveness to messages (push notifications, emails, SMS) helps marketers adjust the volume of messaging. More engaged users could be sent more marketing communications.
  • Segment triggered campaigns
  • Event triggered campaigns
Predictive Scores With Blueshift, you can not only segment by a user’s past behavior, but also by various predictive scores. Blueshift’s predictive scores can help you find users 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 user 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 users 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 users 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 users have affinities towards different sections of the catalog. Blueshift computes user 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 user actions. The filters are available only from the 2nd level trigger onwards.

Some examples where you might use the engagement filters:

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

The engagement actions that you can use are as follows:

  • User has viewed previous message.
  • User has clicked on previous message.
  • User has transacted since previous message.
  • User has not viewed previous message.
  • User has not clicked on previous message.
  • User has not transacted since previous message.

jb_triggerfilter_liquid.png

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.

jb_triggerfilter_platformtype.png

Liquid expression

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

jb_triggerfilter_liquid.png

 

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

Comments

0 comments

Please sign in to leave a comment.