Exclude products from abandoned cart emails

@retention Thank you so much! This worked perfectly. I couldn’t figure it out at first and thought it wasn’t working. Then realized it was because I added the tags to the products, and the preview carts I was using to test were done before the tags were added. Thank you tremendously for taking the time to do this for me 

@retention This was a life saver. Spent days trying to figure this out. 

Question, what if you wanted to include these types of add on products somewhere else in the email but not as detailed, like maybe just an itemized list of titles? 

Hey @ali_luxeAC,

So glad you were able to resolve your own issue and highlighting that sending yourself a preview properly hid the product, unlike the Klaviyo previewer! I’m sure this bit of information will help future Community members who may be confused about this as well!

@sleepingdog, if you wanted to include these types of additional products in your email, but with less detail, you can do so by either using a text block or building another dynamic table block while using the opposite rules used to hide these products away. Borrowing @retention’s example, instead of building an if statement to hide these products which has this “ac_exclude” tag, you can build your if statement to instead only display products with this “ac_exclude” tag.

In terms of the format and the details you want to pull in for these additional products, that would depend on what dynamic variables you are using and including. To further understand how dynamic blocks are build and how to customize your emails with event variables, I would suggest taking a look at the About Using Event Variables to Personalize Flows and How to Build Dynamic Blocks in a Flow Email Help Center articles. 

I hope this helps!

David

Hey @davidbilow,

I would suggest reviewing how you are implementing the code and double checking the variables you are using. Because every store’s integration may be slightly different, some adjustments may be required to achieve the solution posed by @retention in a seamless manner. 

In addition, Route Shipping has a similar solution where instead of evaluating products based on their category, they dictate which products to hide in the dynamic table block through evaluating if a product has a specific title. In their How do I exclude Route from Klaviyo? article they explain how to hide a products whose title equals Route Package Protection' from appearing. Their strategy is also a viable option which can be adjusted to hide specific products which you can customize for use with your own setup if you wish as well. 

Furthermore, because Outlook uses Microsoft Word as their rendering engine for HTML, emails rendering differently than what is designed within an email builder is a known issue explained in he My Email Looks Different When Viewed in Microsoft Outlook Help Center article.

Have a great day!

David

Hey @Zach-LP,

You should be able to accomplish something similar in BigCommerce despite them not using product tags. This would all depend on the if-statement you are create and the variables and values you were evaluating as part of the statement. Instead of using a product tag like you would in Shopify to distinguish these products, you can potentially identify these products within BigCommerce by grouping them in a specific category. 

David

Hey @montes,

The solution that’s being discussed in this thread to omit and prevent certain products from being pulled into an email through a dynamic table block would not be the same as using flow filters to exclude users from a flow. 

The difference here is that a flow filter is used to evaluate if an individual is eligible for the flow as a whole. The solution being discussed here would be on a more targeted level of restricting only certain products from appearing in an email. For example, if someone purchased a t-shirt and a baseball cap, if you wanted to omit the baseball cap, using a flow filter will prevent the user from entering the flow as a whole. Recoding the dynamic table block will still allow the customer to enter the flow, but will prevent the baseball cap from appearing in their abandoned cart email. 

David

Hey @tobias_wildling_shoes,
Just to confirm, are you using the exact code you shared of:

{% if 'ac_exclude' in item.product.tags %} 

{% endif %}

If so, then it seems like you’re missing the response portion of the if-statement. This means that even when this if-statement was true, nothing would be returned since you haven’t defined a response in the statement. My colleague, @Anna McCarthy actually has a great tutorial on using If/Endif/Elif/Else Statements which I’ve included below that I think would be really helpful to take a look at:

If you were using the code provided by @retention verbatim and it worked successfully, I don’t see why removing the not function in the code wouldn’t be working to achieve the inverse effect. Omitting the not from the code would cause those products tagged with ac_exclude to be shown and products without this tag to be hidden. 

David

This was very helpful! Thank you for posting a solution.

Hey @ajensen,

I suspect the issue you’re running into may be the syntax you’re using is incorrect. Since the code discussed in this thread relate to the Shopify Checkout Started metric, the syntax would not translate to an email in a flow triggered by BigCommerce’s Started Checkout event. It may be helpful to take a look at some of the resources that were previously provided such as the About Using Event Variables to Personalize Flows and How to Build Dynamic Blocks in a Flow Email Help Center articles to learn how to properly use and pull the correct dynamic syntaxes for your use. 

I think it would also be helpful if you provided the full if/else statement to see if others can lend some advise.

David

Hey @kellysandberg,

Are you sure you’re putting those codes in the source code of the text box? A lot of times I see customers mistakenly add code directly into the text box instead of the source code which is visible to recipients. 

David

Hi @AlexW ,

Let me see if this helps. While we do sync variants and their images to the catalog in Klaviyo they aren't accessible via a Product Feed. I'm afraid there isn't a specific configuration example but I can provide you with our documentation for how to utilize a feed in Klaviyo and can then work backwards from there: https://help.klaviyo.com/hc/en-us/articles/360033046811-Add-a-Custom-Web-Feed-to-a-Flow-Email

There are a few different ways you could set this up but the high level overview is to take a piece of identifying product information from the event data in your flow (e.g. variant ID or variant color) and look that up in the web feed. The corresponding record in the webfeed would contain an array of other product variants of the same color which could then be used to populate some images/links in your email template. Because this array of products with the matching color would likely also contain the original product being looked up you'd want to also include the product ID for each entry in the array so you could add some logic in your template to exclude the original product that was purchased.

Hey @bill_wishgarden 

Thank you for following up on this topic.

As @retention mention in his first response, for the image part, you need to wrap the existing snippet, in a new “IF” statement that should look like this:

{% if not 'ac_exclude' in item.product.tags %}{% if item.product.variant.images.0.src %}{{item.product.variant.images.0.src}}{%else%}{{item.product.images.0.src|missing_product_image}}{%endif%}{%endif%}

Hope this helps!