Solved

Show/Hide Using Event Data for Specific Items

  • 22 September 2022
  • 1 reply
  • 48 views

Badge +6

I am working with a client who sells around 20 products. I want to build an email with dynamic content for their post purchase journey showing useful tips and tricks per product ordered. 

Ideally I want to have say 20 table blocks with a show/hide clause on. Then regardless of how many products they ordered, it will show all the necessary blocks. So I know I need to use event|lookup: but I’m not sure on what should follow…

 

Do I use the actual name of the product? E.g. Vitamin C Face Moisturiser so that would  be event|lookup:’Vitamin C Moisturiser’ 

Do I also need to use the code from the preview window to add to it event|lookup:’event.extra.fulfillments.0.line_items.0.title’ kind of thing? 

I’m concerned that if any other data is passed through with a conflicting name, it will show the wrong blocks and I am not familiar with using event data for show/hide only customer properties.

Thanks guys!

 

icon

Best answer by In the Inbox 22 September 2022, 16:35

View original

1 reply

Userlevel 5
Badge +20

Hi @jadebiscuit 

Thanks for posting your question in the community!

While I love the idea to dynamically show different content blocks based on the product purchased. 

I have used this resource a TON to set up dynamic show/hide blocks based on event metrics:

https://help.klaviyo.com/hc/en-us/articles/115002779071-About-Using-Event-Variables-to-Personalize-Flows

With that said, setting up an email with 20 different blocks might cause more headaches. I’ve set up a few emails using dynamic blocks and have tried to limit those emails to 2-3 blocks max. 

A couple of reasons:

  • One, as you noted, the more blocks you have with dynamic logic, the higher the likelihood something could get incorrectly shown.
  • Two, when the email is sent, the code for the email will contain all 20 blocks, even if they are hidden, which could exceed some size limits at the top ISPs (Gmail = 102KB) and the email will be clipped. 
  • Third, you do lose the analytics to track and monitor engagement-per product-that might be helpful for future marketing opportunities. 

Based on these 3 things, I might recommend creating an email for each product and either setting up a flow conditionally filters users to the right message, or set up a flow per product and the trigger filters to that specific product SKU or title. 

I hope this is helpful. 

@In the Inbox 

Reply