.svg)
Retention campaign mistakes in Braze usually come from assumptions about what a setting does. Exit rules, frequency caps, quiet hours and conversion windows each behave in a documented way that is easy to misread. This guide shows where those readings go wrong and how to configure each control so a retention journey behaves as planned.
Key Takeaways
- A user in a Delay step stays there until the delay ends, even after the exit event fires.
- Exit criteria can compare the exit event with the entry event, so a reminder stops only for the right purchase.
- Global frequency capping alone doesn't exit users from a Canvas, so capped users still advance through Message steps.
- In-app messages and Content Cards are not counted as or toward caps, and quiet hours release held messages all at once.
- Braze attributes conversions to the last Canvas Message step received, and the conversion window should at least match the longest path.
- We recommend auditing exit rules, caps and conversion windows together before launch.
Which retention campaign mistakes in Braze are worth fixing first?
Start with the controls that decide who stays in a journey and who gets measured. Exit criteria, frequency caps and conversion windows interact. An error in one distorts what you see in the others.
In our experience as a Braze implementation partner, journeys that look healthy in reporting often have exit rules and conversion windows set differently from what the team believes. The table lists the mistakes this guide covers, what Braze documents and the fix.
| Mistake | What Braze documents | Fix |
|---|---|---|
| Expecting an exit to be instant | A user in a Delay step stays there until the delay ends | Plan the delay length around the exit event |
| Exiting on any purchase | Exit criteria can compare the exit event with the entry event | Match the exit to the item or plan that triggered entry |
| Treating a frequency cap as a stop | Capped users still advance through Message steps | Decide what a skipped message should lead to |
| Counting every channel in the cap | In-app messages and Content Cards do not count toward caps | Review those channels separately |
| Ignoring the quiet hours queue | Held messages all send when the window closes | Stagger audiences or choose one timing control |
| Short conversion windows | Attribution runs to the last Message step received | Match the window to the longest path |
Why do users keep receiving messages after they have already returned?
The first mistake is expecting an exit to take effect the moment the event happens. Braze records the exit as soon as the event happens.
A user inside a Delay step, though, remains in that step until the delay period ends. They then leave the Canvas without advancing to later steps.
This matters in long lapse journeys. A Canvas with a long wait between nudges can hold a returned user for days.
Exception events apply while a user is in the Canvas, including when they're waiting in a step such as a Delay step, so the exit is still honoured. What changes is when your analytics show the user as fully gone.
How should exit criteria match the reason a user entered?
The second mistake is a generic exit event. Suppose a user enters because they selected one item or plan.
Exiting them on any purchase removes people who haven't done what the journey was about. Braze documents a better pattern: compare the exit event's property with the entry event's property.
In the Braze ticket example, a user who purchases the same ticket they originally selected exits the Canvas and stops receiving reminders. A user who buys a different ticket stays in the Canvas and keeps receiving follow-up messages about the original one.
For retention, the same pattern fits a renewal reminder that should stop only when the right policy renews. The Braze guide to matching exit criteria to entry events has the setup steps.
We would build the matching exit first and the message copy second. A reminder that outlives its purpose damages trust faster than a plain message does.
What does a frequency cap actually do inside a Canvas?
The third mistake is treating a frequency cap as a brake on the whole journey. Global frequency capping alone doesn't exit users from a Canvas. On Message steps, users still advance when a message isn't sent because of global frequency capping, in line with how users advance through the step.
A capped user therefore moves to the next step with no message and no pause. Aborted messages behave the same way for the journey.
Braze also notes that aborted messages do not count toward frequency capping. If a later step assumes the earlier message landed, the journey can say something that no longer makes sense.
The fix is a sequencing decision. Before launch, read each Message step as if the previous one had been skipped. Rewrite any step whose first line only works after a send.
Which sends fall outside your caps, and when is the cap checked?
The fourth mistake is a cap that looks complete but leaves gaps. You can add up to 10 rules per workspace, and the longest time frame is a maximum duration of 30 days. In-app messages and Content Cards are not counted as or toward caps on campaigns or Canvas components of any type.
Timing catches people out too. Global frequency capping uses the user's time zone and is calculated by calendar days, not 24-hour periods.
Braze checks the cap when a campaign sends or a user reaches a Canvas Message step, before quiet hours. If the user is already at cap, Braze skips the send and does not hold it for quiet hours.
Programmes that mix push and email with in-app messages should review in-app and Content Card volume alongside the cap rules. Those channels sit outside them.
How do quiet hours and Intelligent Timing change a retention send?
The fifth mistake is assuming quiet hours spread sends out. Braze holds the message and delivers it at the next available time after quiet hours end. If a large audience has messages held during quiet hours, all of those messages send at once when the window closes.
Quiet hours do not re-evaluate segment membership for a held send. Eligibility is decided when the message is triggered. Braze also recommends choosing quiet hours or Intelligent Timing, unless policy or compliance requirements make both necessary.
The Braze quiet hours page covers the behaviour in full. Our guide to how to trigger retention messages at the right time in Braze goes further on timing.
Why can a rate limit and a frequency cap send fewer messages than planned?
The sixth mistake is stacking the two controls without checking the order. Rate limit is applied first to select the initial pool of users who can receive messages.
The frequency cap then filters that pool. Braze does not backfill additional users from the rate limit once frequency capping removes users from the send pool.
A win-back send aimed at a fixed audience size can therefore land short. To reach a set number, raise the rate limit or use rate limiting alone, as the rate limiting and frequency capping page describes.
Priority between competing campaigns is a separate question, covered in our post on retention message prioritization. Braze lists Message Prioritization as an optional layer on top of frequency capping.
How should you set the conversion window for a retention Canvas?
The seventh mistake is leaving the conversion window at its default. If you don't select any conversion events during campaign creation, the time defaults to three days.
You can set a window of up to 30 days. Braze recommends a window that at least matches the longest path in the Canvas.
Attribution has its own rules. Braze attributes conversions that occur within the conversion deadline to the last Canvas Message step the user received. A user counts as converted if they performed the specific conversion event in the window, even if they did not open or click the message.
The primary conversion event is the first event you add. Braze uses it to select the best-performing message variation in multivariate campaigns or Canvases.
Because the primary event picks winners, we choose it for the behaviour that defines a retained customer. Opens and clicks stay as supporting signals. Our guide to retention metrics every marketer should track in Braze covers which signals to pair with it.
What do delay settings do to a lapse journey?
The eighth mistake is misreading how a Delay step counts time. A "day" is 24 hours and is calculated from the time the user enters the Delay step. If a time isn't specified, the user is delayed until midnight the next day in company time.
Calendar dates carry a sharper risk. If the selected date and time have already passed by the time users proceed to the Delay step, users exit the Canvas.
A lapse journey tied to a fixed date can drop people without any message. Check the Braze Delay step documentation before you rely on a calendar date.
What does a corrected lapse Canvas look like in practice?
Take a hypothetical subscription app with a three-step lapse Canvas for subscribers who stop opening the app. This is an illustration. It is not client work and it uses no data.
The team first sets the exit event to the renewal of the plan that triggered entry. A plan upgrade then leaves the journey running, and a renewal ends it. Next they read each Message step as if the one before had been skipped, and rewrite the second step so its first line stands alone.
They set the conversion window to cover the full path, with session start as the primary event. Only then do they write the copy.
- Set the exit event and match it to the entry property.
- Read every step as if the previous message was skipped.
- Set the conversion window to the longest path and pick the primary event.
- Review channels that sit outside the caps.
- Choose quiet hours or Intelligent Timing, unless a policy needs both.
How does this connect to the rest of the programme?
These checks sit inside a wider retention programme. Segment choices decide who enters in the first place, which our guide to using segmentation for smarter retention campaigns in Braze covers.
For lapsed users, see how to build effective win-back campaigns in Braze. For the automation view, read reducing churn with retention automation tactics in Braze.
For a worked programme on the same theme, CustomerIK has a case study on using interactive rewards to re-engage lapsing users that shows how that work was approached.
As a Braze implementation partner, CustomerIK recommends auditing exit criteria, cap rules and conversion windows together before launching any retention Canvas. The three interact, so a review of one alone will miss the others.
This post does not settle any consent or data protection question for your market. Take those to your own legal and security teams.
Frequently Asked Questions
1. Does an exit event remove a user from a Delay step straight away?
Braze marks the user to exit as soon as the event happens. They stay in the Delay step until the delay ends and do not advance to later steps afterwards.
2. Do capped users leave a Canvas?
Global frequency capping alone doesn't exit users from a Canvas. On Message steps they still advance when a message isn't sent because of the cap.
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. How long can a conversion window be?
You can set a window of up to 30 days. If you set no conversion events, the time defaults to three days.
5. Should I use quiet hours with Intelligent Timing?
Braze recommends choosing one or the other, unless policy, compliance or other requirements make quiet hours necessary alongside Intelligent Timing.
Sources
- Braze, Exit criteria. Retrieved 02 Nov 2026.
- Braze, Matching exit criteria to entry events. Retrieved 02 Nov 2026.
- Braze, Rate limiting and frequency capping. Retrieved 02 Nov 2026.
- Braze, Quiet hours. Retrieved 02 Nov 2026.
- Braze, Conversion events. Retrieved 02 Nov 2026.
- Braze, Delay. Retrieved 02 Nov 2026.
- Braze, Release notes. Retrieved 02 Nov 2026.
- 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 retention journeys need a review of exit rules, caps and conversion windows, let's talk.
.svg)
