โ07-17-2023 06:58 AM
Hey,
I have a Custom Event : User Created with an event property account_type : free/paid
I want to split my Canvas to create two different flows for each account_type.
I found a way to split a canvas based on a user property or an action taken after the canvas entry.
But I can't find a way to split the canvas based on the canvas_entry_properties.
Does someone know how to do this ? I don't want to create two separate canvas.
Thanks a lot,
Matthias
โ07-17-2023 10:50 AM
Hey Matthias,
This might be a nifty usage of the User Update step!
Unfortunately, you can't split an audience based on the custom event property. However, you can use the User Update step to log the custom event property values as a custom attribute. After that, you can send them down appropriate paths using Audience Paths.
This approach or creating 2 separate Canvases would be your best bet. Let me know if you have any questions on this!
Best,
Allan
โ07-18-2023 05:39 PM
@AllanHeo , not sure if this approach that have adopted will work in the above context. Happy to be guided here. I have used a custom event that triggers a canvas when customers haven't opened emails Vs those opened and clicked and treating them differently from comms and channel strategy. Here I have filtered the custom event properties using an Action step. Does this work at all?
โ07-18-2023 08:26 PM
@Rajorigin that's a great thought, and it was also my initial thought; however, I believe the key difference between Matthias's setup and your setup is that your Canvas seems to have a different entry action, but Matthias is relying on the event properties that are tied to the entry action.
To use the Action Path for Matthias's setup, we would require the users to perform another custom event to fall down the correct Action Path step. However, it doesn't sound like there's any other custom event that we're waiting on for Matthias's setup.
Your setup, it looks like the Action Path is in the middle of an ongoing journey.
Hope this answers your question!
โ07-18-2023 09:00 PM
@AllanHeo , makes sense, thank you ๐