Transactions in segment based campaigns

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 also use content from the transaction record to include personalized campaign messages using Liquid.

Include transaction data in personalized messages sent in campaign

To include transactions data in personalized messages that you send using a segment based campaign, complete the following steps:

1. Add personalizations to the messages in your templates.
2. In your segment based campaign, ensure that you select the same transaction segment that you used to select the preview user in step 1.
3. In the relevant trigger of the campaign journey, select the messaging template from step 1.

Adding personalization to messages

To include transaction data for personalization in your template, complete the following steps:

1. On the Data tab of the template, select a preview user that belongs to the transaction segment for the required transaction record.

   The following example shows a messaging template with the search for users that belong to the transaction segment "Monthly Promotion". The "Monthly promotion" segment targets users who have booked their hotel stay in the past 6 months. 

   

2. The related transaction record for the selected user is displayed in the Preview Data.
3. Click Show Data to view the template data.

   In this example, when you select a preview user that belongs to the transaction segment "Monthly Promotion", the template data includes details of the related transaction record. 

   

4. Go to the user_transaction section. You can use this data to personalize your message content using Liquid.

   In this example, the transaction data includes the hotel booking details for the selected preview user.  For example, {{user_transaction.hotel_booking_id}} or {{user_transaction.hotel_brand}}.

   

Use transaction attributes as filter criteria

You can use transaction attributes as filter criteria in the triggers in your campaign.

• When you use a segment of transactions as the target audience for a campaign, you can use the attributes from the triggering transaction in the trigger filters.
• When you use a segment of users as the target audience for a campaign, you can use the transaction attributes from the user profile in the trigger filters.

To understand the difference between using triggering transactions and transaction attributes from the user profile, consider the following example of user A who has 2 orders in the past 30 days:

• Order 1: Item = Shirt (Apparel), Color = White, Revenue = $75
• Order 2: Item = Jacket (Apparel), Color = Gray, Revenue = $245

Example 1:

1. You create a segment of transactions to target users who have purchased "Apparel" in the past 6 months.
2. You use this segment of transactions in your segment based campiagn.
3. In your email trigger, you use the triggering transaction to select users who have purchased a gray shirt in the past 30 days - item_type=shirt AND item_color=gray

   User A did not purchase a gray shirt and so does not qualify for this trigger.

Example 2:

1. You create a segment based campaign for post purchase product recommendations.
2. In your email trigger, you use the transactions linked to the user profile to select users - item_type=shirt AND item_color=gray. 
3. Attributes of the transactions are considered separately as part of the user profile.

   User A qualifies because user A did purchase a shirt and user A did purchase an item with the color gray.

Send messages to user for each transaction record

When you use a segment of transactions as the target audience for a campaign, the transaction segment might return multiple transaction records for the same user. By default, Blueshift does not send multiple messages to the same user, even if the message is for a different transaction record. To bypass this default behavior and send multiple messages to a user, one for each transaction record, select the Skip duplicate messaging check setting in the Campaign Properties Messaging Preferences.