Forum Discussion
Triggering IAMs in Canvas - Questions from Braze Product Team
Our team at Braze wants to bring real-time triggering in-app message (IAM) functionality to Canvas. Today, real-time triggering IAM functionality only exists in Campaigns. If anyone has a few minu...
Hi everyone, thank you so much for the responses so far. These are so helpful for me and the team.
I wanted to clarify the approaches and was wondering if that would change anyone's answers.
First, approach 1 can do everything approach 2 can do. In approach 1, the action path contains the trigger action and the message step contains the IAM. In approach 2, the message step contains the trigger action and the IAM. That's the only difference.
Second, approach 1 can actually do a little more than approach 2, with regards to branching capabilities. For example, if you wanted to trigger different IAMs on different custom events, or the same custom event with different properties, approach 1 would be able to support this, but not approach 2.
Given the above information, how would you answer the following questions? (if you'd answer differently)
Among the two approaches, which would you favor, and what are the reasons for your preference?
On a scale of 1-4 (1 = not at all, 4 = very much), how disappointed would you be if we implemented the other approach?
