In-App Messages help you get content to your user without interrupting their day with a push notification. Customized and tailored in-app messages enhance the user experience and help your audience get the most value out of your app. With a variety of layouts and customization tools to choose from, in-app messages engage your users more than ever before.
Braze has refreshed in-app messages! Though the creation process is very much the same, our in-app messages have a new, modern look and feel optimized for the best experiences for your customers and give you more options to personalize the experience. For more information on our most recent upgrades to in-app messages, check out our Generation Comparison documentation!
When to Use In-App Messages
In-app messages are good for a lot of things. They can be used in web apps, Android apps, iOS apps, and more!
In-app messages don’t deliver outside of the user’s app and won’t intrude on their home screen, like push notifications do. In-app messages, by their nature, exist within your app and come with context and are almost never unwelcome! They’re always delivered when the user is active within your app.
Great Use Cases
- New App Features
- App Management
- App Upgrades/Updates
- Giveaways & Sweepstakes
To see examples of in-app messages, check out our Client Integration Gallery.
In-App Message Types
Braze currently offers the following default in-app message types:
HTML. Each in-app message type is customizable across content, images, icons, click actions, analytics, display, and delivery.
All in-app messages inherit their prototype from
appboy.ab.InAppMessage, which defines basic behavior and traits for all in-app messages. The protypical subclasses are appboy.ab.SlideUpMessage, appboy.ab.ModalMessage, appboy.ab.FullScreenMessage, and appboy.ab.HtmlMessage.
Expected Behaviors by Message Types
These are what it looks like for your users to open one of our out-of-the-box in-app message types.
SlideUp in-app messages are so-named because traditionally on mobile platforms they “slide up” or “slide down” from the top or bottom of the screen. In the Braze Web SDK, these messages are actually displayed as more of a Growl or Toast style notification, to align with the web’s dominant paradigm. They cover a small portion of the screen and provide an effective and non-intrusive messaging capability.
Modal in-app messages appear in the center of the screen and are framed by a translucent panel. Useful for more critical messaging, they can be equipped with up to two click action and analytics enabled buttons.
Full in-app messages are useful for maximizing the content and impact of your user communication. On narrow browser windows (e.g. the mobile web),
full in-app messages take up the entire browser window. On larger browser windows,
full in-app messages appear similarly to
modal in-app messages. The upper half of a
full in-app message contains an image and the lower half allows up to eight lines of text as well as up to two click action and analytics enabled buttons
appboyBridge interface to call methods on the Braze Web SDK from within your HTML, see Best Practices for more details.
To enable HTML in-app messages, your SDK integration must supply the
enableHtmlInAppMessages initialization option to Braze, e.g.
At Braze, the web SDK treats the “Email Web Capture Form” message type template as an HTML in-app message, therefore the same
enableHtmlInAppMessages option must be set.
The following example shows a paginated HTML in-app message: