Use Case maturity:

Basic

What to expect:

Increase in AOV

Use Case goal:

Performance

What to Expect From This Use Case

The Interactive Pre-Travel Engagement use case ensures customers receive a series of informative emails at 60, 30, 14, 7, and 1 day before departure. These emails offer essential pre-travel information and opportunities to enhance their experience through service upgrades. The scenario activates upon booking completion, evaluating the days until departure to determine the email sequence starting point. Before each email, the system checks for booking updates and valid customer consent and ensures no duplicate emails for the same booking.

💡

Tip

Visit our microsite to read more about this and other use cases developed by a team of Bloomreach experts.

Use Case Items

With this use case, you’ll get a:

• Pre-Travel Engagement email scenario

How to deploy the Use Case

After downloading the use case, follow these steps:

Step 1: Meet the Requirements

Verify if the data in your project meets the requirements. Follow this step-by-step setup guide in case of problems.

Step 2: Understand the Use Case Logic

The scenario activates upon the completion of a booking. Customers are then evaluated based on the days until their departure to determine their starting point in the email sequence. For example, a customer who books 21 days before departure will enter the sequence with the '30-day' email. The communication flow initiates no more than 60 days before departure.

Before sending each email, we ensure:

• The 'booking has not been updated' prevents a booking from continuing the sequence if a newer booking has been tracked (e.g., booking change) and generates multiple messages. This also stops any canceled bookings from moving further.
• The customer's consent is confirmed to be valid.
• The customer has not previously received the same email for the current booking, which could occur, for instance, in cases of booking upgrades. To manage this, custom campaign tracking is set up to track each event's booking ID.
  • Details on the setup of custom campaign tracking can be found in the documentation. For this scenario, the attribute name should be 'booking_id,' with the attribute value set as {{ event.booking_id }}. This configuration is included in all email templates within this scenario.

Please refer to the scenario descriptions for step-by-step information on use case deployment.

👍

Information

The logic of this use case is built on best practices and only requires adjustments if you want to further customize the use case. Get instant value by launching this campaign in just a few clicks.

However, we highly recommend you adjust the use case design and copy to fit your business needs.

Step 3: Adjust the Use Case

Now that you understand the use case logic, you can set up the use case according to your preference.

3.1 Email Settings

If you decide to customize the email settings, follow this detailed guide to make the adjustments.

3.2 Design & Copy

Customize the email visuals and copy to align with your company's brand identity.

Otherwise, you can go through this guide for more information.

Follow this guide to adjust the email template with products in the email node.

Step 4: Test and Run the Use Case

When you are done adjusting the use case, we recommend to always test the use case before deployment. When testing, double-check if the use case design, copy, and settings work as preferred.

❗️

Warning

You should only deploy a use case after testing. Testing prevents sending unfinished or imperfect campaigns to your customer base.

Run the use case once the testing is over. When you open the email, click the Start button in the upper right corner to launch the campaign.

Additional Resources

Learn how to enhance and optimize email performance with different tips and tricks from Bloomreach experts.