World is now on Opti ID! Learn more

David Buö
Apr 24, 2019
  34
(0 votes)

Get started with Abandoned Basket e-mails

Abandoned basket e-mails is a widely used concept within commerce and builds on the concept that visitors use their basket as a "reminder". A lot of visitors put products in their basket since they're not ready for the purchase, they want to do more research, they don't have time to do the checkout, information is missing etc. As a commerce website, we can utilize this opportunity of a visitor showing a high interest for a product (by adding it to the basket) to generate more sales.

In the following post, I will show you hands-on how you set-up an abandoned basket scenario with Episerver Personalization and Episerver Campaign.

Before we start digging into the details, let's have a look at the steps we need to do (i assume that Episerver Personalization tracking is already implemented on the website):

  1. Request a new recipient list
  2. Create an abandoned basket campaign in the Personalization Portal
  3. Create and abandoned basket e-mail
  4. Set-up the abandoned basket trigger

1. Request a new recipient list

The starting point of any e-mail within Episerver Campaign is a recipient list, for your trigger scenarios I would recommend you to request a new recipient list that is designed to support the integration between Episerver Personalization and Episerver Campaign (we support a lot of other ESPs as well). You do this by simply send an e-mail to support@episerver.com.

2. Create an abandoned basket campaign in the Personalization Portal.

In the personalization portal, navigate to Mail > New Campaign (picture below). The first step allows you to configure the style of the recommendation, Episervers web help has the whole step explained here.

After giving your new Mail Campaign a new and a stylistic touch we move on to the actual configuration of the e-mail strategies we want to apply. This is described in detail in our web help here. Since Episerver utilizes the same process for designing a various amount of e-mail scenarios we must define what strategies we want to apply to our campaign. In this scenario, we're designing an abandoned basket scenario so I will select an abandoned basket as the first strategy.

The strategies are explained here and abandoned basket scenarios are described as "Shows products that were added to the basket but not purchased. Only baskets abandoned within the last 90 days and products currently available are considered." Since there might be scenarios were a visitor already has purchased the product that was abandoned I want to apply other strategies as well, strategy 2 and 3 will be injected if the abandoned basket scenario doesn't apply. If you don't want to decide what strategy to use if the abandoned basket strategy doesn't apply, you can use "top-ups" that will go back to the default algorithm and make sure that the widget doesn't get empty when opening the e-mail.

For the final step, we need to define our ESP and our E-mail field function ({Email}) that is used for that ESP. The field function is the parameter that gets passed back to the recommendations engine in order to serve recommendations, so it's important that you make sure to get this correct. Click "Generate code" and save the codes in an empty document or similar.

 

You can now save the Campaign.

3. Create and abandoned basket e-mail

Now it's time to create the actual e-mail that will be sent when someone abandoned a cart. To do that I will create a transactional e-mail in Episerver Campaign, and configure a recommendations block that will render the e-mail recommendations (the abandoned products).

Go to Transactional E-mail and Create a new transactional E-mail. Select your recipient list (as requested in step 1) and give your Abandoned Basket E-mail a name. 

Create a recommendations block and copy/paste the links from the Generated code in step 2 for each widget you have configured in the Personalization Mail Campaign (my scenario has 2).

When you're finished with your copy/paste exercise, hit apply and your recommendations block should look something like the picture below.

You can test how this e-mail will look by clicking "Test Message" and enter your e-mail address. When you have added some more content to give the e-mail a nice look click "Close" and then "Save and close". Back at the Transactional email dashboard, select your Abandoned basket e-mail and click "Start".

Now we have created recommendations (abandoned basket scenario) and also an e-mail that will render the abandoned products. The final step is to configure the actual trigger.

4. Set-up the abandoned basket trigger

Navigate back to the Personalization portal and go to Triggers and New Campaign 

The first time you configure a trigger you need to set-up an ESP connection. The configuration varies depending on your ESP, for Episerver Campaign you need to get your "recipient list authorization code" for the Recipient List that was requested in Step 1 (guide here). Give the connection a name, enter the recipient list authorization code and click "Test Connection". After the test is sucessful, save the ESP connection.

We also need to set up the ESP action. As for the action type, there are three different types for Episerver Campaign: send a message, add a user to a target group and remove a user from a target group. For abandoned basket e-mails, select send a message and paste the ID of abandoned basket e-mail you just created. 

Go to Episerver Campaign > Transactional mails to get the ID of your Abandoned Basket e-mail.

To test your ESP action you must first add your e-mail to the recipient list. This is because Episerver Campaign will only send e-mails to customers that have opted in for marketing information, therefore we must add all the recipients that have opted in into Episerver Campaign. After you've added your e-mail, enter it in the empty field and click Test ESP action. You should now receive an e-mail (which indicated that the action is working). If you don't get the e-mail, something is wrong.

With both the ESP connection and ESP action setup we can now configure the trigger, as you can see you can configure a lot more scenarios than Abandoned Basket. With your scenario configured, hit save and don't forget to activate the trigger by hitting "play" in the trigger campaign overview.

Let's try it out!

I'll navigate to my demo site, register an account with the same e-mail as I added in Episerver Campaign before (remember, this would be an import/integration in a production scenario). Add two products to the basket and then close my session.

After 180 minutes (according to configuration) I get my abandoned basket e-mail!

I hope you found this hands-on blog interesting and that it helps you generate more sales on your commerce website!

Apr 24, 2019

Comments

Please login to comment.
Latest blogs
Make Global Assets Site- and Language-Aware at Indexing Time

I had a support case the other day with a question around search on global assets on a multisite. This is the result of that investigation. This co...

dada | Jun 26, 2025

The remote server returned an error: (400) Bad Request – when configuring Azure Storage for an older Optimizely CMS site

How to fix a strange issue that occurred when I moved editor-uploaded files for some old Optimizely CMS 11 solutions to Azure Storage.

Tomas Hensrud Gulla | Jun 26, 2025 |

Enable Opal AI for your Optimizely products

Learn how to enable Opal AI, and meet your infinite workforce.

Tomas Hensrud Gulla | Jun 25, 2025 |

Deploying to Optimizely Frontend Hosting: A Practical Guide

Optimizely Frontend Hosting is a cloud-based solution for deploying headless frontend applications - currently supporting only Next.js projects. It...

Szymon Uryga | Jun 25, 2025

World on Opti ID

We're excited to announce that world.optimizely.com is now integrated with Opti ID! What does this mean for you? New Users:  You can now log in wit...

Patrick Lam | Jun 22, 2025

Avoid Scandinavian Letters in File Names in Optimizely CMS

Discover how Scandinavian letters in file names can break media in Optimizely CMS—and learn a simple code fix to automatically sanitize uploads for...

Henning Sjørbotten | Jun 19, 2025 |