Sounds really nice! It's a feature we're really looking into as we use a lot of in-app messaging and it's always a pain to create additional IAM campaigns for large flows.
1. Among the two approaches, which would you favor, and what are the reasons for your preference?
Approach 2 might be a good solution, but how would I control that a user stays in the canvas step? What if I need to keep the IAM in the application longer than the canvas flow? How do I make sure that a customer has not already entered the next step? Would the IAM still be possible to get triggered?
However, the downside of approach 1 would be that customers could only get 1 IAM with the ranking and I like to have more control, so approach 2 would be the best option.
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?
Since both approaches would be great -> 2
3. 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?
Clear a 4. Our goal is to keep the customer in the app and show the right communication at the right time. Reopening the app would mean that we would not be able to verify that the customer received the correct communication during the journey.
4. Would you still be able to use triggered IAMs if this was the case?
Would use campaigns
5. 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 often in one session. When they open the app, they usually stay in the app to complete their order. They may close and re-open to check competitors.
Really looking forward to test this new IAM approach! That would make many lives easier ;).
