Creative In-App Messaging Ideas for Braze Campaigns

Close view of a hand lowering a brass key on a green cord into its own compartment of an oak tray, with three other keys in separate compartments, showing one in-app messaging idea per trigger.

Creative in-app messaging ideas work best in Braze when the format, the trigger and the audience are chosen together. This guide covers push primers, multi-page flows, surveys, email capture and slideups, with the documented mechanics behind each. It ends with a launch sequence for a hypothetical retailer app.

Key Takeaways

  • Choose the editor before the idea, because switching a drag-and-drop message to the traditional editor converts it to HTML and can't be reversed.
  • Ask for push permission after a high-value action, using the Request Push Permission button action.
  • Give each idea its own trigger or audience, because only one in-app message displays per occurrence of a trigger event.
  • Decide the follow-up campaign for a survey before you write the question.
  • Test the login-after-capture path for an email capture form with a user who already has an account.

Which creative in-app messaging ideas does Braze support?

Braze documents several in-app formats, and each suits a different idea. Fullscreen and modal messages work in both editors. Slideups, custom HTML, email capture forms and simple surveys use the traditional editor.

FormatEditorDocumented fitDesign detail to plan for
FullscreenDrag-and-drop and traditionalMandatory app updatesThe hub advises avoiding in-app channels for critical, time-sensitive updates
ModalDrag-and-drop and traditionalSales and promotions with static promotion codes or offersAbout two to four lines of body text
SlideupTraditionalNew terms of service, cookies, short snippetsUp to three lines of copy before truncation
Custom HTMLTraditionalCustom layouts or interactive experiencesMust include a close or dismissal control
Email capture formTraditionalCollecting email addressesSubmit button appears after a valid address
Simple surveyTraditionalPreferences, attributes, satisfactionUp to 12 choices

Choose the editor before the idea, because switching a drag-and-drop message to the traditional editor converts it to HTML. You can't switch it back. We recommend deciding on day one whether the idea needs a slideup or custom code.

How can a push primer earn the permission prompt?

A push primer is the most clearly documented idea in the channel. Braze describes using an in-app message to explain what users can expect before they see the native push prompt. The stakes are real: the prompt can be displayed only once per install, and on Android 13 and later, two denials block further prompts.

Our suggestion is to treat timing as the creative decision. Braze suggests waiting until a user completes a high-value action, or until there's a compelling need that push can address. A first order is a natural moment, because the user now has a reason to want shipping tracking information.

Use the no-code primer, which is the Request Push Permission button action. With it you don't need push subscription filters, because the SDK suppresses the message based on the device's push permission state. If you set up custom logic or deep links instead, the SDK can't identify a push primer.

Avoid a user-level filter such as Push Subscription Status is not Opted In. It excludes users who are already opted in on another device, so they never see the prompt on a new one. We recommend writing the copy as a promise you can keep, naming the one notification type the user will receive first.

How can a multi-page flow guide a new user?

The drag-and-drop editor lets one message carry up to ten pages. Users tap or click to move through them, so a modal can become a short onboarding or welcome sequence. Every page must be linked to another, or the message can't be launched.

Three documented behaviours shape the design. The close X can't be removed, and a background image set on one page applies to all pages. A Liquid syntax error on one page affects the rendering of Liquid on all pages, because the pages are not independent.

We recommend one background for the whole flow. When a preview shows raw Liquid, check every page, because a broken preview on one page doesn't mean the error is on that page.

Messages built in the drag-and-drop editor don't reach users on older SDK versions. Body clicks aren't automatically collected for these messages, and you can segment on button clicks for up to two buttons. Decide up front which two buttons carry the signal you want to act on.

How can a survey feed your segmentation?

The simple survey has the clearest data payoff of these ideas. You can add up to 12 choices, then either log attributes on submission or log responses only. Attributes let you create new segments and retargeting campaigns, while response-only logging records button clicks that aren't available for retargeting.

Match the data type to the question. A single-choice question needs a string attribute, and a multiple-choice question needs an array, otherwise responses won't be logged. Braze's own example measures customer satisfaction and sends win-back campaigns to users who left low scores.

We recommend deciding the follow-up campaign before you write the question. A survey whose answers have no planned use costs the user attention and returns nothing.

Braze's release notes dated 20 Aug 2026 also list in-app message and landing page surveys as generally available. Check the current documentation for the survey experience that suits your workspace.

How can an email capture form grow your reachable audience?

The form adds the address to the user's profile, and the submit button appears only after the user enters a valid address. For anonymous users, the address is stored on the anonymous profile tied to the device. Target the form with the filter Email Available is false, so people who already have an address on file never see it.

Plan identity before launch. If an address already exists on the profile, the newly entered one overwrites it.

If changeUser is called with an existing external_id, the anonymous profile is orphaned. Any fields that already exist on the identified user are lost, including the email address.

We recommend testing the login-after-capture path with a user who already has an account, because that is where an address can disappear. Where fragmented profiles are the wider problem, our customer data management service covers identity resolution. On the web, Braze notes that you must supply the allowUserSuppliedJavascript initialization option to enable HTML in-app messages.

An email address is personal data, and this post doesn't settle consent or lawful-basis questions for your markets.

When should a slideup replace a modal?

Slideups are non-obtrusive and let users keep interacting with the app while the message displays. Braze names terms of service and cookies as good fits. Modals use a screen overlay and suit sales and promotions, so keep the body copy to about two to four lines.

We recommend a slideup when the user can ignore the message without consequence, and a modal when ignoring it costs them something. Fullscreen needs more care. Braze's example is mandatory app updates, yet the hub also recommends avoiding in-app channels for critical, time-sensitive updates, because they rely on device connectivity.

Check assets early, because image files have a recommended size of 500 KB and a maximum of 5 MB. Braze lists PNG, JPEG and GIF as supported types, and SVG isn't supported. Confirm file types before you commission artwork.

How does personalisation change delivery?

Personalisation turns a creative idea into a delivery question. A message is delivered as a templated in-app message when Re-evaluate campaign eligibility before displaying is selected, or when it uses Liquid tags such as connected_content.

The SDK then reevaluates the message when the trigger event occurs. That requires a network connection and can add a short delay (typically under 100 ms on a stable connection).

Standard messages behave differently, because after a message is cached it can display when its trigger occurs while the device is offline. Braze advises against the re-evaluation option for messages that must trigger while the user is offline.

Standard messages don't log aborts. An abort means the user didn't see the message despite performing the trigger action. Templated messages do log aborts, because the Liquid evaluation occurs after the trigger action.

Two safeguards belong in every test plan. Braze's checklist asks whether you have accounted for a default attribute value when the Liquid returns no information. Image URLs pulled in through Connected Content or Liquid must begin with https://, because Braze states that http:// will crash your app.

What does a hypothetical launch sequence look like?

Take a hypothetical retailer app with four ideas to launch in one quarter: a welcome flow, a push primer, a preference survey and a sale modal. The first mistake is giving all four a session start trigger. Only one in-app message displays per occurrence of a trigger event, the highest priority wins, and ties go to the most recently created message.

We recommend giving each idea its own trigger or audience instead. The welcome flow starts at session start for new users only. The push primer fires on a custom event that marks a first order, in line with Braze's advice to wait for a high-value action.

The survey fires on a custom event the app logs when setup is complete. The sale modal targets existing customers, so it never contests a new user's session. Priority now settles only the rare tie, rather than deciding which idea users ever see.

This example is illustrative. It contains no client data and no outcome figures.

How does this connect to the rest of the programme?

Triggers decide when ideas collide, so start with the guide to in-app message triggers. Audience rules come next, and segmenting users for targeted in-app messaging covers them. Measurement belongs in the plan from the start, and measuring in-app message engagement explains what to track.

For the build itself, see creating engaging in-app messages with Braze. The broader case is in in-app messaging for higher customer engagement. Braze documents every format above in its in-app message documentation.

Our case study on interactive gamification covers a related idea, an embedded interactive reward placed in the lifecycle path for lapsing users.

As a Braze implementation partner, CustomerIK recommends launching one idea per trigger. Start with the push primer after a first high-value action, then review delivery results before adding the next idea.

Frequently Asked Questions

1. How many pages can a multi-page in-app message have?

A drag-and-drop in-app message can have up to ten pages, and every page must be linked or the message can't be launched.

2. Can two in-app messages display on the same trigger?

Only one in-app message displays per occurrence of a trigger event, so the highest-priority message wins when campaigns share a trigger.

3. Which editor do I need for a slideup?

Slideups use the traditional editor, as do custom HTML, email capture forms and simple surveys.

4. Can an in-app message display while a device is offline?

After a message is cached, it can display when its trigger occurs while the device is offline.

5. Why don't I see opens for in-app messages?

In-app messages do not use an Opens metric, so compare impressions and clicks instead.

Sources

CustomerIK is a Braze implementation partner working across onboarding, technical integration, marketing operations and customer data management.

If you're planning an in-app programme and want a second view on trigger design and launch order, let's talk.

Preferences

Privacy is important to us, so you have the option of disabling certain types of storage that may not be necessary for the basic functioning of the website. Blocking categories may impact your experience on the website.

Accept all cookies
Accept all cookies

These items are required to enable basic website functionality.

Always active

These items are used to deliver advertising that is more relevant to you and your interests.

These items allow the website to remember choices you make (such as your user name, language, or the region you are in) and provide enhanced, more personal features.

These items help the website operator understand how its website performs, how visitors interact with the site, and whether there may be technical issues.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.