
Braze documents four push notification use cases: onboarding, first purchases, new features and time-sensitive offers. Reach decides which one to build first, because a push can only land on a device that has granted permission. This guide sets out the permission, audience and trigger work that comes before each use case, and a build order from a Braze implementation partner.
Key Takeaways
- Braze documents four push use cases: onboarding, first purchases, new features and time-sensitive offers.
- The permission prompt can be displayed only once per install, so the permission flow is the first build.
- Braze suggests asking after a high-value action, using an action-based in-app primer.
- Apple's guidelines say promotional push needs explicit opt-in through consent language in the app.
- Braze logs a Send on dispatch, so read delivery and opens separately.
- Conversion events can count for up to a 30-day window, so agree the window before launch.
What are the main Braze push notification use cases?
The Braze push documentation lists four use cases. Onboarding pushes urge people to finish early steps such as registering an account. First-purchase pushes help comfortable users become in-app purchasers.
Feature pushes bring disengaged users back, and time-sensitive pushes warn people before an offer expires. The docs also give a game example: a push that warns a player their daily streak is at risk.
| Use case | What Braze documents | What has to exist first |
|---|---|---|
| Initial onboarding | Urging users to complete early steps such as registering an account | A registration event the app reports, and a way to ask for permission |
| First purchases | Converting users who are comfortable in the app into purchasers | A purchase event that ends the journey |
| New features | Notifying disengaged users about features that might attract them back | A lapsed segment that still has reachable devices |
| Time-sensitive offers | Telling users before an offer expires | An expiry the message can state, and a rule for repeats |
The list tells you what push is good for. It doesn't tell you which to build first, and that ordering is our judgement.
Why does reach come before any use case?
Braze tells teams they get one chance to ask users for push permission. The operating system enforces it: the prompt can be displayed only once per install.
On Android 13 and later, a user who denies the prompt twice is blocked from further prompts, including Braze primer messages. A use case aimed at devices that can't receive it looks finished in the Canvas builder and does nothing in the field.
So the first thing we build is the permission flow, and the first campaign comes after it. Every use case in the table depends on it.
When should the push primer appear, and who should see it?
Braze suggests waiting until a user completes a high-value action, or until there's a compelling need push can address. Its own example is offering shipping tracking after an order. The primer is an in-app message scheduled as an action-based message with a custom event as the trigger.
- Choose the event that shows a user has seen value, such as a first order.
- Build the primer as an in-app message whose primary button uses the Request Push Permission behaviour.
- Schedule it as an action-based message triggered by that custom event.
- Leave push subscription filters out of the audience and let the no-code primer do the suppression.
The last step matters for people with more than one device. Braze notes that a user-level filter such as Push Subscription Status is not Opted In excludes users already opted in on another device, so they never get the prompt on the new one. Braze recommends the no-code push primer for this reason.
How should an onboarding push be built?
Braze describes the purpose plainly: until users take the first steps, their value is severely limited. Push can urge them to complete those steps. Onboarding runs over several messages, and Braze positions Canvases for multi-step journeys and campaigns for single targeted messages.
Write the exit condition before the first message. If the registration event ends the journey, nobody who has already registered gets a reminder to register. Remember that audience rules are checked first and the trigger second: Braze describes the target audience as a waiting room, and only users already inside can move forward when the action happens.
How do first-purchase and time-sensitive pushes differ?
A first-purchase push is a one-shot. It helps a comfortable user convert, and the purchase event should end it. A time-sensitive push has a different shape, because the message depends on a clock.
Braze says push is a great way to tell users about an offer before it expires. The streak example from the docs shows a third shape, a message that can repeat. Braze lets you choose delivery by schedule, by action or by API trigger.
Braze also exposes delivery controls such as re-eligibility and frequency capping rules. Decide the repeat rule for each use case separately. The first-purchase push should never repeat after a purchase, and the streak push may repeat daily, so it needs a cap before it goes live.
What do Apple's guidelines mean for use case choice?
Apple's App Review Guidelines, section 4.5.4, say push notifications must not be required for the app to function and should not carry sensitive personal or confidential information. They also say push shouldn't be used for promotions or direct marketing unless customers have opted in through consent language in the app and have a way to opt out.
That makes the promotional use cases the ones to check first. We keep service pushes, such as order tracking, in separate segments from promotional pushes, so the consent basis of each audience is easy to read. This post doesn't settle the policy or legal question, so check the current guidelines and take advice for your own app.
How do push use cases fit into multichannel journeys?
By default, Braze sends a push to all devices with a valid push token. You can narrow it to the last-used device, but Braze is clear that the label is a technical status. It follows the device with the latest updated push token, whichever device had the latest session.
For a time-sensitive offer, one device may be enough. For a purchase confirmation, all devices may be right. Decide the device rule and the opted-in rule for each use case before launch.
Braze also documents a multichannel setting for opted-in users only: a user who is subscribed to email and push enabled still receives the push but not the email. Check that setting when a use case pairs email with push.
What does the build order look like for a hypothetical app?
Imagine a subscription meal-kit app with a registration step, a first-order event and a weekly menu. The team wants all four use cases. The Braze list starts with onboarding, but at registration nobody has granted permission yet, so a registration push has no audience.
We would build in this order. First, the primer, triggered by the first order, so the permission prompt arrives when the app has just proved useful. Second, a post-order tracking push for the users who accept.
Third, a feature push to lapsed users who are still reachable. Last, a time-sensitive menu offer with a repeat rule and an expiry. Onboarding for unregistered users stays on email and in-app messaging until push can reach them.
This is a hypothetical scenario. It isn't client work and it isn't a measured result.
How do you tell whether a use case is working?
This post states no results. The Braze pages we read describe what each use case is for and give no achieved results, and we have no shareable delivery data. Treat any uplift figure you see for push use cases with caution until you can trace it to a primary source.
Set the measurement before launch. Braze lets conversion events count for up to a 30-day window, so agree the window and the event first. Read a Send as a dispatch record: Braze logs a Send once the message goes toward Apple, Google or your web push service, and delivered, opens, bounces and uninstall signals are tracked separately and may arrive later.
How does this connect to the rest of the programme?
Push use cases sit on top of segmentation, triggers and measurement, and we have written about each. For audience rules, see push notification segmentation. For the trigger mechanics, see triggered push notifications.
The first use case on the Braze list, onboarding, is covered in push notifications for onboarding completion. Channel pairing is covered in multichannel engagement campaigns. To read results, see push notification analytics and A/B testing push notifications.
As a Braze implementation partner, CustomerIK recommends building the permission flow first, then one use case with a written exit rule, and measuring it before adding the next.
Frequently Asked Questions
1. Which Braze push notification use case should come first?
The one whose audience can already receive push. In practice that means the permission flow, then a post-action message for users who accepted.
2. Does Braze publish results for these use cases?
The pages we read describe the purpose of each use case and give no rates. This post states none and we have no shareable delivery data.
3. Can I send promotional push without extra consent?
Apple's guidelines say promotional push needs explicit opt-in through consent language in the app, with a way to opt out. This post doesn't settle the legal question.
4. What happens if an Android 13 user denies permission twice?
Android blocks further prompts, including Braze primer messages. The user then has to enable push in device settings.
5. Is a logged Send the same as a delivered push?
No. Braze logs a Send on dispatch, and delivery and open signals are tracked separately and may arrive later.
Sources
- Braze, Push. Retrieved 10 Nov 2026.
- Braze, Push primer in-app messages. Retrieved 10 Nov 2026.
- Braze, Create a push message. Retrieved 10 Nov 2026.
- Apple, App Review Guidelines. Retrieved 10 Nov 2026.
- This post rests on three Braze documentation pages and Apple's published guidelines as retrieved on the date shown, so check the live pages before you build.
- 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 push use case to build first, let's talk.




