
Push notifications in multichannel campaigns in Braze work when every channel has a defined job and a defined audience rule. Choose between a campaign and a Canvas, set how opt-in states are handled, and decide which devices receive the push. Then sequence the channels with delays and frequency controls so the same message never lands twice.
Key Takeaways
- Braze documentation says campaigns suit single, targeted sends and Canvases suit multi-step user journeys.
- Each channel checks its own eligibility, so one user can receive the push and not the email.
- With the opted-in-only setting, Target Audiences filters should not limit the audience to a single channel.
- Narrowing push to one device picks the newest push token, and the push does not send if that device is not push enabled.
- A user can advance through a message step without a send, because a frequency capped or unreachable user still moves on.
- We recommend building audience rules and frequency controls before the creative.
Should push notifications in multichannel campaigns in Braze be a campaign or a Canvas?
Braze documentation draws the line clearly. Campaigns suit single, targeted sends, while Canvases suit multi-step user journeys. When a campaign needs more than one channel, you select Multichannel at creation.
As a rule of thumb, we ask one thing first: whether the second message depends on what happened to the first. If it does, build a Canvas. If both channels go out together with no dependency, a multichannel campaign is simpler to maintain.
How do opt-in states decide who gets push and who gets email?
Braze documents a three-user example for email plus push, under the opted-in-only setting described below. Each channel checks its own eligibility, so outcomes differ by user.
| User | Email status | Push status | Documented result |
|---|---|---|---|
| A | Subscribed | Push enabled | Receives the push, not the email |
| B | Opted in | Not push enabled | Receives the email, not the push |
| C | Opted in | Push enabled | Receives both |
To send email only to explicitly opted-in users, you choose "opted-in users only" under Audience Summary. Braze then sends the push to users who are push enabled by default. With this configuration, the documentation says not to add any Target Audiences filter that limits the audience to a single channel, such as Foreground Push Enabled = True or Email Subscription = Opted-In.
The failure we would plan for is inheritance. A segment built years ago for an email-only programme often carries a channel filter nobody remembers, so check every segment you reuse before the first test send. If channel and consent data sit in different systems, CustomerIK's customer data management service covers identity resolution, CDP integration and data governance.
Which devices receive the push in a multichannel send?
By default, Braze sends a push to all devices with a valid push token when a user has your app on several. You can narrow this to a single device. The device chosen is the one with the newest push token, which can differ from the one used in the latest session.
If the device holding the newest token is not push enabled, the documentation says the message does not send. In a multichannel journey this matters more than in a push-only one, because the email may still go out while the push does not.
For time-sensitive pushes we would leave the destination on all devices and control repetition through frequency rules instead. Narrowing to one device trades reach for fewer duplicates, and that trade is easy to make without noticing.
How should you sequence push and the other channels?
The documentation describes the mechanics of a Canvas and does not prescribe an order. The order below is our working method.
- Write one sentence for each channel describing its job. Push carries the prompt, email carries the detail.
- Send the push first when the message has a short useful life, and let a delay step give the user time to act.
- Gate the follow-up with a decision or delivery check, so users who already converted exit the journey.
- Send the email only to users who still qualify, with different content from the push.
We put push first because it is the channel a user is likelier to see within minutes, and because it makes a cheap first attempt before a heavier email. That is judgement, not a documented rule, and your own tests should overrule it.
Delay steps need care with units. A day is 24 hours from the moment the user enters the Delay step, while a calendar day waits until the next specified time, which could be less than 24 hours. You can also delay at company time or at a user's local time.
What do Canvas delivery settings add to a message step?
A message step adds a standalone message wherever you want it in your Canvas. Its delivery settings cover Intelligent Delivery, Quiet Hours overrides and delivery validation. Braze recommends enabling Intelligent Timing and rate limiting as an additional check on any delay between a user entering the step and the message sending.
Delivery validations confirm at send time that the audience still meets your criteria. If a user fails them, you choose whether they exit the Canvas or advance to the next step. For a push-then-email journey this is the cleanest way to stop an email going to someone who already converted.
Why can a user advance without receiving the message?
Users advance through a message step in several cases, and a send is only one of them. Two documented conditions matter here. One is a message that is frequency capped and not sent, and the other is a user who is not reachable by channel.
The consequence is a named failure mode we see when reviewing journeys. A follow-up step can assume the push was delivered when it never was. Treat reaching the next step as progress only, and add a separate check if the next message needs a delivered push.
How do you keep push and email from stacking up?
Braze states the risk plainly: a user who receives too many messages in a short time may turn off push notifications or uninstall your app. Frequency capping and the Last Received filters give you the controls. Appending the Last Received Push filter to every targeted segment would cap users at one push every 24 hours.
For multichannel campaigns, the maximum user cap has a detail that is easy to miss. Braze first selects one audience up to the cap, then evaluates each user in that audience for each channel. The capped audience stays the same size, while sends per channel can differ with eligibility.
What does this look like for a hypothetical retailer?
Take a hypothetical subscription retailer that wants to recover started-but-abandoned checkouts. This is an illustration, not client work, and it uses no figures. The journey starts with a Canvas, because the email depends on what the push achieved.
The audience rule comes first. The team removes any inherited single-channel filter, then lets push-enabled users receive the push and opted-in users receive the email. A delay gives the shopper time to return.
A delivery validation removes anyone who has since purchased, and the email goes only to the remainder with different content. Frequency rules sit across the whole programme, so a shopper who already had a message today skips the journey rather than receiving a third nudge.
The design choice worth copying is the order of decisions: audience rule, then delay, then validation, then the second channel. Each step removes people before the more expensive message goes out.
Which mistakes break push-led multichannel journeys?
We see the same four mistakes when a push channel is added to an existing programme.
- Reusing a segment that still carries a single-channel filter, which shrinks the audience without any warning.
- Sending identical copy on push and email, so the second message adds nothing.
- Assuming a step means the push was delivered, as covered above.
- Setting no cross-channel frequency rule, so each team caps only its own channel.
How do you measure whether the combination works?
Set conversion events deliberately. Braze allows a window of up to 30 days in which a conversion counts if the user takes the specified action. Choose a window that fits the journey, and avoid taking the longest by default.
Message step analytics include Unique Recipients, the number of users who received messages from that step. Compare channels by recipients rather than raw sends. Read the push step and the email step side by side before judging the journey.
How does this connect to the rest of the programme?
Push is one channel in a wider design, so start with building multichannel engagement campaigns in Braze and the cross-channel customer journeys guide. Audience quality decides how well any of this works, which is covered in push notification segmentation.
Timing and triggers come next. See optimising push notification timing and triggered push notification setup. For choosing which job each channel should do, read mobile engagement use cases in Braze.
For a view of a fallback sequence across channels, see a CustomerIK case study on unifying guest profiles for a multi-property hospitality business. It covers consolidating booking, tier, language and consent data and building Canvas journeys with an automated fallback sequence.
The Braze reference for building the message itself is Create a push message. As a Braze implementation partner, CustomerIK recommends building the audience rules and frequency controls before the creative. A well-written push on a mis-filtered audience still underperforms, and the fix is cheaper before launch than after.
Frequently Asked Questions
1. Can one Braze campaign send push and email together?
Braze documentation says to select Multichannel when a campaign targets multiple channels. Each channel still checks its own eligibility, so a user can receive one channel and not the other.
2. What happens to a user who is not push enabled?
Braze documents an example where such a user, opted in to email, receives the email and not the push.
3. Does narrowing push to one device remove duplicate sends?
It limits sends within a platform, and the device chosen is the one with the newest push token. Braze documents that campaigns targeting several platforms can still send to each.
4. Should the push or the email go first?
The Braze pages we reviewed describe the mechanics and do not prescribe an order. Our view is that push goes first for short-lived messages, with a delay and a delivery check before the email, but you should test it.
5. Does this post settle consent questions?
It does not. It describes documented Braze behaviour only and states no legal conclusion on consent or lawful basis for push or email.
Sources
- Braze, Create a push message. Retrieved 15 Nov 2026.
- Braze, Message step. Retrieved 15 Nov 2026.
- Braze, Rate limiting and frequency capping. Retrieved 15 Nov 2026.
- Braze, Delay. Retrieved 15 Nov 2026.
- The sequencing advice, failure modes and worked example are CustomerIK judgement, not Braze documentation.
- 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 your push and email programme needs its audience rules and frequency controls reviewed before the next launch, let's talk.




