Hey @mvs
Thank you for sharing your question here in the community,
- Yes you are correct, we can only use event data as the trigger of a flow and can use that trigger data in the show/hide logic and you can use previous data only by using conditional splits in a flow
instead of using show/hide logic, why not just create different emails with static product blocks?
so just add a conditional split and split based on Collections (instead of products) and if they purchased from these collections they will go through yes path and that email will have products relevant to that and so on for all the conditional splits that you want
I totally understand what you want and if they purchased 3 different products from 3 different collections, then it will go through the first definition in the conditional split where the condition is true. so yes this is not accurate, but this is the closest you can get without complicating things.
So I see what you are trying to achieve, but i am afraid creating those flows is the only way to go. Instead look at the possibility to create flows based on collections, instead of each SKU/product, as that will complicate a lot of things.
Not sure if that helped, but I hope it did
Cheers
Arpit
Hey @mvs
Thank you for sharing your question here in the community,
- Yes you are correct, we can only use event data as the trigger of a flow and can use that trigger data in the show/hide logic and you can use previous data only by using conditional splits in a flow
instead of using show/hide logic, why not just create different emails with static product blocks?
so just add a conditional split and split based on Collections (instead of products) and if they purchased from these collections they will go through yes path and that email will have products relevant to that and so on for all the conditional splits that you want
I totally understand what you want and if they purchased 3 different products from 3 different collections, then it will go through the first definition in the conditional split where the condition is true. so yes this is not accurate, but this is the closest you can get without complicating things.
So I see what you are trying to achieve, but i am afraid creating those flows is the only way to go. Instead look at the possibility to create flows based on collections, instead of each SKU/product, as that will complicate a lot of things.
Not sure if that helped, but I hope it did
Cheers
Arpit
The main issue with this is in reality we have a lot more products than the three in my example. We’d have to manage a separate flow to handle every possible combination of products a user has previously purchased.
hey @mvs
I understand you have a lot of products but dont you have collections and split based on those collections? I feel that’s the best way to go about this for now.
