Iterable workflows allows you to create complex series of emails triggered by a user event with a simple drag and drop interface. This article demonstrates how to create two popular marketing automation campaigns: a welcome series and a shopping cart abandonment campaign.
Example: Welcome series
The welcome series is kicked off when a user signs up for your newsletter or service. Immediately after signup, the user receives a welcome email. Over the next couple of days, you send subsequent emails geared at getting the new user to complete a certain number of actions, thus pushing them down the funnel. In this example, the goal is to get the new user to fill out a profile and invite their friends to join.
You can test this workflow by either using the Send Test Trigger option,
which will trigger the workflow even if it's turned off. Another testing
option is to add a filter after the first node to only allow people with
email addresses from your company to go through the workflow. Then, turn on
the workflow and send a sample
signUp event or subscribe to the trigger list
using a company email address.
After verifying that the workflow works, remove the filter to allow all users to go through the workflow.
Example: Shopping cart abandonment
The shopping cart abandonment campaign starts when a person adds an item to
his/her cart. When you call the
API endpoint, it updates the user profile with the items in their shopping
cart, which you can use to customize the email to show the items in the cart.
If the purchase is not completed in a certain amount of time, you will send
the first reminder email. You can add additional steps if you'd like to send
more than one cart retrieval email. The following cart abandonment workflow
sends two email reminders
You should test this workflow by adding a filter after the first node to only
allow people with email addresses from your company to go through the
workflow. Then, turn on the workflow and send a sample
updateCart event for
a company email address.
After verifying that it works, remove the filter to allow all users to go through the workflow.