Skip to main content

RTB Requests Reporting Enhancements

D
Written by Denise Abdullah
Updated over 2 months ago


​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.

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.

Did this answer your question?