Skip to content

In-app message testing

It is extremely important to always test your in-app messages before sending your campaigns. Our preview and testing capabilities offer two ways to take a look at your in-app messages. You can preview your message, to help you visualize as you compose it, as well as send a test message to your or a specific user’s device. We recommend you take advantage of both.

Preview

You can preview your in-app message as you compose it. This should help you visualize what your final message will look like from your user’s perspective.

In-app message generation preview

Preview what your message will look like to a random user, a specific user, or a customized user—the latter two are especially useful if your message contains personalization or multiple languages. You can also preview messages for either mobile devices or tablets to get a better idea of what users will experience.

Compose tab when building an in-app message showing the preview of what the message will look like. A user is not selected, so the Liquid added in the body section displays as is.

Braze has three generations of in-app messages available. You can fine-tune to which devices your messages should be sent, based on which Generation they support.

Switching between generations when previewing an in-app message.

Test

Preview message as user

You can also preview messages from the Test tab, as though you were a user. You can select a specific user, a random user, or create a custom user.

Test tab when building an in-app message. "Preview message as user" is set to "Custom User" with available profile fields appearing as configurable options.

Test checklist

  • Do the images and media show up and act as expected?
  • Does the Liquid function as expected? Have you accounted for a default attribute value in the event that the Liquid returns no information?
  • Is your copy clear, concise, and correct?
  • Do your buttons direct the user where they should go?

Accessibility scanner

To support accessibility best practices, Braze automatically scans the content of in-app messages created using the traditional HTML editor against accessibility standards. This scanner helps identify content that may not meet Web Content Accessibility Guidelines (WCAG) standards. WCAG is a set of internationally recognized technical standards developed by the World Wide Web Consortium (W3C) to make web content more accessible to people with disabilities.

Accessibility scan results

How it works

The scanner runs automatically on custom HTML messages and evaluates your entire HTML message against the full WCAG 2.1 AA rule set. For each flagged issue, it shows:

  • The specific HTML element involved
  • A description of the accessibility issue
  • A link to additional context or remediation guidance

Understanding automated accessibility testing

Automated accessibility testing helps catch common issues like missing alt text or low color contrast based on WCAG Level AA standards. It’s a powerful starting point for building more inclusive messages.

But automation can’t catch everything. Some issues need a human eye—like whether the focus order makes sense, if links and buttons are clearly labeled, or if your instructions are easy to follow. Think of these checks as a diagnostic tool, not a final verdict. We recommend reviewing flagged issues manually and using your best judgment when something is marked as “Needs review.”

For extra support, our Accessibility at Braze guide shares practical tips for making your content easier for everyone to use, including:

When you combine automated testing with thoughtful manual review, you’ll catch more issues—and create a better experience for all your users.

HOW HELPFUL WAS THIS PAGE?
New Stuff!