Segment Builder Updates
We have updated our segment builder such that it is really easy for you to build a transaction segment. All you need to do is select ‘transactions’ (instead of ‘users’) and specify the transaction model at the time of creating the segment. This will eliminate human errors from forgetting to target (star) a traction or accidentally un-starring a transaction in the segment editor. Moreover, the target of the segment will be displayed in the segment editor at all times so that you can easily identify which entity (user or transaction) the segment targets. Additionally, the target of the segment will also be displayed on the segment index screen so that you can quickly find the segment you are looking for.
Transaction Segment vs User Segment
When you create a segment in Blueshift, by default it is a segment of users. Such a segment has access to all the information on the user profile screen, including transactions, but does not have all the details of a specific transaction record that you are interested in (i.e. based on your segmentation criteria). Consider this example:
Let’s say you’ve created a transaction model called “orders” and let’s say a user, Gavin Belson, has 2 orders in the last 30 days:
- Order 1 on day (Now-25): Item type = shirt, item color = white, amount = $50
- Order 2 on day (Now – 7): item type = pants, item color = gray, amount = $200
Now, let’s say you want to message users who have purchased a gray shirt in the last 30 days i.e. you use the filter criteria: “item type = shirt AND item color = gray”
- If you use this criteria in a user segment, the user Gavin Belson would qualify for the message since they have transaction records in the past 30 days that meet both the specified criteria
- However, if you use this criteria in a transaction segment, then the user Gavin Belson would not qualify since this user does not have a single transaction record in the past 30 days that meet both the criteria