In-App Messaging Use Cases: What to Launch First in Braze

Top-down view of a hand lifting one green-edged cream card from an oak card rack while two more stay seated, showing one in-app message per trigger.

In-app messaging use cases in Braze include push priming, promotions, feature adoption and personalised first screens. Each one pairs a message type with a trigger and an audience rule, and each depends on a different setting being right. This guide maps the documented use cases to those settings and suggests an order for launching them.

Key Takeaways

  • Push priming comes first, because the operating system allows the native push prompt only once per install.
  • A primer built with the Request Push Permission button action is suppressed on devices that can't use it. Custom logic or deep links lose that protection.
  • Only one in-app message displays per occurrence of a trigger, so give each use case its own trigger where you can.
  • Re-evaluating eligibility and Connected Content make a message templated, which needs a network request and a connection at display time.
  • In-app messages have no Opens metric. Compare Impressions and Clicks, and define the push opt-in event before launch.
  • Braze recommends avoiding this channel for critical, time-sensitive updates.

What are the main in-app messaging use cases in Braze?

The Braze in-app message hub lists push priming, sales and promotions, feature adoption and highly personalised campaigns. It also points to new app features, reviews, app upgrades and giveaways as further ideas. Braze added in-app message surveys to its release notes on 20 Aug 2026, which opens a feedback use case as well.

The table pairs each core use case with a message type from the documentation and the trigger we recommend. The last column is the setting we would check before anything else.

Use caseMessage type fitTriggerCheck first
Push primingFullscreen or modalCustom eventWhether the device can still show the native prompt
Sales and promotionsModalSession start or purchasePriority against other messages
Feature adoptionModal or slideupCustom event or session startMinimum SDK versions for drag-and-drop messages
Highly personalised campaignsDepends on the offerSession startNetwork dependence of templated delivery

Slideup and custom HTML messages need the traditional editor. Fullscreen and modal messages are available in both editors. For most in-app messages, Braze says to use the drag-and-drop editor.

Which in-app messaging use cases should you launch first?

We recommend starting with push priming. The operating system shows the native push prompt only once per install, and iOS won't show it again after a denial. A promotion can be corrected next week, but a spent permission prompt can't be recovered.

Our suggestion for the order after that is feature adoption, then promotions, then personalised first screens. Feature adoption asks the least of the user and teaches you how your audience responds to the channel. Promotions come once priority rules are in place, and personalised screens come last because they depend on clean data and on the network at display time.

How do you set up a push primer that respects each device?

Braze describes the push primer as an in-app message that explains what users can expect before the native prompt appears. It also notes that you get one chance to ask for push permission. The documented steps are short:

  1. Build the message in a fullscreen or modal layout, so there is room for the copy and both buttons.
  2. Set the secondary "Not now" button to Close Message and the primary "Allow notifications" button to Request Push Permission.
  3. Schedule the message as action-based, with Perform Custom Event as the trigger action.
  4. Target users on any device that hasn't yet granted push permission, and add no extra push status filters.
  5. Ask your developers to remove any existing code that requests push permission, so users see one prompt.

Braze suggests waiting until a user has completed a high-value action, such as placing an order, before the primer appears. On Android 12 and earlier, Braze notes that primers aren't recommended because push is opted in by default.

What goes wrong with push primers when a user has several devices?

Braze captures user data at the profile level rather than the device level. A push filter can therefore describe the user while missing the device in front of them. Braze documents that a user-level filter such as Push Subscription Status is not Opted In excludes users already opted in on another device.

For example, a user opted in on an Android phone would never see the primer on a new iPhone. The documented answer is the no-code push primer with no extra push status filters.

The SDK checks the push permission state of the device that would show the message. It then decides whether to display or suppress the primer.

That suppression depends on the Request Push Permission button action. If a team builds the same flow with custom logic or a deep link, the SDK can't recognise it as a primer. The message then appears whatever the device's state.

When we review an existing primer campaign, a profile-level push filter is the first thing we look for. It is easy to add in good faith and hard to notice, because the campaign still delivers and still reports impressions.

Braze also documents a Liquid check for teams that want to withhold the primer from devices where notifications were explicitly switched off:

{% if targeted_device.${foreground_push_enabled} == false %}
{% abort_message('user turned off push notifications') %}
{% endif %}

targeted_device looks only at the device displaying the message. For a device that hasn't responded to a push permission state yet, the value is unset, so the check leaves it eligible.

How should promotions and feature announcements share a screen?

Only one in-app message can display per occurrence of a trigger event. If several campaigns share a trigger such as session start, the highest-priority message displays. The next chance for another comes at the next session.

Priority comes in high, medium and low buckets. Exact order within a bucket is set from the delivery settings.

A sale modal and a feature tour that both fire on session start will therefore take turns, one per session. We recommend giving the feature message its own custom event trigger and keeping session start for the promotion. A slideup suits low-urgency feature news, because Braze describes it as a format for short announcements that shouldn't block the rest of the screen.

How does personalisation change delivery?

Braze checks whether a user is in the target audience when the device downloads in-app messages, which usually happens at session start. The device stores eligible messages and displays each one when its trigger occurs, even later in the session. Users who become eligible mid-session receive the message at their next session start.

Messages become templated when Re-evaluate campaign eligibility before displaying is selected. They also become templated when the message uses certain Liquid tags, Connected Content among them.

A templated message needs an additional network request after the trigger. Braze says this can add a short delay, typically under 100 ms on a stable connection. If the device has no internet access, the message isn't delivered.

We recommend treating Connected Content in an in-app message as a trade: you gain fresh data and lose offline display. Use it where the data changes within a day, and leave it out where static copy does the same job.

What should in-app messages not be used for?

Braze recommends avoiding in-app messages, Content Cards, Banners and feature flags for critical, time-sensitive updates. They rely on device connectivity to sync. Our suggestion is to use the channel for messages that can wait for the user's next session.

Users see in-app messages only while they're active in the app, so Quiet Hours isn't available for this channel. Braze documents a Liquid time-window check that aborts a message outside the hours you set.

After a campaign is stopped, users who started a session before it stopped may still see the cached message when they perform the trigger event. Re-evaluate campaign eligibility before displaying checks eligibility again just before display, and it needs a network connection. Our suggestion is to plan a campaign's stop date with that cached window in mind.

Braze also sets a default capacity of 200 active, action-based in-app message campaigns per workspace. It notes that your workspace may have a different capacity.

How would a hypothetical retailer sequence these use cases?

Take a hypothetical retailer with an app and a website. It has no push permission history worth keeping and wants to build the programme from scratch. Nothing here describes client work, and no results are implied.

The retailer first ships a push primer, triggered by a custom event after a first order. That matches the timing Braze suggests. Next it adds a slideup announcing a new wishlist feature, triggered by a custom event rather than session start.

Then it adds a seasonal promotion modal on session start at high priority. Last, it adds a returning-customer greeting using Connected Content, and accepts that the greeting needs a network connection.

The decision that matters is the second one. Had the wishlist announcement shared the session start trigger with the promotion, it would appear only when the promotion lost priority. Moving it to its own trigger removes the contest without touching the promotion.

How do you measure each use case?

In-app messages don't use an Opens metric. Braze logs Impressions when the message becomes visible on screen and Clicks when users interact with the message body or buttons. Dismissing a message logs an impression but not a click.

For a push primer, we recommend reading the push opt-in that follows rather than clicks on the primary button. Braze suggests default conversion settings but notes you may want conversion events built around push primers. We would define that event before launch, so the first week of data answers the question you actually asked.

How does this connect to the rest of the programme?

Once the use cases are chosen, trigger rules decide what users see. Setting up in-app message triggers is the natural next read. Audience rules matter just as much, and segmenting users for targeted in-app messaging covers that side.

For creative direction, see creative in-app messaging ideas and how to create engaging in-app messages. Reporting is covered in measuring in-app message engagement, and the wider picture sits in in-app messaging for higher customer engagement.

What should you do next?

As a Braze implementation partner, CustomerIK recommends auditing any live push primer for profile-level push filters before building a new use case. Then launch in the order above, giving each message its own trigger wherever the trigger would otherwise be shared. Check the Braze documentation again before launch, because limits and behaviour can change.

Frequently Asked Questions

1. Do in-app messages work offline?

They can. Messages are delivered at session start, so a device that downloaded the payload before going offline can still display it. If the payload wasn't downloaded, the message doesn't display.

2. Can a user see two in-app messages in one session?

Yes, but only one per occurrence of a trigger event. For session start triggers that means one message per session, with the next opportunity at the following session.

3. Do in-app messages need push to be integrated?

No. In-app messages do not require push notifications to function in production, although test sends do need push on the test device.

4. Why are there no opens for in-app messages?

In-app messages do not use an Opens metric. Compare Impressions and Clicks instead.

5. Which editor should you use?

Braze recommends the drag-and-drop editor for most in-app messages. Use the traditional editor when you need slideup messages or custom HTML.

Sources

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

If you want a second pair of eyes on your push primer and trigger setup, 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.