Hey @Lorena Jaqueline,

From your scenario and the screenshot, I don’t think it’s actually the flow structure that’s incorrect, but rather that you’re using the incorrect variable. The {{ person.ViewedItems.0.Title }} variable you’ve using is meant to bring in the most recent viewed items into an email - in that regards, it’s doing exactly just that. 

A lot of times the use of this would be either in campaign emails or within other flow emails where you don’t have access to the explicit viewed product event data. The viewed product event is sort of unique in the sense that not only is an event recorded, but we also record an accessible profile property for this sort of use case. 

Instead of using that {{ person.ViewedItems.0.Title }} variable, you may want to take a look at our Creating a Browse Abandonment Flow Help Center article which highlights how to build your browse abandonment flow email triggered by the viewed product event. It may also help to take a look at some of the resources below too if you’re unfamiliar with building dynamic table blocks:

• How to build dynamic blocks in a flow email (classic editor)
• How to Build Dynamic Blocks in a Flow Email (new editor)
• Repeating a Block Based on Dynamic Data
• How to insert a dynamic image in an event-based flow email

@Anna McCarthy, our template specialist also has a great walkthrough and example on how to use event data to build a dynamic table block:

One additional thing to note that I’ve seen a lot, because a viewed product event only carries one set of data and not an array of data, you wouldn’t need to set your dynamic table block to dynamic. Instead, you’ll want to use the Static option and to input the correct event variables. I know this is called out in the Browse Abandonment flow article I included above, but it often times gets overlooked. 

I hope this helps!

David