RTB Requests Reporting Enhancements
Location: Reporting → RTB Requests SectionWhat Changed
Added new columns for improved visibility into routing outcomes:
Total Routes
Failed Routes (ineligible routes, met caps, outside HOO, etc.)
Successful Routes
Bid Won → If Yes, Duration and Payout are displayed (conditional on successful call transfer).
Duration
Payout
CLID
Added API response detail per call, including the actual ping associated with the call.
If a call was made, the CLID is now included in the details.
Users can click View Call to see specific call details tied to the CLID.
Why This Matters
These updates provide clearer insights into why routes succeed or fail, make bid outcomes more transparent, and align reporting data with API responses. This reduces friction when troubleshooting calls or validating performance.
Example Use Cases
Identify if a call failed due to restrictions (caps, budget, state, etc.).
Confirm that a winning bid properly shows Duration and Payout.
Use CLID details to validate calls against API logs.
CSV exports for RTB request tables
RTB request tables now support CSV export. Exports are available for Inbound RTB Life Logs, Inbound RTB Requests, and Outbound RTB Requests.
Exported files use the same date range, filters, search, and sort settings currently applied to the table. Large exports stream with progress feedback and can be cancelled while running.
Getting Started
Navigate to the RTB Requests section on the Reporting page. Look for the new columns in the table, then click View Call for complete call details.