Triggering IAMs in Canvas - Questions from Braze Product Team

The update we've been waiting for-excited to see this one coming! 

1. Among the two approaches, which would you favor, and what are the reasons for your preference?
   Provided approach one can do everything that approach two can do, then approach one because it will allow us to use specific event properties to trigger the IAM. 

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

We are also seeking feedback on how “real-time” the Canvas<>SDK information refresh/exchange needs to be. Today, the SDK (which is the agent that shows IAMs) only refreshes information from Braze when the user opens the app, and users may not necessarily open their apps as quickly as they move through a Canvas. Consider the following hypothetical example of how triggered IAMs could work:

• 9:00 am: In Canvas, UserA reaches the Canvas step where they are qualified to be shown IAM_1 immediately after they perform ActionX

• 9:20 am: UserA performs ActionX. No IAM is shown

• 9:30 am: UserA leaves the app and reopens it. Note: at this time, the SDK refreshes information from Braze

• 10 am: UserA performs ActionX. This time, they are shown IAM_1 immediately since the SDK has the latest information from Canvas

The need for the user to leave/reopen the app may not be ideal, but if you feel the feature is still usable, we can deliver a first version of the feature (triggered IAMs in Canvas) to you sooner. With this in mind, we had a few additional questions:

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?
   3- it really removes the utility if we have to get the user back an app. We'd better using another channel. If refresh can't be achieved without closing/opening, perhaps we could have the ability to query the message queue as we do with content cards 

2. Would you still be able to use triggered IAMs if this was the case?
   Yes but it would be the same as our use today which is relatively limited because of this.

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?
   We send a lot of time sensitive deals, typically expiring within 24 hours. We see that our best users will create a session a day, and are most likely to be unsubscribed to email so we'd miss a large amount of organic traffic.