Transaction based segments

Transaction Modeling is an advanced Blueshift capability that allows you to connect and segment lifecycle events/behaviors through a common identifier. Certain transactions, like hotel bookings, have multiple events associated with the transaction. Blueshift’s Transactions capability allows you to link these related events by using a common identifier.

After you group related events into a single transaction record, you can use the content from the transaction record in a message to your customers. You can also update the user journey based on information in the transaction record. In order to do this, you must first set up a transaction segment.

You can create different types of transaction based segments:

• A segment of transactions: you can access the details for a specific transaction record in addition to the details for a user profile.
• A segment of users with transaction criteria: you can access all the transactions linked to the user profile. However, you cannot access the details for a specific transaction record.
• A transaction mixin segment: Transaction mixins are advanced reference segments that are limited to using only transaction criteria.

View transaction based segments

For all transaction based segments, the target of the transaction is displayed on the segment index screen so that you can quickly search for and find the segment that you are looking for.

Comparison between a segment of users and a segment of transactions

Consider user A who has 2 orders in the past 30 days:

• Order 1: Item = Jeans (Apparel), Revenue = $75
• Order 2: Item = Purse, Revenue = $245

When you create a segment of transactions to target users who have purchased "Apparel" and for whom the revenue is greater than or equal to 100, User A does not qualify because a segment of transactions considers the transaction in its entirety. User A did not purchase any apparel of value greater than $100.

When you create a segment of users with Transactions criteria to target users who have purchased "Apparel" and for whom the revenue is greater than or equal to 100, User A qualifies because the attributes of the transactions are considered separately as part of the user profile. User A did purchase apparel and User A also purchased an item of value greater than $100.