Feature Update
Location: Reporting β RTB Requests
βRelease Date: 9/29/25
π Overview
The RTB Requests reporting view has been enhanced to provide clearer visibility into routing outcomes, bid results, and call-level details. These improvements make it easier to understand why routes succeed or fail and to validate performance against RTB API responses.
β¨ What Changed
π New Routing Outcome Columns
The RTB Requests table now includes additional columns to improve transparency:
Total Routes
Failed Routes
β(ineligible routes, caps reached, outside hours of operation, etc.)Successful Routes
Bid Won
If Yes, Duration and Payout are displayed
Displayed only when a call is successfully transferred
βοΈ Expanded Call Metrics
Additional call-level fields are now available directly in reporting:
Duration
Payout
CLID
These values help tie routing outcomes directly to call performance.
π API Response & Call Detail Visibility
Each RTB request now includes:
The actual RTB ping/response associated with the call
CLID included when a call is placed
A View Call action that links directly to detailed call records tied to the CLID
π¦ Traceability: Reporting data now aligns more closely with RTB API behavior and call execution.
π― Why This Matters
These enhancements make RTB reporting more actionable and easier to troubleshoot by:
Clarifying why routes succeed or fail
Making bid outcomes more transparent
Aligning routing data with API responses and call records
Reducing friction when validating performance or investigating issues
π‘ Example Use Cases
Identify whether a call failed due to caps, budgets, geography, or hours-of-operation rules
Confirm that winning bids correctly display Duration and Payout
Use CLID to cross-reference RTB activity with call logs and external API records
π Getting Started
Navigate to Reporting β RTB Requests
Review the new routing and bid-related columns in the table
Click View Call to access full call details associated with the CLID
π§ Roadmap
Additional reporting enhancements and expanded analytics are planned to further improve RTB visibility and performance analysis.