Step 2: Schedule Delivery Workflow
Interactive student module explaining message timing, event triggers, and delivery controls in Braze
Time-Based Schedule
Step 2a
2a. Scheduled Delivery
Send messages at a
specific date/time
or optimize delivery per individual using AI-driven
Intelligent Timing
.
Scheduled Calendar vs. AI Optimal Time
Schedule Type
Send Once at Designated Time
Recurring (Daily / Weekly / Monthly)
Intelligent Timing (Most Active Hour)
Send Immediately on Campaign Launch
Scheduled Start Date
Action-Based Triggers
Step 2b
2b. Event-Based Delivery
Trigger messages in real-time when users perform a specific action, such as an
In-App Purchase
,
Session Start
, or custom event.
User Action Event ➜ Dynamic Delay ➜ Message Send
Trigger Event Action
Performs Custom Event (e.g. Added To Cart)
Starts App Session
Makes Any Purchase
Enters Geofence Area
Delivery Delay
Send Immediately
Delay 15 Minutes
Delay 1 Hour
Delay 1 Day
API-Triggered Send
Step 2c
2c. API-Triggered Delivery
Pass server-side payload data directly via the
/campaigns/trigger/send
API for transactional communications.
External Server ➜ API REST Call ➜ Braze Push/Email
Campaign Trigger ID
Requires server endpoint configuration with API authorization headers.
Time Zone & Quiet Hours
Step 2d
2d. Local Time & Quiet Hours
Respect international audiences by delivering messages in the user's
Local Time Zone
and suppressing overnight alerts using
Quiet Hours
.
Suppress Messages Between 10:00 PM and 8:00 AM
Send campaign in user's
local time zone
Enable
Quiet Hours
(Delay send if triggered during restricted hours)
Frequency & Limits
Step 2e
2e. Re-Eligibility & Capping
Prevent message fatigue by controlling how often a user can re-enter this campaign and enforcing workspace-level
Frequency Capping Rules
.
Limit Messaging: Max 2 Push Notifications per Day
Allow users to become
re-eligible
after 7 days
Respect Global
Frequency Capping Rules
Delivery schedule configuration complete! Ready to target audiences.