Abandoned Cart Upgrade

Learn how your Abandoned Cart workflow was upgraded to a new Abandoned Cart and Abandoned Checkout

Ira avatar
Written by Ira
Updated over a week ago

This user guide provides information about the Abandoned Cart and Abandoned Checkout workflows, their migration process, and the improvements made to enhance your experience. Please read on to understand the changes and how they affect your message sending and reporting.

The changes described in this guide have been applicable since July 2023.

Contents

Migration of Old Abandoned Cart Workflow

If you had an older version of the Abandoned Cart workflow, it has now been split into two new workflows - Abandoned Cart and Abandoned Checkout. This migration has taken place on the improved integrations of Shopify, BigCommerce, and WooCommerce.

No action is needed from your end. Your messages will continue to be sent as before, ensuring a seamless transition.

Benefits

The new integration provides better results compared to the legacy Abandoned Cart workflow.

You will now have access to more data, additional filtering and splitting options, and the ability to customize the workflows based on where customers are in their customer journey.

This includes distinguishing between those who have already started the checkout process and those who haven't.

Understanding the Workflows

Reporting

Your old Abandoned Cart workflow is now disabled and operates in report-only mode, preserving all its data. You can still access all the statistics and reports associated with the workflow. Two new workflows, Abandoned Cart and Abandoned Checkout, have been created with the content from your old Abandoned Cart.

Workflow Logic

The logic behind the old Abandoned Cart workflow is the same as for the new workflows. However, the enhanced integration ensures that a maximum number of cart abandonment events are captured from your ecommerce platform. As a result, you may see more contacts entering the workflows.

Keep in mind if you wish to compare the statistics of your old Abandoned Cart workflow with the new workflows, you will need to combine the numbers from the Abandoned Cart and Abandoned Checkout workflows.

Message Sending

Your message setup has been preserved, and your messages will continue to be sent without interruption.

Contacts who abandon their carts will be directed to either the new Abandoned Cart or Abandoned Checkout workflows, depending on their position in the customer journey.

The content of your messages remains unchanged. You can continue to engage with your customers effectively using the same messaging as before.

Changes to Delay Block

If you previously had a delay block after the trigger block, it has been replaced with the Trigger Inactivity Time setting.

This setting operates similarly, ensuring that your customers receive the first message after a specified delay time. Please refer to our user guide to learn more about this new setting.

Abandoned Cart Workflow

The Abandoned Cart workflow is triggered by the "Added Product to Cart" event. It sends messages to customers who add products to their carts but leave without starting the checkout process.

To prevent duplicate messages, the Abandoned Cart workflow includes an exit condition of "Started Checkout." This ensures that customers will only receive messages from one of the workflows at a time.

Contacts who entered the old Abandoned Cart workflow before the migration will continue and complete that workflow. On the other hand, contacts who abandon their carts after the migration will enter either the new Abandoned Cart or Abandoned Checkout workflows.

Abandoned Checkout Workflow

The Abandoned Checkout workflow is triggered by the "Started Checkout" event. It sends messages to customers who add products to their carts, start the checkout process but ultimately abandon it.

Please refer to the guide below to learn more about the new Abandoned Cart and Abandoned Checkout workflows.

If you have any further questions or require assistance, please refer to the provided resources or reach out to our support team.

Did this answer your question?