FEATURE ENHANCEMENT RELEASE
RTB Reporting — Outbound Visibility & Inbound Improvements
Location: Reporting → RTB Requests
Release Date: February 18, 2026
Overview
This release expands RTB reporting in two ways: it adds a new Outbound section that shows what the platform sends to buyers, and it upgrades the existing Inbound view with new columns, filters, and pagination. Together, these changes give you a complete picture of RTB activity — publisher pings coming in and bid requests going out — in one reporting surface.
What's New
New: Outbound Section
A new Outbound section now appears at the bottom of the RTB Requests report. It shows each outbound bid request grouped by request ID — with the campaign, publisher, buyer, number of steps, latest HTTP status code, state, and timestamp.
Each row groups all the individual bid steps for that request. Expand a row to inspect step-level detail: buyer endpoint, HTTP method, timing, request config, and the buyer's full response. Config and response data open in a JSON viewer.
Outbound state — Each outbound request shows one of three states: COMPLETED, NO_ROUTES, or ERROR. States are color-coded in the table.
Latest HTTP status — A separate column shows the HTTP response code from the buyer's last step (e.g., 200, 404, 500), color-coded by range.
Inbound Request ID — Each outbound request is linked to the originating inbound ping via an Inbound Request ID column. Use it to trace a full RTB request end-to-end: the publisher ping that triggered it, the outbound bid steps it generated, and the call outcome.
Updated: Inbound View
The existing inbound RTB Requests table has been updated with new columns and controls.
New columns — The inbound table now shows Caller ID, Campaign, Publisher, and Buyer alongside the existing State column.
Filters — Campaign, Publisher, and Buyer filter dropdowns are now available on the inbound view, so you can scope it to a specific slice of traffic.
Pagination — The inbound table now paginates server-side, improving performance for high-volume accounts.
New: Inbound/Outbound Toggle in RTB Statistics Summary
The RTB Statistics Summary now includes an Inbound/Outbound toggle. Switch to Outbound to see aggregate metrics — Requests, Responded, Connected, and Converted — broken down by campaign, publisher, buyer, and state.
Outbound filters — The Outbound view includes the same Campaign, Publisher, and Buyer filter dropdowns as the updated inbound view.
Why This Matters
Until now, RTB reporting showed what publishers sent in — but not what happened next. Outbound reporting closes that gap. You can see which buyer endpoints are responding, which are returning errors, and how bid outcomes connect to actual call conversions. The inbound improvements make it easier to find specific requests and understand their context without having to cross-reference other reports.
Example Use Cases
Filter the Outbound view by buyer to find an endpoint with a high rate of 500 errors — and confirm the issue before it affects fill rates.
Use the Inbound Request ID on an outbound row to trace a specific caller's journey from publisher ping through buyer bid to connected call.
Compare Responded vs. Connected counts across buyers to identify which buyers are winning bids but not converting to calls.
Use the new Caller ID column in the inbound view to look up a specific caller's RTB request without leaving the report.
Getting Started
Navigate to Reporting → RTB Requests.
Use the Campaign, Publisher, and Buyer dropdowns to filter the inbound view.
Scroll to the bottom of the page to find the new Outbound section.
Toggle between Inbound and Outbound in the RTB Statistics Summary to compare aggregate metrics.
Click any outbound row to expand step-level detail, or click a Config or Response cell to open the JSON viewer.
Questions? Reach out to your account manager or contact support.