.svg)
Mobile engagement use cases in Braze fall into jobs that push, in-app messages and Content Cards each do best. Push reaches users who've opted in and suits time-sensitive offers. In-app messages and Content Cards need no opt-in, but the Braze documentation advises against them for critical, time-sensitive updates, so this guide maps each use case to the channel the documentation assigns it.
Key Takeaways
- Push needs the user to grant permission on their device, while Content Cards don't require opt-in or permissions.
- In-app messages are permissionless and short-lived. Content Cards are permissionless and permanent.
- Braze recommends avoiding in-app messages and Content Cards for critical, time-sensitive updates.
- A popular pairing is a push, then the same content saved as a Content Card for anyone who didn't engage.
- Remove a card once the user completes the task it asked for.
- Braze's release notes list real-time updates for Content Cards, dated 15 Oct 2026, with the status ga.
What are the main mobile engagement use cases in Braze?
Braze documents use cases separately for push, in-app messages and Content Cards. The table puts them side by side, so you can see which job each channel is described as doing.
| Use case | Channel in the Braze documentation | What the documentation describes |
|---|---|---|
| Initial onboarding | Push | Urging users to finish first steps such as registering an account |
| First purchases | Push | Converting comfortable users into in-app purchasers |
| New features | Push | Bringing disengaged users back with something new |
| Time-sensitive offers | Push | Alerting users before an offer expires |
| Push priming | In-app message | Showing the benefit of opting in, then prompting for permission |
| Feature adoption | In-app message | Encouraging use of other parts of the app or a service |
| Personalised first screen | In-app message | Placing a message first when users enter the app or site |
| Sales and promotions | In-app message and Content Card | Static offers in a modal, or promotional inbox cards |
| Onboarding next steps | Content Card | An onboarding tab that holds outstanding tasks |
| Event attendance | Content Card | Homepage cards with location targeting |
| Recommendations | Content Card | Homepage or inbox cards driven by behaviour and preferences |
The Content Cards page adds one more option. If your use case isn't listed, you can set up key-value pairs and send the payloads to your app or website. The table is a starting set, not a boundary.
Which channel should carry which job?
Sort every use case by two properties: permission and lifespan. Users must grant push permission on their device. Content Cards don't require opt-in or permissions from your users.
The Content Cards page draws the lifespan line. In-app messages are permissionless and short-lived, while Content Cards are permissionless and permanent.
We recommend giving the interrupting moment to an in-app message, the standing reminder to a Content Card, and the reach outside a session to push. That's our rule of thumb, built on the documented properties rather than quoted from Braze.
Where does time-sensitivity change the answer?
Braze says Content Cards, in-app messages, Banners and feature flags rely on device connectivity to sync with Braze servers. It recommends avoiding these channels for critical, time-sensitive updates.
Push is described as the channel for an offer with a clock ticking. Braze says it's a great way to let users know about an offer before it expires.
Our suggestion is to plan every time-sensitive journey with push first. The in-app or Content Card version then acts as a second chance for people who open the app later.
How do the channels work together in one journey?
Braze names two pairings. A popular use case is sending a push notification, then saving it as a Content Card in your app for anyone who didn't engage with the push. Push priming runs the other way: a rich in-app message shows the benefit of opting in, then presents a prompt to grant push permission.
We recommend this sequence for a new user:
- Show a push priming in-app message at a natural moment, before the system prompt.
- Send push to those who granted permission, for the next step or first purchase.
- Save the same content as a Content Card for anyone who didn't engage.
- Remove the card once the user completes the task.
The last step comes from the documentation, which says not to forget to remove a card after a user completes the desired task. In our view, a card that outlives its job nudges people toward something they've already done. Give the removal rule an owner before launch.
What changed for Content Cards in October 2026?
Braze's release notes carry an entry dated 15 Oct 2026 titled "Real-time updates for Content Cards", with the status ga. It says Content Cards now reach a user's device as soon as they happen during a session, with no manual refresh required.
The SDK keeps a live connection open for the session, so Braze pushes updates to the device instead of waiting for the next session or refresh. Real-time delivery covers campaign eligibility, Canvas step entry, card removals and API-triggered sends. The entry also lists minimum SDK versions, so read it before you plan around the change.
The in-app message and Content Card pages still recommend avoiding these channels for critical, time-sensitive updates, as retrieved on 22 Oct 2026. Neither page says how that advice relates to real-time delivery. Until Braze says more, we'd keep the documented rule and treat real-time delivery as a freshness gain for card content.
Content Cards availability depends on your Braze package. Check yours before planning around cards.
What does a hypothetical worked example look like?
Take a hypothetical retailer app with three kinds of shopper: a new one, a lapsed one and a loyal one. This is an illustration, not client work, and it uses no figures.
For the new shopper, a push priming in-app message appears after the first useful moment. Once permission is granted, push covers the next onboarding step. A Content Card in an onboarding tab holds anything outstanding, and it's removed when the shopper finishes the task.
For the lapsed shopper, an expiring offer goes out as push first. Anyone who doesn't engage sees the same offer as a Content Card in the promotional inbox on their next visit.
For the loyal shopper, a homepage Content Card shows recommendations drawn from past purchases and browsing. Push stays off unless something is time-sensitive.
What should you check before sending push promotions?
The Braze push page says your push messages must follow the Apple App Store Review Guidelines and Google Play policies. Against Apple 4.5.4, it lists this: don't use push for promotions or direct marketing unless customers explicitly opt in via consent language in your app's UI and can opt out in the app.
This post doesn't settle the policy or legal question for your app. Read the current store guidelines and your own consent wording, and treat the Braze page as a pointer to them.
How does this connect to the rest of the programme?
Channel choice is one decision in a mobile programme. For the first-session flow, see onboarding new mobile users from first open and push notifications for onboarding completion.
For the in-app side, creating engaging in-app messages covers the message types, and deep links for mobile engagement covers where a tap should land.
To sequence these across steps, read automating mobile campaigns in Canvas. For send timing, see optimising push notification timing. For a rewards programme that used Content Cards for interactive gamification and feedback, see this case study on migrating and automating a multi-brand rewards programme.
Where should you start?
As a Braze implementation partner, we recommend starting with one journey. Use the new-user sequence above before you map every use case in the table.
It exercises all three channels and shows where card removal and permission handling need developer work. It also gives you a pattern to copy for the lapsed and loyal cases.
Frequently Asked Questions
1. Which channel is best for mobile engagement in Braze?
The documentation doesn't rank channels. It assigns jobs: push for time-sensitive calls to action, in-app messages for in-the-moment prompts, and Content Cards for permanent, permissionless content.
2. Do in-app messages and Content Cards need push permission?
No. The documentation says Content Cards don't require opt-in or permissions, and describes in-app messages as permissionless as well. Push does require the user to grant permission on their device.
3. Can I use Content Cards for time-sensitive offers?
The documentation recommends avoiding these channels for critical, time-sensitive updates. They rely on device connectivity to sync. Use push as the primary channel and a card as backup.
4. What is push priming?
It's a rich in-app message. It shows customers the benefit of opting in to push and then presents a prompt to grant permission. The in-app message comes first so the system request arrives with context.
5. Are Content Cards available on every Braze package?
The documentation says Content Cards availability depends on your Braze package. Ask your account manager or customer success manager to confirm yours.
Sources
- Braze, Content Cards. Retrieved 22 Oct 2026.
- Braze, In-app messages. Retrieved 22 Oct 2026.
- Braze, Push. Retrieved 22 Oct 2026.
- Braze, What's new in Braze. Retrieved 22 Oct 2026.
- Braze documentation changes. Check the pages above before you plan around a release status or package limit.
- Written by CustomerIK, a Braze implementation partner.
CustomerIK is a Braze implementation partner working across onboarding, technical integration, marketing operations and customer data management.
If you're deciding which Braze channel should carry which job in your mobile programme, let's talk.
.svg)
