skills.rest
delta-and-beta
delta-and-betaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

engineer-campaign-building

Configure Braze campaign delivery, triggers, and rate limiting.

Updated Apr 6, 2026
Search Tags:#triggers#scheduling#rate-limiting#campaigns#delivery#api-triggered#braze
One-click install
npx skills add https://github.com/delta-and-beta/braze-agency --skill engineer-campaign-building
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: engineer-campaign-building
Source: https://github.com/delta-and-beta/braze-agency/tree/main/skills/engineer-campaign-building
Command: npx skills add https://github.com/delta-and-beta/braze-agency --skill engineer-campaign-building

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides clear, technical guidance to implement, configure, and troubleshoot Braze campaign delivery so teams can reliably send scheduled, triggered, or API-initiated messages without accidental over-sending, misconfigured triggers, or delivery-window failures.

Core Features & Use Cases

  • Delivery Type Selection: Guidance to choose between scheduled, action-based (triggered), API-triggered, attribute-triggered, and campaign-connector approaches.
  • Triggering & Scheduling: Steps for configuring event and attribute triggers, re-eligibility windows, exception events, Intelligent Timing, and local time zone delivery.
  • Rate Limiting & Frequency Capping: How to set per-minute throughput caps, channel or shared limits for multichannel sends, maximum user caps, and global frequency capping rules.
  • Integration & API Use: Best practices for wiring API-triggered campaigns, using trigger_properties for templating, and persisting user attributes when needed.
  • Auditability & Operations: Using the Content Calendar, send audits, and reference docs to validate campaigns before launch.
  • Use case example: Configure an API-triggered transactional campaign that uses trigger_properties for personalized content, enforces a 10k/min rate limit, and respects global frequency capping.

Quick Start

Create or open a Braze campaign, set delivery to API-triggered or action-based as required, add your audience and conversion events, configure rate limiting and re-eligibility, then run a controlled test to validate sends and template rendering.

Frequently Asked Questions about engineer-campaign-building

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure API-triggered Braze campaigns with trigger_properties?▼

To configure API-triggered Braze campaigns, set delivery to API-triggered, use trigger_properties for payload templating, and persist user attributes. You must enforce rate limiting and run controlled tests to validate template rendering before launch.

What's the best way to prevent over-sending in Braze multichannel campaigns?▼

Prevent over-sending in Braze multichannel campaigns by setting per-minute throughput caps, maximum user caps, and global frequency capping rules. Channel or shared limits should also be configured for multichannel sends to strictly control delivery rates.

How does local timezone scheduling work for Braze campaign delivery?▼

Local timezone scheduling allows Braze campaigns to send messages to users based on their specific regional time. Configure this during the delivery setup alongside Intelligent Timing and re-eligibility windows to ensure messages arrive at appropriate local hours.

When should I use action-based triggers instead of scheduled delivery in Braze?▼

Use action-based triggers in Braze for event-driven messages, while scheduled delivery suits fixed-time broadcasts. Action-based workflows leverage event and attribute triggers, exception events, and re-eligibility windows to respond immediately to user actions.

How do I audit Braze campaign sends before a launch?▼

Audit Braze campaign sends by utilizing the Content Calendar and performing send audits. Validate campaign configurations, trigger property usage, and delivery settings against reference docs to ensure compliance and prevent misconfigured triggers.

Can I use campaign-connector workflows with Braze rate limiting?▼

Campaign-connector workflows support Braze rate limiting by applying per-minute throughput caps and shared channel limits. Configure maximum user caps and global frequency capping rules to manage multichannel sends and prevent accidental delivery failures.

Related Skills

Explore More Software Engineering Skills→
delta-and-betadelta-and-beta

analyst-segment-analytics

Analyze Braze audience segments, event frequency, and attribute correlations.

Community
Intermediate
delta-and-betadelta-and-beta

tester-messaging-validation

Validate Braze message delivery and rendering across Web, Android, and iOS SDKs.

Community
Intermediate
a-ariffa-ariff
14

canvas-api

Connect to the Canvas LMS API for course data access.

Community
Advanced
delta-and-betadelta-and-beta

engineer-canvas-creation

Automate Braze Canvas flow implementation with entry properties, channel configuration, and exit criteria.

Community
Advanced