Derived events are synthetic events generated by Blueshift when certain criteria are met. You can use a combination of customer metadata, transactions, browsing behavior, and catalog/content changes to specify the criteria to trigger such events. 

You can then use these derived events in event triggered campaigns or use them as filters to segment customers for segment triggered campaigns.


Derived events are a premium feature and are not included in the standard package. Contact your CSM to explore and implement any custom use cases and to set up derived events.

Use Cases

Here are some examples of use cases for derived events:

Catalog driven

To generate catalog driven events, you must first upload a catalog of items (e.g. products, content etc.) to Blueshift. Catalog driven events can also be used for eCommerce campaigns.

  • Price drop alert - Notify customers about a price drop for an item they have viewed but not purchased.
  • Back in stock notification - Notify customers that an out of stock item that they viewed within a preset time frame is now available.
  • Promotion for frequently viewed items - Send promotional material to customers who frequently visit particular items in a catalog.
  • New items in collection - Send promotional material to customers if there is a new item in a collection in which they have expressed interest.

Transaction data driven

To generate transaction driven events, you must first set up a transaction model in Blueshift.

  • Subscription renewal - Send subscription renewal messages to customers who have subscriptions that are expiring in the next X days.
  • Feedback reminder - Send feedback reminders to customers after a specific event if they haven't submitted a feedback in X days.



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



Please sign in to leave a comment.