
Boosting app retention in Braze means joining three documented jobs: measuring who comes back with the retention report, reaching lapsed users with the lapsed user Canvas template, and limiting message volume with frequency capping. We recommend agreeing the retention event, the control group and the cap before building any win-back message, so every result can be read against a baseline.
Key Takeaways
- The Braze retention report measures whether users performed your chosen retention event within 30 days of receiving a campaign or Canvas.
- The control group's retention data shows what retention looks like without a message, so compare against it before crediting a campaign.
- The lapsed user template targets users who haven't used the app in over 30 days and sends only to users who have opted in.
- In-app messages and Content Cards are not counted toward frequency caps, so a push cap says nothing about them.
- A frequency-capped Canvas user advances to the next step with no send event, so progress through a Canvas is not proof of delivery.
- We recommend fixing the retention event, the control group and the cap before the first win-back message is built.
How do you boost app retention with Braze mobile campaigns?
Braze documents three parts that matter for retention. The retention report shows whether users came back, the lapsed user Canvas template reaches people who have stopped opening the app, and frequency capping controls how often anyone is messaged. Each page makes sense alone, and none sets out a combined order.
We recommend setting them up in a fixed order. Choose the behaviour that counts as coming back, then define the lapsed audience, then set the cap. The sections below follow that order.
What does a Braze retention report measure?
Braze lets you measure retention on the Analytics page of a campaign or Canvas. Campaign retention is the rate at which users who received the campaign performed a retention event that you specify. The window is the 30 days from the time they received it, and Canvas retention works the same way.
Two details change how you plan. Retention reports aren't available for API-triggered campaigns, so check how a send is triggered before you promise anyone this report. A user who received the campaign or Canvas in more than one cohort is counted twice in the report summary row.
| Report behaviour | What the documentation says |
|---|---|
| Measurement window | Retention event within 30 days of receiving the message |
| API-triggered campaigns | Retention reports aren't available |
| Users in several cohorts | Results are counted twice in the summary row |
| Re-running a report | Not with the same retention event for 24 hours |
| No-message baseline | The control group's retention data can be viewed |
Why does the control group matter more than the headline rate?
A headline retention rate alone can't separate returns you caused from returns that would have happened anyway. The report page offers a fix: you can see what retention looks like if you didn't send a message by digging into the control group's retention data. Compare the two before crediting the campaign.
Lapsed users can return for reasons unrelated to your message, such as a new release or a change in routine. We suggest reading every result against the control group for that reason.
The same page suggests asking where the impact starts to decline. That can signal that a new campaign or Canvas is needed as another boost to retention. We read that as a sequencing cue: the point where the lift fades is where the next step of your programme belongs.
How does the lapsed user template define a lapsed user?
The Braze lapsed user template targets users who haven't used your app in over 30 days by default. Its default entry controls let users re-enter the Canvas after four weeks, so someone who lapses again can be picked up again. The template also says to send only to users who have subscribed or opted into receiving messages or notifications.
That last rule means the win-back audience can be smaller than the lapsed list, so plan reach on the opted-in count. We also recommend matching the retention event to the behaviour that ends the lapse. If the audience rule treats a user as lapsed until they open the app but the report counts a purchase as coming back, the two disagree about success.
How should you cap a win-back push without losing the message?
The template says to apply your frequency capping rules so that you don't overwhelm your audience. Its example limits campaigns or Canvas steps tagged Lapsing/Retention to two every week. Braze gives the reason: if a user receives too many messages within a short time period, they will feel over-encumbered and either turn off push notifications or uninstall your app.
Quiet hours add a wrinkle. The template suggests selecting Send at next available time so that users don't miss out on promotions. Braze checks the cap when a campaign sends or a user reaches a Canvas Message step, before quiet hours, and it checks again at the delayed send.
Caps are calculated by calendar days in the user's time zone, not 24-hour periods. We suggest testing the cap against your own send times, because a held message meets the cap a second time. Each workspace can have up to 10 frequency capping rules joined by the AND operator, with a time frame of up to 30 days.
What do frequency caps count, and what do they skip?
Not every message type counts toward a cap, so check the table before you set the number.
| Item | What Braze documents |
|---|---|
| In-app messages | Not counted toward caps |
| Content Cards | Not counted toward caps |
| Push to a user with several devices | Counted as one send, however many devices receive it |
| Aborted messages | Not counted toward caps |
| Canvas user who is capped | Advances to the next step, with no send event |
In-app message rules are sent down to an app on session start. Braze can therefore send a message to the user before the cap is hit, but by the time the user triggers it the cap has been hit. We read that as a limit on reach: an in-app message can only reach a lapsed user after they've returned, so a cap on a win-back is mostly a cap on push and email.
Braze also lists Message Prioritization, an optional layer on top of frequency capping, as generally available in a release entry dated 15 Oct 2026. Check the release notes before relying on it, since release status can change.
What does a hypothetical win-back walk-through look like?
Take a hypothetical retailer with a shopping app that wants to win back users who haven't opened it in over 30 days. This is an illustration of sequence only, with no client data and no outcome.
- Choose the retention event first. Pick starting a session, the same behaviour that ends a lapse.
- Build the Canvas from the lapsed user template. Keep the entry audience of users inactive for over 30 days and the four-week re-entry.
- Keep a control group, so the report can show retention without a message.
- Tag the Canvas for lapsing and retention, and cap that tag at two a week. Select Send at next available time for quiet hours.
- Send only to users who have subscribed or opted into receiving messages or notifications.
- Run the retention report once the first cohort's window has passed. Compare the Canvas against the control group, then look for the day the lift fades.
The retailer writes the event down in step one because the report can be re-run with a different event. That flexibility helps exploration but is risky for reporting.
Which mistakes break the retention loop?
The first is choosing the retention event after the results are in. Braze lets you change the event and re-run the report, so it's tempting to keep trying events until one flatters the campaign. A pre-agreed event stops that.
The second is assuming in-app messages and Content Cards are capped. They aren't counted toward caps, so a push cap of two a week says nothing about how many in-app messages a returning user sees.
The third is reading a capped Canvas step as a delivered one. A capped user advances without a send event, so a Canvas can show people progressing through a win-back that never messaged them. To identify these users, you can use Currents to track message frequency capped events.
How does this connect to the rest of the programme?
Retention work sits inside a wider lifecycle. For the metric side, see Retention Metrics Every Marketer Should Track in Braze. For the win-back mechanics, see How to Build Effective Win-Back Campaigns in Braze.
Planning errors are covered in Retention Campaign Mistakes to Avoid in Braze Canvas. Canvas build detail is in How to Automate Mobile Campaigns in Braze Canvas. For message content, see How to Personalize Retention Messaging in Braze, and for timing, see How to Trigger Retention Messages at the Right Time in Braze.
For a retail example of re-engaging lapsing users with interactive rewards inside automated lifecycle messaging, see the case study Implementing Interactive Gamification to Re-Engage Lapsing Users and Boost Conversions. If you want churn modelling and lifetime value forecasting beside the retention report, see Marketing Analytics, the CustomerIK service that covers both.
Frequently Asked Questions
1. What is a retention event in Braze?
It is the event you specify on the retention report, such as starting a session, that counts a user as having come back.
2. Can I run a retention report on an API-triggered campaign?
Braze documents that retention reports aren't available for API-triggered campaigns.
3. Do in-app messages count toward frequency caps?
In-app messages and Content Cards are not counted as or toward caps on campaigns or Canvas components of any type.
4. Does a frequency cap remove a user from a Canvas?
A capped user stays in the Canvas. The user immediately advances to the next step, and Braze generates no send event for that step.
5. Can I re-run a retention report straight away?
Not with the same retention event. Braze documents a wait of 24 hours, though you can change the event and re-run the report.
Sources
- Braze, Retention reports. Retrieved 06 Nov 2026.
- Braze, Lapsed user (Canvas template). Retrieved 06 Nov 2026.
- Braze, Rate limiting and frequency capping. Retrieved 06 Nov 2026.
- Braze, Release notes. Retrieved 06 Nov 2026. The Message Prioritization entry was read from the release notes index only.
- Limits and defaults in this post describe Braze documentation on the retrieval date and can change, so check the 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 are planning a win-back Canvas and want the retention event, control group and frequency cap agreed before the build, let's talk.




