Forum Discussion
Audience Path through event properties
Hello community!
I need your help to set up a Canvas Flow:
Context:
In our subscription we are customising the unsubscribe flow based on the reason. We register this reason as an event property of the event that triggers the flow ( subscription cancel complete).
Problem:
It does not find the way to direct the users in a flow or another depending on the property of the event, since the ''audience path'' tool does not allow to split by event property.
How would you do it? I could do it through conditions and liquid, but the flows are not exactly the same for all properties/reason.
Thank you very much!
This is a common question asked here, you can find a lot of solutions. Short answer is there is no step to do so.
- You can configure the event property filters at the Entry Settings. This means you will need a canvas for each flow
- You can create dynamic messages using liquid (if canvas_entry_property = x, elsif canvas_entry_property = y, endif). This means the flow has to be the same for both sets.
- Set up an hourly refreshed SQL Segment Extension and use that in your decision split.
- The last option to create conditional spacergif webhooks that log a message received and using those filters in a canvas step. This does add a few steps to your canvas and more challenging to QA/review.
- rayelkhoPractitioner III
This is a common question asked here, you can find a lot of solutions. Short answer is there is no step to do so.
- You can configure the event property filters at the Entry Settings. This means you will need a canvas for each flow
- You can create dynamic messages using liquid (if canvas_entry_property = x, elsif canvas_entry_property = y, endif). This means the flow has to be the same for both sets.
- Set up an hourly refreshed SQL Segment Extension and use that in your decision split.
- The last option to create conditional spacergif webhooks that log a message received and using those filters in a canvas step. This does add a few steps to your canvas and more challenging to QA/review. - godofprogrammerActive Member
I think you are trying to send different messages based on the reason for unsubscribing. For my business, I use conditions and liquid to personalize customer experiences e.g. sending messages based on their browsing or purchase history. You can do something similar by pulling event data and creating flows that fit each customer’s journey. The messaging is more relevant to them, whether they’re canceling or making a purchase.
It is working in my case, hopefully, it will help you out as well. - SergitcActive Member II
Thanks guys, I think i will do a canvas for each property because i need different flows for each property.
Thanks for your help!