Derived Events

Blueshift has the ability to auto-generate and trigger smart notifications (email or push). Our platform can use a combination of user metadata, transactions, browsing behavior and catalog/content changes to trigger these notifications.

Use Cases

You can customize any transaction/catalog behavior or event behavior based computation and use that to trigger a personalized message. Below are a few examples. Please contact your CSM or reach out to support@blueshift.com  to explore these and other custom use cases.

1 - Price Drop (catalog driven)

  • When: The price of item changes within X days (we recommend at least 7 days).
  • Who to target: All users who have viewed but have not purchased (can also base it off other events).
  • Data needed: Product catalog with price information.
Price Drop

 

2 - Back In Stock (catalog driven)

  • When: The product they viewed in the last 7 days in is back in stock.
  • Who to target: All users who have viewed an out of stock item.
  • Data needed: Product catalog with availability (in stock or out of stock) or dates (start and end).

 

Back In Stock

3 - Subscription Expiration (transactions)

You can send subscription renewal messages to users who have subscriptions which are expiring in the next X days. You can use the transaction data to create a segment to target users who's subscriptions are expiring in next X days. Blueshift can generate a derived event (re-play) and  the relevant subscription (transaction) data.  You can then use the derived event to setup an Event Triggered campaign.

4 - Customer feedback (transactions)

You can send feedback reminder emails to users who have checked out and haven't submitted a feedback in X days. You can use the transaction data to create a segment to target users who have checked out, but haven't submitted any feedback. Blueshift can generate a derived event (replay) based on the transaction data,  which can then be used in an Event Triggered campaign.

5 - Frequent visit (catalog driven)

You can send promotional material to customers who frequently visit items in a catalog. For example, if you run a furniture store and a customer frequently visits tables on your site, Blueshift can generate the 'frequent visit' derived event for the product. You can use this event to run event triggered campaigns and send promotional material to your customers. 

  • When: The product that they viewed frequently (more than a specified number of times) in the last specified number of days. You can specify the number of times a customer visits a product. In addition, you can specify the number of days in which a customer visits a product.  
  • Who to target:  All users who have frequently viewed a product.
  • Data needed: Events that a user activity generates. 

6 - New in collection (catalog driven)

You can send promotional material to customers if there is a new product in the collection in which they have expressed interest. For example, you run a furniture store and you have a collection called office supplies that includes products like chair, table, and lamp. When you introduce a new product in the collection, for example a foot-rest, Blueshift can generate the 'new in collection' derived event. You can use this event to run event triggered campaigns and send promotional material to your customers. 

  • When: A customer engaged with products from a collection in the last specified number of days, and there are new products in the collection.  You can specify customer engagement. For example, a customer engagement can be a product view, add to cart, lead, or purchase. 
  • Who to target: Customers who engaged with a product in the last specified number of days and the collection has new products.
  • Data needed: Product catalog with collections defined properly. 

 

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