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...
So good to know this is on the works!
Among the two approaches, which would you favor, and what are the reasons for your preference?So
Approach 2 (Allow real-time triggering based off actions specified within an IAM Message Step). It feels more specific to the use case of trying to replicate the behaviour we see in campaigns. Action paths may be useful to trigger multiple messages but the fact that we're missing in Canvas the behaviour we see in Campaigns for IAMS I feel would be better addressed if the change happens inside the IAM step.
On a scale of 1-4 (1 = not at all, 4 = very much), how disappointed would you be if we implemented the other approach?
Probably 2. Slightly disappointed.
On a scale of 1-4 (1 = not at all, 4 = very much), how disappointed would you be if users needed to reopen the app to allow the SDK to refresh information?
4 = Very disappointed. Then I don't see how this is different from the current scenario where the triggering is not immediate like it happens in campaigns?
Would you still be able to use triggered IAMs if this was the case?
I wouldn't see any difference to how they're being used right now, so I'd have to continue to use them for cases where immediacy is not needed but with my needs not being covered.
How frequently do your users typically leave/reopen their app? What scenarios, if any, do you foresee where users are unable to be shown IAMs due to them not reopening the app?
Not frequently. Users average behaviour is only 1-2 days a week of using the app.
