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 minutes, we’d appreciate it if you could answer the questions in bold below. We can add you to the early access when the feature is available in exchange as well. Let me know if you have any questions and thank you in advance! Also, if you’d prefer to chat over a call, happy to do so instead (please schedule here). Thank you, Rishi Product Manager at Braze Questionnaire - Triggered IAMs in Canvas The current state of triggered IAMs: In Campaigns, marketers can specify a custom event that triggers/shows an IAM to a user in real-time In Canvas, marketers can specify a custom event within an Action Path that triggers/shows an IAM to the user once they do the following: (1) perform the action, then (2) restart the app (they’ll then see the IAM once the app opens) Our ask: We are considering one of the following approaches for providing more real-time triggered IAMs in Canvas and would like your input. Approach 1 Approach 2 Allow real-time triggering of IAMs via the Action Path Allow real-time triggering based off actions specified within an IAM Message Step Benefits: Branching actions. Marketers can define several triggers/actions that all show different IAMs and qualify the user for all of them, but only display the IAM for the first action performed (and disqualify the rest) Ranking actions. If multiple actions are performed by the user within the action path’s time window, Braze will show the associated IAM then send the user through the highest-ranked action path only Benefits: Independent control of IAM message triggers/actions. Actions will be defined within the IAM Message (similar to IAM expiration), giving the marketer more control This approach/feature is easier for Braze to build, so we can deliver it to customers faster A couple of questions for you here: 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? 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: 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? Would you still be able to use triggered IAMs if this was the case? 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've created new blocks and templates for In-App Messages. Would love some feedback
Hi all In the drag&drop in-app editor, we created tools to enhance our own campaigns. The impact of this extension on our teams convinced us to release it as an extension to help other marketers achieve the same results. Video embedding (YouTube, Vimeo, and MP4), countdown timers, interactive scratch-to-reveal coupons, animated counters, auto-close messages, copy-to-clipboard coupon codes, an In-App Messages template library and import/export email templates are just a few of the features included in this extension. Each tool is crafted to help marketers create more dynamic, engaging content—no coding required! This extension is available in the Chrome extension store: https://chromewebstore.google.com/detail/hippo-power-tools-for-bra/klnaclpjbenicaapccooonooopnieekg Would love any feedback you have on this extension, including ideas for more features. Our goal is to make these useful tools for all Braze users.Rate limiting Action based campaigns
Greetings! Our team is working on implementing an Action based campaign for surveys (using in App messaging) We trigger the survey when the user performs Custom events ( which are navigation events that we have predefined ). One of our requirements is that we only want to trigger surveys for X users a day. Reason being - we have a large customer base and don't want to overload our servers. Also, we want our surveys to be spread over time so there is no time period bias in the responses. Problem: We are unable to configure such a rate limit in our Action-based campaign. The only rate limiting option available is a blanket "Stop sending this in-app message after approximately X impressions" which is not useful for us, since we want to rate limit, not a volume limit. Wondering if there is such a thing as rate limit for Action based campaigns and keen to understand how others might have tackled this situation. Thank you in advance !
Help - IAM's are spamming some of our users
We have IAM's in our mobile app that are occasionally being sent multiple times in a day to some users. This is concerning because it looks very spammy. We upgraded our iOS Braze SDK on May 15th and saw an increase in this behavior. But, it's been happening before just the rate was about 5% of users. Now it is more like 20% of users being affected. I find it hard to believe this is just an SDK issue. Plus, we also see this behavior on Android. About one of the affected campaigns: The most concerning campaign is a rating request - not one you want to spam users with 😮 We have the Delivery Controls set so the user should not receive the campaign more than once in 30 days. Is there another way to try to prevent a user from seeing the campaign more than once that we are missing? Thanks in advance for any insight. It will be a bummer if the only resolution as another SDK update. That takes many months to propagate through our entire install base.
