RTB Bid Expiration and TTL Controls
Category: Enhancement
Location: Targets/RTBs → RTB Formulas and Targets/RTBs → RTB Groups
Release Date: August 7 2026
Inbound RTB routing can now account for how long a buyer’s bid remains valid, helping prevent accepted bids from being passed downstream after—or just before—the buyer’s routing window expires.
What changed
RTB Formulas now include Bid TTL Settings where you can set a default bid TTL and a minimum remaining TTL required to accept a bid.
RTB Groups now support minimum and maximum bid TTL controls, including formula-level overrides when different formulas need different limits.
Buyer expiration values are recognized in ISO timestamps, Unix seconds or milliseconds, and relative TTL seconds. Retreaver response mappings can pass the buyer’s
expires_atvalue through asexpiresAt.Bids below the configured minimum TTL are rejected instead of being treated as usable; bids above a group maximum are constrained to the configured window.
Routing allocation is limited to the bid’s remaining lifetime, and expired duplicate-response cache entries are no longer replayed.
How to use it
Open an RTB Formula and configure its default TTL for responses without buyer expiration data, plus the minimum remaining TTL required for acceptance.
Open an RTB Group to set the group-wide minimum and maximum TTL. Add formula overrides when one formula needs stricter or broader limits than the group default.
For Retreaver buyers, map the buyer response’s
expires_atvalue toexpiresAtso Moja can preserve the buyer-provided expiration.
Impact
Publishers receive fewer stale accepted bids, while sellers gain explicit control over which bids have enough time remaining to route and connect successfully.