Transactions in event triggered campaigns

In an event triggered campaign, you add triggers that send messages to customers when the conditions for the trigger are met. When the triggering event is a state of a transaction model, you can include transaction data in the messages sent by the campaign. You can also use attributes from the transaction record as delay criteria or filter criteria for the campaign.

Include transaction data in personalized messages sent in campaign

You can include information from related events in personalized messages that you send using an event triggered campaign. For example, when a message is sent after a user checks out of a hotel, you can include booking or payment details which are included in the booking_confirmation event but are not available in the check_out event (i.e. the event triggering for your campaign).

Note: The related events must be part of a transaction model.

To include transaction data in event triggered campaigns, complete the following steps:

1. Add personalizations to the messages in your templates.
2. In your event triggered campaign, ensure that you select the same event that you used as the Sample Event when adding personalizations in step 1.
3. In the relevant trigger of the campaign journey, select the messaging template from step 1.

Adding personalization to messages

You can include transaction data for personalization in Email, Push, and SMS messaging templates.

Note: Before you can include personalization in the messages, you must have at least one transaction record for the transaction model. You can send a few test events to create a sample record.

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

1. Go to the Data tab > Preview Data section of the template.
2. For the Sample Event, select the event that is the triggering event for the campaign.

   

3. Select a preview user who has an event that is linked to the transaction record. You can select the same user as in the selected event record to ensure that the selected user has an event linked to the transaction record.

   

4. Event transactions for this preview user are displayed in the Preview Data section below the selected Sample Event.

   

5. Click Show Data to view the template data.
6. Go to the event_transaction section. You can use this data to personalize your message content using Liquid.

   

   For example, {{event_transaction.hotel_booking.hotel_name}}

   Note: If the transaction model has a space in the name, for example “Hotel Booking”, then you must use the following syntax: {{event_transaction.[“Hotel Booking”].hotel_name}}

Use transaction event attributes as delay criteria

When the triggering event is a state of a transaction model, you can use attributes from the transaction record (attributes from all the events tied to the transaction record) as delay criteria for the campaign.

For example, consider a Hotel booking transaction model. When you send a message for the check in state (event), you can use a template designed for a particular hotel brand by using the hotel brand information that is part of the booked state (event).

Example:

Consider the following example of a campaign that uses a transaction model (Hotel Booking) for a hotel booking:

Transaction model: Hotel Booking

Transaction states (events): booked, checkin, checkout, cancel

Event attributes for booked: booked_status, checkin_date, checkout_date, hotel_brand, room_type, payment

1. The campaign is triggered when a customer books a hotel room. (Transaction = Hotel Booking, event = booked, attribute = booked_status).
2. A confirmation email is sent to the customer. The email template is personalised for the user and the hotel brand. (Transaction = Hotel Booking, event = booked, attribute = hotel_brand)
3. A reminder SMS is sent to the customer 2 days before the check in date using a transaction attribute based delay. (Transaction = Hotel Booking, event = booked, attribute = checkin_date)
4. After check in, a welcome email is sent to the customer with information about wifi passwords, dining hours, and other hotel facilities. The checkin event triggers this email, but information within the email is based on the room_type information passed in the booked event. For example, if the room_type is one that includes wifi, then a wifi password is included in the email. (Transaction = Hotel Booking, event = checkin, attribute = room_type (from booked event))
5. After check out, the customer is sent a thank you message and a billing summary. (Transaction = Hotel Booking, event = checkout)
6. Two days after the customer checks out, an email is sent asking for feedback using an attribute based delay. (Transaction = Hotel Booking, event = checkout, attribute = checkout_timestamp)

Use transaction event attributes as filter criteria

When the triggering event is a state of a transaction model, you can use attributes from the transaction record (attributes from all the events tied to the transaction record) as filter criteria for the campaign.

In this example, the campaign is triggered when a customer checks out of the hotel (Transaction = Hotel Booking, event = checkout).

1. In the filter criteria select an event attribute as the Transaction ID.
   For example, for the transaction Hotel Booking select Transaction ID as the identifier and select the booking_id attribute.
2. The transaction record that contains this event attribute is now available for use as the filter criteria.
   For example, for the transaction Hotel Booking, the record that contains the booking_id attribute is now available.
3. Use transaction attributes from this transaction record in the filter criteria.
   For example, the record that contains the booking_id attribute also contains the hotel_name. You can filter and select users who have booked a hotel room at the hotel Caesar's Palace.