Each RTB formula can now limit how many outbound pings Moja sends during a minute, hour, or day without reducing traffic for the entire publisher or campaign.

Set a maximum number of simultaneous in-flight requests to prevent one buyer endpoint from receiving more concurrent pings than it can handle.

Enable buyer cooldown to temporarily stop new pings after a configured number of consecutive buyer rate-limit responses, duplicate-shield responses, or timeouts. Other eligible formulas can continue competing while one formula is throttled.

Leave these settings blank or disabled to preserve unlimited outbound ping behavior.

Open Targets/RTBs → RTBs, select an RTB formula, and configure its outbound ping rate and period, in-flight request cap, or cooldown threshold and duration.

Use the minute, hour, or day rate window to match the buyer’s accepted ping volume. Pair it with the in-flight cap when the endpoint also limits concurrent requests.

Use cooldown when repeated buyer-side rate limits, duplicate protection, or timeouts should pause that formula briefly instead of continuing to send requests.

In outbound RTB reporting, the By Buyer view now distinguishes pings Moja intentionally skipped because of the configured throttle from buyer HTTP 429 responses, duplicate-shield responses, and buyer timeouts.

Ask AI follows the same distinction, so teams can tell whether Moja protected a configured limit or the buyer rejected an actual request.

Teams can protect buyer relationships and endpoint capacity without pausing the buyer, removing it from routing, or slowing unrelated RTB traffic.