Braze Email Trigger Strategies for Every Journey Stage

Two hands arranging three cards in an oak holder on a linen cloth, with the third card lifted out and edged in green, showing the trigger, exit and memory of a triggered email set one at a time.

Braze email trigger strategies pair each action-based trigger with three decisions: what should stop the send, whether the user can receive it again, and which frequency rules apply. This guide maps those decisions to welcome, activation, cart, post-purchase and engagement stages, then explains how to diagnose a triggered email that did not arrive.

Key Takeaways

  • Treat every triggered email as three decisions made together: the trigger, the exit and the memory.
  • An exception event only works when the message sends after a delay.
  • A user stopped by an exception event can qualify again at the next trigger, even without re-eligibility.
  • Campaign re-eligibility follows message receipt, while Canvas re-eligibility follows entry.
  • A frequency cap skips the send but does not remove the user from a Canvas.
  • When an email does not arrive, check the exception event, the cap and the receipt history before the trigger.

What are Braze email trigger strategies?

Action-based delivery sends a message after a user performs an event, instead of on a calendar. Braze describes these campaigns as effective for transactional or achievement-based messages.

As a Braze implementation partner, we treat every triggered email as three decisions made together: the trigger, the exit and the memory. The trigger says who qualifies, and the exit says what cancels the send.

The memory says whether the user can qualify again. The defaults are sensible, but a default cannot know which stage of the journey an email belongs to.

Which trigger fits which stage of the journey?

The table pairs each stage with a trigger, an exit and a memory setting. The stage pairings are our judgement, built on the documented trigger and exit options.

StageTriggerExit (exception event)Memory (re-eligibility)
WelcomeAdd an Email Address, or Perform Custom Event for registrationNone needed when sent immediatelyOff, so it sends once
Activation nudgePerform Custom Event for sign-upStart SessionOff, so it sends once
Cart reminderUpdate Cart, with property filtersPlace OrderOn, with a gap between sends
Post-purchasePlace OrderNoneOn, so each order sends
Engagement follow-upClick email on an earlier campaignA conversion eventOff, so it sends once per campaign

Every row depends on one rule: an exception event only works when the message sends after a delay. If the email goes out immediately, there is nothing to cancel.

How should you trigger welcome and activation emails?

A welcome email has an obvious trigger, but two details need care. The Add an Email Address trigger fires when an email address is added to a user profile, so you can filter on the address itself. If several profiles share one email address, the campaign may fire once for each profile.

For activation, Braze notes that staggering messages across the days after registration allows you to create a thorough onboarding process. A Canvas Delay step can extend up to two years (730 days), which leaves plenty of room for an activation nudge.

The exit matters more than the delay length. A nudge for users who have not started a session should be cancelled when they start one. Braze notes that you cannot make a session start both the trigger event and the exception event for a campaign.

We recommend building the welcome email as an immediate send, then putting the delay and exception logic on the second message. That way the first email never waits on anything.

How do you build a cart reminder that stops itself?

A cart reminder is the clearest case for an exception event. Braze describes adding an item to a cart as a great example of a campaign that benefits from one. If a user completes the trigger event but then completes the exception event before the message sends, they don't receive the campaign.

Property filters keep the trigger honest. Place Order and Update Cart accept property filters, so a trigger fires only for the orders or carts you want. Without a filter, every cart update is a candidate for a reminder.

There is a useful detail on the exit as well. A user stopped by an exception event can receive the campaign the next time they complete the trigger event, even if you have not elected for users to become re-eligible. The exit does not use up the user's one send.

What changes for post-purchase and transactional emails?

Braze notes that some campaigns, such as transactional messages, are ones you may want to always reach the user, even if they have already reached their frequency cap. You can override frequency capping for a campaign by toggling Frequency Capping to off when you schedule its delivery.

That toggle carries a responsibility, because an email that ignores caps removes a protection for the user. We recommend being strict about what qualifies. A shipping confirmation qualifies, while a cross-sell offer in the same message does not and belongs in a separate campaign that obeys the caps.

Our fuller walkthrough is in the guide to automating transactional emails with Braze.

Can opens and clicks trigger the next email?

Braze lists email interactions among its trigger events, and the list separates Click email from Open email. The open options are split further into machine opens and other opens.

Our view is that a follow-up decision should rest on a click rather than an open. The separate machine-open option is a reminder, in our view, that an open does not always mean a person read the email. We would use opens for monitoring and clicks for branching.

How do you stop a trigger email repeating?

By default, Braze sends a message to a user only once, even if they re-qualify multiple times. Re-eligibility has to be turned on separately. Three details decide whether your setting behaves the way you expect.

  1. For campaigns, re-eligibility is based on message receipt and not campaign entry. With re-eligibility on, a user who completed the trigger but did not actually receive the message qualifies automatically at the next trigger.
  2. For Canvas, re-eligibility is tied to entry rather than message receipt. A user who enters a Canvas and receives no message cannot re-enter unless re-eligibility is turned on.
  3. Re-eligibility is calculated in seconds, not calendar days, and the maximum time for a campaign is 720 days.

When a user re-enters a Canvas, the steps they received on the first pass are not visible to them, so they may receive the same message again. Braze suggests a User Update step that logs the send as a custom attribute, which you can then filter on.

How do frequency caps interact with triggered journeys?

Braze checks the cap when a campaign sends or a user reaches a Canvas Message step, before quiet hours. Global frequency capping alone doesn't exit users from a Canvas, so the user advances without the email.

Caps are calculated by calendar days in the user's time zone, not 24-hour periods. When rules conflict, the most restrictive applicable rule applies. Aborted messages do not count toward frequency capping.

A journey built on the assumption that every step sends can drift without any visible error. For a journey where one email carries the whole point of the Canvas, we recommend tagging the Canvas and reviewing the frequency rules for it before launch. A cap set for promotional volume should not thin out a lifecycle sequence unnoticed.

Why did a triggered email not send as expected?

Work through the causes in this order. Each one is documented on the Braze pages listed under Sources.

  1. The event arrived before the campaign launched. Users who completed the trigger event before the campaign launches don't qualify to receive it.
  2. The event timestamp was backdated. Braze uses the timestamp sent with the custom event to evaluate the delay, so a backdated timestamp may make the delay look already elapsed and the message send earlier than expected.
  3. A race condition on segment data. If the segment depends on an attribute set at the same moment as the event, Braze may evaluate membership before the change is processed. Braze suggests attaching the relevant data to the event as a custom event property and filtering on the property instead.
  4. The user left the audience during the delay. If the campaign is action-based and has a delay, the option to re-evaluate segment membership at send time keeps the audience current.
  5. An exception event, a cap or a previous receipt. Check the user profile for each before suspecting the trigger itself.

What does a joined-up journey look like in practice?

Take a hypothetical homeware retailer. A customer adds an email address at checkout, and the Add an Email Address trigger sends a welcome email at once. The retailer sets no exception event and leaves re-eligibility off.

Next, the customer adds a lamp to their cart and leaves. An Update Cart trigger with a property filter starts a reminder after a delay, with Place Order as the exception event. If the customer buys, the reminder is cancelled and the customer can receive it again at the next cart event.

The Place Order trigger then sends an order confirmation that overrides the marketing caps. The retailer tags the cart reminder and the welcome email as lifecycle, so the weekly cap still protects the customer from stacked promotions. Nothing here is client work or delivery data, and it only shows how the three decisions fit together.

How does this connect to the rest of the programme?

Triggers sit inside a wider system, so these guides cover the neighbouring decisions. If you are choosing between entry types, read action-based or API-triggered automation in Braze. For the welcome stage in a Canvas, see automating the onboarding journey in Braze Canvas.

Failure planning is covered in six email automation failure modes. Timing decisions for retention emails are in triggering retention messages at the right time. For behavioural signals beyond email, see setting up engagement triggers in Braze.

As a Braze Solutions Partner, CustomerIK recommends writing down the trigger, the exit and the memory for every email in a journey before building it. A one-line entry per email is enough, and it makes the review far quicker. If you want a second pair of eyes on that map, our Braze services page covers onboarding, technical integration and AI enablement.

Frequently Asked Questions

1. Can a Braze email trigger fire before the campaign is launched?

Users who completed the trigger event before the campaign launches don't qualify to receive the campaign.

2. Do I need to turn on re-eligibility for a cart reminder?

Not for a user who was stopped by the exception event, because that user can receive the campaign the next time they complete the trigger event. Turn it on if you want the reminder to reach the same user again after a completed send.

3. Does a frequency cap remove a user from a Canvas?

Global frequency capping alone doesn't exit users from a Canvas, so the user advances to the next step without receiving that email.

4. Can the same event be the trigger and the exception event?

Not for a session start: Braze states you cannot make it both the trigger event and the exception event for a campaign. For other events, Braze documents that a campaign whose trigger event matches the exception event is cancelled and rescheduled using the exception event's message delivery time.

5. Should transactional emails count towards frequency caps?

That is a configuration choice. Braze lets a campaign override frequency capping when you schedule its delivery, so decide it per campaign and keep the override for messages that must reach the user.

Sources

CustomerIK is a Braze implementation partner working across onboarding, technical integration, marketing operations and customer data management.

If you are mapping triggers, exits and re-eligibility for a journey you are about to build, let's talk.

Preferences

Privacy is important to us, so you have the option of disabling certain types of storage that may not be necessary for the basic functioning of the website. Blocking categories may impact your experience on the website.

Accept all cookies
Accept all cookies

These items are required to enable basic website functionality.

Always active

These items are used to deliver advertising that is more relevant to you and your interests.

These items allow the website to remember choices you make (such as your user name, language, or the region you are in) and provide enhanced, more personal features.

These items help the website operator understand how its website performs, how visitors interact with the site, and whether there may be technical issues.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.