RTB Pulse now explains buyer response outcomes
Category: Enhancement
Location: Reporting → RTB Pulse → Tuning
Release Date: August 21, 2026
What’s new
RTB Pulse now separates transport failures from the business outcome returned by a buyer, so a successful connection that returns “no target” is no longer grouped with an endpoint that never responded.
Open an endpoint in Tuning to see a Summary-first percentage breakdown for the last 24 hours, 7 days, or 30 days across six outcomes: Accepted, No target, Rejected, Ping Shield, No response, and Other.
Recommendations now reflect the dominant outcome mix. This helps distinguish buyer availability, duplicate protection, source rejection, and configuration or rate-limit responses from genuine timeout or connection failures.
Endpoint health now distinguishes idle, paused, degraded, and critical behavior. An endpoint receiving meaningful traffic with no responses is no longer shown as idle.
How to use it
Open Reporting → RTB Pulse, select Tuning, then choose an endpoint.
Review the Summary outcome mix and switch between 24-hour, 7-day, and 30-day periods to see whether the dominant buyer response is persistent or recent.
Use the outcome-specific recommendation to decide whether to investigate availability, traffic quality, duplicate pings, endpoint configuration, or transport health.
Impact
Teams can diagnose outbound RTB performance from the operational summary instead of interpreting raw response bodies or treating every non-bid result as the same failure.