What to Expect From this Use Case

The Birthday Reminder Banner use case helps you collect the birthdays of one or two friends via a banner. Once their birthdays are approaching, you’ll receive an email reminder, ensuring you never miss congratulating them. This automated solution keeps you informed and prepared to celebrate your friends' special days.

💡

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:

• Birthday reminder banner
• Birthday reminder email
• Evaluation dashboard

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 birthday reminder use case includes a banner where customers can enter the names and email addresses of up to two friends and select one of five product categories suitable for their gifts. An email reminder is sent to the customer two weeks before each friend's birthday and again on the birthday day.

Only customers with a valid email address and who have given email consent are targeted with the banner.

Banner

The banner includes Name, Birthday, and Choose a gift category for your friend input fields for your first and second friends.

You can define up to five different gift categories. If you want to define fewer categories, leave the rest blank; they will not show when the campaign is live. For example, if you want to give the customer two options, for Option 1, insert Toys, Option 2, Games, and leave Option 3, 4, and 5 blank. The minimum is to insert one option to run the use case.

Your customer must fill in details for at least one customer to Submit the banner.

Email

First flow

The first flow saves the data from the Birthday Reminder Banner into customer properties so they can be used in email communication.

Second flow

The second flow is triggered daily and consists of five pairs of branches representing the five gift categories defined in the banner.

To comply with GDPR rules, we verify that the customer has given newsletter consent after the Repeat daily trigger node. Each category is then divided into checks for friend_1's and friend_2's birthdays.

An email reminder is sent 14 days before the birthday, personalized with condition rows for either friend_1 or friend_2 and featuring a recommendation engine corresponding to the chosen gift category. Do not remove the condition rows for the use case to function correctly.

Another email is sent on the exact birthday, replicating the personalization and recommendation logic from the first email.

👍

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.

Banner

3.1 Banner Settings

The banner is shown only to customers with consent. And to customers who have seen more than five products in the last seven days and have not filled in the banner previously.

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

3.2 Design & Copy

Customize the banner visuals and copy to align with your company's brand identity. See banner tooltips ℹ️ in case of uncertainty.

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

Email

3.3 Email Settings

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

3.4 Design & Copy

Open the email node to adjust the email design and settings.

Friend's birthday email - 2 weeks before

The content for either friend_1 or friend_2 is personalized using row display condition. For this use case to function, the condition rows must be kept in the email design for friend_1 and friend_2. These rows are dynamic; only the corresponding row will be displayed to the recipient.

If both friends have birthdays on the same day, both rows will be displayed to the recipient.

Make sure the correct row conditions are chosen and check the recommendation block.

Friend's birthday email - today

As in the previous email, ensure the correct row conditions are chosen and check the recommendation block.

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

3.5 Recommendation engine

Open the email node to adjust the recommendation engine.

Make sure that the correct recommendation engine is chosen for both emails. Click on the Recommendations HTML block > CONFIGURE BLOCK and check the Recommendation ID. There is a corresponding engine for each category branch. For example, for Category 1, there is Most bought products from category 1 ... engine.

These engines consist of most bought products in the specific category in last 30 days.

3.6 Segmentation

If you decide to change the gift categories, open segmentations for both friends and adjust the customer filter for each category. For example, currently category 1 equals Toys - if you decide to change this insert category of your choice into the segments.

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 banner and the email, click Start to launch the campaign.

Step 5: Evaluate the Results

Remember to run the use case for a few days to see the impact.

After this initial period, use the prebuilt and ready-to-use evaluation dashboard specifically included in this use case to measure and analyze relevant data.

To evaluate, open the evaluation dashboard and set the attribution window for revenue in hours (e.g. 24) and click the Refresh button in the upper right corner to see the results.

If you encounter any problems, read this article for insights on evaluating your campaign.

💡

Tip

Don’t forget to regularly check campaign results so you can optimize the use case for better performance.

Additional Resources

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