Braze Campaigns, Delivery Types: API-Triggered
What is this mysterious “API-Triggered” option?
Why don’t I have any edit options?
Watch the video below to find out!
🗣️ WATCH FULL YOUTUBE VIDEO HERE 🗣
🧑🏻🏫 Braze API-Triggered Delivery/Entry 🧑🏻🏫
[Braze-mas 2023, Day 19]
What’s up everyone, my name is Allan, Founder and Consultant at For Now Marketing, and welcome to Day 19 of Braze-mas 2023!
Before we get started, if you have any questions, whether you are currently using Braze or considering using Braze, please feel free to reach out! You can find these addresses and more in the Youtube description below.
API-Triggered
Today, we are going over the 3rd option for Action-Based Campaigns: API-Triggered. This option doesn’t get as much love as the other two options, but there are plenty of use cases for this option.
Let’s get started!
API-Triggered: Use Case
So far, we’ve gone over two other types of Campaign Delivery Types. First, we talked about the classic, traditional Scheduled send where you set the exact date and time that the message will be sent.
Next, we talked about the Action-Based option where the message is sent based on an action that the user performed.
Finally, API-Triggered, many times also called the server-triggered, is when the brand wants to decide when the message gets sent out.
Maybe your users can submit an application on your app or website, and you want to send an email to your users when the application has been reviewed.
There’s no set time when the application gets reviewed, so we can’t use Scheduled.
Also, the application review is out of the user’s control, so we can’t use Action-Based.
In our case, API-Triggered would be perfect, because then, the brand can set up the logic to trigger the message from the backend, once the application has been reviewed.
So we set up the Campaign in the Braze dashboard, just like any other Campaigns.
Then, we launch and provide the Campaign ID to our Engineering team.
Lastly, they implement the logic in the backend that will decide when this Campaign will get triggered.
Additional Features
Unfortunately, with the API-Triggered option, we don’t really get the option to add any of the additional features we discussed yesterday, like Quiet Hours or Campaign Duration.
However, API-Triggered messages are often used for Transactional Messages, so from my experience, I’ve had no issues without these missing features, and if these features are absolutely necessary, then the Engineering team may be able to implement some of that custom logic for the Marketing team.
API-Triggered Canvas
One last note on today’s topic: Canvases have the exact same Entry Type called API-Triggered, and there’s really no difference at all between how API-Triggered works for Campaigns vs Canvases. Of course, for Canvases, the API-Triggered Entry determines when the users will enter the Canvas, not when they’ll receive messages.
Thank you!
That’s it for Day 19. Tomorrow, we’ll go over the Delivery Controls feature which I’m sure you’ve been wondering about over the last several days.
If you have any questions, please share them in the comments. We’re happy to help! 🙏
If you learned something from this video, please subscribe for more awesome Braze videos in the future!
Thank you for watching, and see you next time!
allan@fornowmarketing.com
fornowmarketing.com
