In-app messages integration
In-app messages help you get content to your users 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 from your app. With various layouts and customization tools to choose from, in-app messages engage your users more than ever before.
Check out our case studies to see examples of in-app messages.
In-app message types
Braze currently offers the following default in-app message types:
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
InAppMessage, which defines basic behavior and traits for all in-app messages. The protypical subclasses are
Expected behaviors by message type
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 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 our best practices for more details.
To enable HTML in-app messages, your SDK integration must supply the
At Braze, the web SDK treats the “Email Web Capture Form” message type template as an HTML in-app message; therefore, the same
The following example shows a paginated HTML in-app message:
By default, in-app messages are automatically displayed as part of our recommended integration instructions. Additional customization can be done by following the steps in this guide.