How to Retarget BigCommerce Checkout Abandonment with Automations

Recover potentially lost sales with Sendlane's abandoned checkout Automation trigger for BigCommerce! Follow the instructions below to set up an abandoned checkout Automation for your BigCommerce store.

🚦 Before Getting Started

  1. Check out our guides to integrating BigCommerce and Sendlane and collecting SMS consent with BigCommerce! 
  2. Disable BigCommerce Abandoned Cart Saver if it is turned on
    BigCommerce will only reconstruct Contacts' abandoned checkouts the first time they click the abandoned cart block. If Contacts click the abandoned cart block a second time, they will see an empty cart.
1

 Create a New Automation

Create a new Automation

  1. Click Automations
  2. Click New Automation
  3. Click Start From Scratch
  4. Enter an Automation Name
  5. Click OK!

2

 Add a BigCommerce Abandoned Checkout Trigger

Your Automation will trigger once a customer satisfies the conditions you specify in the BigCommerce Abandoned Checkout trigger.

  1. Click Add Trigger 
  2. Click Abandoned Checkout.

    3. Trigger Options

    • Store Select your BigCommerce store
    • Limit Per Subscriber Select an optional limit on the volume of abandoned cart content Contacts receive
    • Consider Abandoned After Select an amount of time to wait after a customer puts a product in their cart
3

 Add an Email Node

  1. Click the  + button 
  2. Click Send Message 
  3. Click Email 
  4. Click Create New Email (then check out our introduction to Automation email nodes for more information on creating your email!)

Want to learn even more about what makes a great, engaging abandoned cart Automation? Check out eCommerce Academy for expert guidance on strategy and content!

🚨 Emails must contain an abandoned cart block and a button

You must add the following content blocks to your email:

  1. BigCommerce Abandoned Cart to display the product abandoned in the Contact's cart (only one abandoned cart block is allowed per email).
  2. Button which will automatically fill in to link the Contact back to their cart

To place a direct link to a Contact's abandoned checkout in hyperlinked text and images or a button, paste the following snippet in the URL field:

{% set data = trigger.getCheckout() %} {{ data.checkout_data.cart_url}}

If Contacts click this link on a device other than the one they built their checkout on, they will be taken to your store's generic cart page.

4

 Add a Wait Node

We recommend adding a wait node set to 24 hours after all email nodes to prevent your Contacts from receiving emails too frequently.

Add a wait node to your Automation:

  1. Clicking the  + button
  2. Click Wait 
  3. Select a Duration and optional time of day or day of week
  4. Click Done.

    5. Your BigCommerce abandoned cart Automation is now ready to go! Make sure to activate your Automation to start it.

💡 Use Conditional Splits to create nodes for specific products

Conditional Splits allow you to target specific products for specialized content!

Create a Conditional Split node and set the conditions for:

  1. Condition: BigCommerce
  2. Resource: Checkout
  3. Filter: Product or Product Collection, depending on what you want to target
  4. Operator: Select In to specify products or product groups present in the abandoned checkout
  5. Select Items or Groups
  6. Click Done
  7. Create messages under each path:
Yes Path No Path
Customers who had the selected products or product groups in their abandoned checkout Customers who DID NOT have the selected products or product groups in their abandoned checkout

Additional Resources

Troubleshooting

The abandoned cart block isn't available!

The abandoned cart block may not appear in your elements sidebar for two common reasons:

  1. Your eCommerce integration is not set up correctly. Review your eCommerce store's integration with Sendlane for possible connection issues.
  2. You already added an abandoned cart block to your email. Only one abandoned cart block is allowed per email.
Did this answer your question? Thanks for your feedback! There was a problem submitting your feedback. Please try again!