Transparent Expected Conversion Details on RTB Reservations

What's new

When a ping arrives via the RTB API, Retreaver selects a buyer based on your campaign's routing strategy - whether that's Priority & Weight, Route by Performance, or Route by Bid. Once a buyer is selected, Retreaver determines the expected financial outcome of the call using the buyer's conversion criteria:

• Expected Payout: How much the buyer is willing to pay, based on the payable conversion configured on the target
• Expected Revenue: How much the publisher will receive, based on the receivable conversion
• Expected Seconds: The minimum call duration required for the conversion to trigger

These values are returned in the RTB response as retreaver_payout and retreaver_seconds, and were previously only visible in the RTB dashboard.

What you'll see

Superusers can now view an "RTB Properties" section on the call detail page, even before the call arrives. This section shows:

• The expected payable and receivable conversion groups that were evaluated
• The specific conversion rule that matched, showing the logic of how the payout was calculated
• The expected payout, revenue, and required seconds
• When the conversion was determined

All values are marked as expected to distinguish them from the actual conversion outcome after the call completes.

Why it matters

Previously, the payout and seconds were visible in the RTB dashboard but there was no way to see the underlying payable and receivable conversion logic that determined those values. Now the full conversion criteria - which conversion group matched, which rule applied, and how the payout was calculated - is visible directly on the call page, making it easier to audit bids, debug routing decisions, and reconcile expected vs actual payouts.