Solved

Exclude products from abandoned cart emails

  • 13 February 2021
  • 8 replies
  • 460 views

Badge

Hello!

I am wondering if it is possible to exclude certain items from the dynamic table block for the abandoned cart e-mails. Or only include certain items/ collections. These are items that are “in” their cart but I do not want to send them to encourage them to finish checking out. For example I have the cloverly app for offsetting carbon footprint for shipping and I also have an app that I use to have multiple options for products. I don’t want these items showing in the abandoned cart e-mail. Is there a way to go about excluding these?

Thanks so much for any help!

Natalie

 

 

 

icon

Best answer by retention 15 February 2021, 17:42

View original

8 replies

Userlevel 7
Badge +5

@tangleartistry There is a way, but it requires some coding. It’s actually quite interesting to achieve.

If you have multiple different products that you want to exclude from the dynamic table block, the easiest way to do it is to tag those products in Shopify, and then use that tag to exclude the products.

Let’s say for example you tag them with “ac_exclude”.

Then, in the dynamic table block, you need to wrap the text part (Title, Quantity, Price, etc.) in an “IF” statement that should look like this:

{% if not 'ac_exclude' in item.product.tags %}
<h3><a href="{{ organization.url }}products/{{ item.product.handle }}">{{ item.product.title }}</a></h3>

<p>Quantity: {{ item.quantity|floatformat:0 }} — Total: {% currency_format item.line_price|striptags|floatformat:2 %}</p>
{% endif %}

This will check for each product if “ac_exclude” is one of the tags. If the product doesn’t have the “ac_exclude” tag, it will be shown in the feed.

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 that you’ll succeed in implementing this!

Badge

@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 :hugging:

 
Userlevel 7
Badge +5

@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 :hugging:

 

 

Really glad that you’ve figured out how to implement it. It can be tricky.

Badge

@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? 

This only partially worked. The coding successfully hid the product names, but (in the preiview) the photos are showing as blank boxes and they are still linked.

**EDIT: it works just fine- I emailed myself a preview instead of previewing in Klaviyo and the flow works correctly. Thanks!

 

 

Userlevel 6
Badge +4

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

 

@retention @david.to @ali_luxeAC I was successful with hiding the text, however, I’m experiencing the same issue as you did, @ali_luxeAC , where the image block is visible (but the image itself is hidden). In the previewer it’s an empty box. In an emailed version it is still a link to the product.

So instead of an image block, I used a text block and coded in the image. This hides it appropriately, but the images are huge in an outlook email.

Any ideas anyone?

Thanks!

Userlevel 6
Badge +4

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

Reply