Automated Triggers in Braze: Action-Based or API-Triggered?

A kitchen order rail with five slips, one green-clipped slip being lifted off before it is started, showing an exception event that cancels a delayed send.

Automated triggers in Braze start a message or a Canvas journey when something happens, not on a calendar date. You choose between an action-based campaign, an API-triggered campaign and Canvas entry. This guide shows how to choose, set one up, and avoid the failures that stop messages sending.

Key Takeaways

  • Choose the trigger route from where the event originates: Braze already records it, or your own systems send it.
  • Users who completed the trigger event before the campaign launches don't qualify to receive it.
  • You can add an exception event only if your triggered message sends after a time delay.
  • Send user data on the event as custom event properties, then use a property filter, to avoid a race condition with segments.
  • A backdated event timestamp may be treated as an elapsed delay, so send the current time.
  • For API-triggered campaigns, send_to_existing_only is true by default, so Braze creates no new profiles in that call.

What are automated triggers in Braze?

An automated trigger replaces the send date with an event. Braze documents the idea this way: "Instead of sending your campaign on certain days, you can trigger them to send after a user completes a certain event".

The event can come from the user, such as an app open, a purchase or a custom event. It can also come from your own systems through a server call. That difference decides which route you use.

Which trigger type should you choose?

Start from where the event originates. Use an action-based trigger when the user does something Braze already records. Use an API-triggered one when the event lives in a back-end system.

RouteWhat starts itWhere the rules liveCheck before launch
Action-based campaignA user completes a chosen event after launchCampaign settings in the dashboardEvents completed before launch don't qualify
API-triggered campaignYour server calls /campaigns/trigger/sendCopy and re-eligibility in the dashboardsend_to_existing_only is true by default
Action-based Canvas entryUsers take actions such as opening the app, purchasing or sending a custom eventEntry Audience windowHourly entrance limit applies every UTC hour
API-triggered Canvas entryYou add users with /canvas/trigger/sendEntry Audience windowEntry data goes in the context object when the dashboard shows Context Variables

With the API route, marketers "manage campaign copy, multivariate testing, and re-eligibility rules within the Braze dashboard". Delivery is triggered "from their own servers and systems". That split suits transactional messages, because engineers own the event and marketers own the message.

There is one naming trap. The documentation states that "An API-triggered campaign is different from an API campaign". Check which one a colleague means before you scope the work.

How do you set up an action-based trigger?

The campaign builder asks for six decisions in order. Treat each one as a rule you are writing, not a field you are filling in.

  1. Select a trigger event, such as a purchase, a session start or a custom event.
  2. Select a delay length, either immediately or after a delay.
  3. Select exception events that disqualify a user during the delay.
  4. Assign a duration with a start time and an optional end time.
  5. Select a time frame for the part of the day when sending is allowed.
  6. Determine re-eligibility, including any wait before a user can receive the campaign again.

Property filters make the first step sharper. Braze notes that Place Order and Update Cart "accept property filters, so a trigger fires only for the orders or carts you want".

Why does a triggered message sometimes not arrive?

Three causes are worth checking first. The first is that the user did the event too early. Braze is clear that users "who completed the trigger event before the campaign launches don't qualify".

A campaign that goes live at noon cannot reach someone who abandoned a cart at eleven. Check the launch time against the events you expect to catch.

The second cause is a delay that outlasts the window. If the delay is longer than the sending duration, "no users receive the campaign". Check the delay against the start time, end time and time frame together.

The third cause is the segment and the event racing each other. Braze warns that segmenting on user data recorded at the time of the event "may cause a race condition". Its fix is to attach the relevant user properties to the event as custom event properties.

You then apply a property filter instead of a segmentation filter. Our suggestion: test with a user whose attributes were set seconds before the event, because a long-settled test user hides the race.

How should you use delays and exception events?

A delay gives the user time to change their mind. An exception event is how you respect that. You can add one only if your triggered message sends after a time delay.

The documentation's own example is a cart reminder. The exception event is the user buying the products in their cart. A user who triggers the exception becomes eligible again the next time they complete the trigger event.

Timestamps deserve a separate warning. Braze evaluates the delay from the timestamp sent with the custom event, so a backdated timestamp may be treated as an elapsed delay. If events arrive through a batch job, stamp them with the current time.

When event data arrives late or malformed, look at how data enters the platform. CustomerIK's customer data management work covers designing the schemas and rules for how data enters, moves through and exits a business.

We recommend building the exception event before you tune the delay, because the delay length only makes sense once you know what can cancel the send. If the campaign has a delay, Braze also offers a setting to re-evaluate segment membership at send time.

How do you set up an API-triggered campaign?

You build the campaign in the dashboard and select API-Triggered Delivery. Then you call the endpoint from your own system. Message content can travel with the call in the trigger_properties object, and the message body can reference it.

{{api_trigger_properties.${your_property}}}

Braze is precise here: "Use exactly two curly braces per Liquid tag in trigger_properties and message copy". An extra brace is "a common cause of API-triggered personalization failures". Read your template again before you blame the payload.

Profile readiness is the other detail to plan for. By default, send_to_existing_only is true on the trigger endpoint, so Braze sends only to existing users and does not create new profiles in that call. If an email profile has no address yet, Braze retries for up to approximately 2 hours while it waits for profile data.

Including the email address in the same request avoids that wait. Check the current request reference before you build, because retry behaviour can change.

Re-eligibility needs a decision too. For a transactional campaign, Braze advises setting the delay to zero minutes so the user receives the message every time they transact. For promotional sends, limit repeats with re-eligibility settings.

How do triggers work at Canvas entry?

In Canvas, the trigger becomes the entry rule. With the action-based route, users enter when they take particular actions, such as opening the app, making a purchase or triggering a custom event. With the API route, users enter after you add them with the /canvas/trigger/send endpoint.

Entry controls then decide whether users can come back in. For both routes, an hourly entrance limit is applied every Coordinated Universal Time hour. That matters if you run campaigns across several time zones.

Interact with Canvas Step is not available as an action-based entry trigger. To chain journeys, use the Send to Destination Canvas component or a Braze-to-Braze webhook. Exit criteria follow the same logic as exception events: a user who matches them receives no further messages.

What does a trigger decision look like for a hypothetical retailer?

Take a hypothetical retailer that wants to remind shoppers about items left in a cart. This example is illustrative and carries no client data or results.

The event starts in the app, so the route is an action-based campaign, triggered by the cart update event. The retailer wants only carts above a set value. The value goes on the event as a property and the campaign filters on it, which avoids the segment race.

Next comes the delay, long enough that a shopper who is still browsing isn't interrupted. The exception event is the purchase, so anyone who buys during the delay never sees the reminder. Re-eligibility gets a wait of several days.

Last, the team checks the event timestamps. If cart events came from a nightly import, the delay could collapse and reminders could send early. The retailer would then switch to events stamped at the moment of the action.

How does this connect to the rest of the programme?

Triggers are one part of a wider automation design. Our guide to building an automated marketing workflow in Braze covers the surrounding structure. Setting up engagement triggers looks at behavioural signals in more depth.

Channel specifics sit in separate pieces. For messages inside the app, read how to set up in-app message triggers. For server-driven sends, read automating transactional emails.

Audience design shapes who a trigger reaches, so segmenting audiences for automated campaigns pairs well with this guide. When a journey grows beyond a single send, move to automating complex workflows in Braze Canvas.

For automated lifecycle work in practice, read our case study on migrating a multi-brand rewards programme. It covers how the team mapped its existing use cases before moving them.

What should you check before launch?

We recommend running these checks in this order, because each one depends on the one before it. Stop at the first one that fails.

  1. Confirm the event reaches Braze, and check its timestamp against the current time.
  2. Confirm the audience logic, preferring event properties over attributes set at the same moment.
  3. Confirm that the delay fits inside the duration and the time frame.
  4. Confirm the exception event and the re-eligibility wait.
  5. Send to a small internal audience before you widen it.

As a Braze implementation partner, CustomerIK recommends writing the trigger rule as one plain sentence before building. State the event, the audience, the delay, what cancels it and how often it repeats. If the sentence won't fit, the design isn't ready to build.

Frequently Asked Questions

1. What is the difference between an action-based and an API-triggered campaign?

An action-based campaign starts when a user completes an event Braze records. An API-triggered campaign starts when your server calls the trigger endpoint, while copy and re-eligibility stay in the dashboard.

2. Why did a backdated custom event send my message early?

Braze evaluates the delay from the timestamp sent with the event. If that timestamp is backdated, the delay may already count as elapsed, so send the current time.

3. Can I trigger in-app messages through the API?

According to the Braze documentation, only events sent through the SDK can trigger in-app messages. Events sent through the server-side api cannot.

4. How do I stop a triggered campaign from becoming repetitive?

Use the re-eligibility settings to add a wait before a user can receive the campaign again. Braze says this prevents triggered campaigns from becoming "spammy".

5. Does this guide settle consent or data protection questions?

Triggers can reach personal data, and consent rules vary by region. This guide does not settle any legal question, so route those through your own security and privacy review.

Sources

  • Braze, Action-based delivery. Retrieved 07 Nov 2026.
  • Braze, API-triggered delivery. Retrieved 07 Nov 2026.
  • Braze, Create a Canvas. Retrieved 07 Nov 2026.
  • Limits, defaults and retry windows are quoted from these pages on the retrieval date and can change, so check the current Braze documentation 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 want a second pair of eyes on your trigger rules before they go live, 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.