Triggering IAMs in Canvas - Questions from Braze Product Team

Very excited for this feature.

1. Among the two approaches, which would you favor, and what are the reasons for your preference
   
   Approach 2. It gives the marketer more control over how and when we want messages to show. Action Paths are great there are instances where we might want more than one IAM to show depending on a user's actions. 

2. On a scale of 1-4 (1 = not at all, 4 = very much), how disappointed would you be if we implemented the other approach?
   2 - a little bit. It would still be a marked improvement being able to have real time IAMs. 

1. 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. It's not fit for purpose for a lot of the use cases I can think of where we need actual real time triggered messages. 

2. Would you still be able to use triggered IAMs if this was the case?
   Yes but not for time-sensitive messaging.

3. 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?
   Reopens aren't frequent - we talk in MAU, not DAU.  This would limit IAM usefulness in canvases for onboarding, post transaction flows (i.e. you now have access to XY&Z), error events (i.e. helping with troubleshooting) to name a few.