Issue
Customers routing traffic from Segment to Braze may notice that event requests are not being batched to the maximum configuration limit of 75 events, resulting in unexpectedly small payload sizes per request. This reduced batch size increases the total request volume and can trigger HTTP 429 rate limit errors on both Segment and destination jobs. While the Batch Data to Braze setting is enabled, the system does not wait indefinitely to fill the 75-event quota.
Product
Segment Destinations
Environment
Segment Console
Cause
Segment evaluates and queues batches per mapping rather than aggregating them across the entire destination. Batches are flushed to the destination when either the maximum size limit is reached (75 events for Braze) or a predefined time threshold (up to one minute) is met to ensure data freshness.
If a workspace utilizes numerous active mappings (such as separate queues for Update User Profile and Track Event), the event volume is fragmented across isolated queues. Because the traffic is divided, each queue fills slowly, causing the time-based flush to trigger before the 75-event maximum is reached.
Resolution
To achieve denser batching and reduce the total number of HTTP requests, you can consolidate your active mappings.
- Review your current Segment to Braze destination mappings within your workspace.
- Combine multiple mappings with highly specific event triggers into fewer, broader mappings.
- Verify that your pooled traffic allows the combined queues to reach the 75-event maximum much faster. This ensures size-based flushes trigger before the time threshold kicks in.
Additional Information
Segment automatically retries data delivery when encountering rate limits to prevent data loss. Consolidating mappings is the recommended initial approach to optimize batch sizes and reduce request volume. For more information you can refer to this following doc: