RTB Dashboard

The RTB Log and Call Log show different stages of the call flow.

A publisher can send an RTB request and receive a reservation, but if they never route the caller to the reserved number, that activity appears in the RTB Log but not in the Call Log.

This is one of the most important differences when troubleshooting “missing calls.”

Every RTB chart, drilldown, and log row follows the date range and filters at the top of the page.

• Realtime tab — live RTB activity as requests come in.
• Historical tab — past RTB activity based on the selected date range.
• Add Filter — filter by campaign, publisher, call buyer, postback key, status, caller location, tags, payout, and more.
• Search RTBs by UUID or Caller Number — quickly locate a specific reservation request.
• Date range picker — choose common ranges like past 1 hour, past 6 hours, past 1 day, past 2 days, today, yesterday, month to date, or a custom range.
• Time zone indicator — shows which time zone the data is being viewed in, such as EDT.

RTB statuses explain what happened to each reservation request.

A Reserved status does not always mean a call was received. It means the opportunity was accepted and a slot was held.

An Expired status usually means the publisher received the reservation but did not complete the handoff by sending the call into Retreaver.

A No-target status usually means Retreaver could not find an available buyer based on business hours, geo targeting, filters, caps, tags, or routing rules.

The Inbound Requests chart shows RTB request volume across the selected date range.

Use this chart to identify:

• Spikes in inbound RTB activity
• Drops in publisher traffic
• High ping volume that is not converting into calls
• Time periods where requests increased but calls did not
• Daypart patterns in RTB traffic

The chart is especially useful when comparing publisher activity against actual call volume. If RTB volume is high but call volume is low, check for expired reservations or publisher handoff issues.

Use this chart to answer: “Are publishers sending requests, and are those requests turning into calls?”

This chart breaks down the reasons RTB requests are not finding a successful path.

Common reasons may include:

• undialable_expression — the caller number did not match the campaign’s dialable rules or targeting logic.
• target_disqualified — a buyer was available but did not match the caller profile, such as state, ZIP, tags, or other filters.
• targets_closed — eligible buyers were closed due to business hours, caps, schedules, or availability rules.
• targets_paused — buyers were paused manually or by configuration.
• rejected — the request was rejected by a buyer endpoint, webhook, or campaign rule.

This chart breaks down RTB request outcomes by Postback Key.

Each postback key represents a publisher integration endpoint. Reviewing activity by postback key helps identify which traffic sources are producing healthy reservations and which are causing issues.

Common outcomes include:

• claimed — the reservation became a call.
• expired — the reservation was created, but the publisher did not send the call.
• no-target — no eligible buyer was available.
• rejected — the request was rejected.

This chart shows how many inbound requests have been limited per postback key.

High limited counts may indicate:

• Duplicate ping activity
• Repeated requests for the same caller
• Publisher-side retry logic creating excess pings
• Traffic volume exceeding expected limits
• Low-quality or mismatched traffic being sent repeatedly

Use this widget to identify publisher integrations that may need review.

Pair this chart with the Postback Key breakdown to see whether a publisher is generating high volume, high limits, high no-targets, or high expired reservations.

The RTB Drilldown lets you build a nested report using multiple levels. This is one of the best tools for identifying exactly where RTB issues are coming from.

You can drill down by:

• Type
• Campaign
• Status
• Publisher
• Call Buyer
• Postback Key
• Caller Number
• Caller State
• Caller City
• Caller ZIP
• Caller Country
• Daily
• Hourly
• Day Of Week
• Hour Of Day
• Tag

How to add or remove drilldown levels:

1. Locate the Drill down by: row.
2. Click the + button.
3. Select the level you want to add.
4. Click Apply.
5. Remove any level by clicking the × on the chip.

A useful default workflow is:

Type → Campaign → Status

This quickly shows which campaigns are producing inbound RTB requests and whether those requests are being reserved, expired, rejected, or returning no-target.

Another useful workflow is:

Publisher → Postback Key → Status

This helps identify which publisher integrations are producing the most issues.

The RTB Log is the detailed event-level table at the bottom of the RTB Dashboard. Each row represents an individual RTB reservation request.

Common columns include:

Use the RTB Log when investigating a specific reservation, caller number, UUID, publisher, campaign, or postback key.

The RTB Log is especially useful when a publisher says they sent traffic, but you do not see matching calls in the Call Log.

The RTB Dashboard supports reusable templates and CSV exports.

Templates allow you to save custom dashboard views, including selected drilldown levels, hidden or reordered columns, and preferred layouts.

Examples of useful RTB templates:

• Publisher_Health_Daily
• Postback_Key_Audit
• No_Target_Review
• Expired_RTB_Report
• Campaign_RTB_Performance

CSV Export allows you to export the current drilldown or RTB Log view.

The export reflects the filters, date range, columns, and drilldown levels currently applied.

Use CSV exports when you need to:

• Share data with a publisher
• Review RTB performance offline
• Send a report to a buyer or internal stakeholder
• Compare RTB activity against Call Log activity
• Audit expired, rejected, or no-target reservations

An expired RTB means Retreaver created a reservation, but the publisher did not send the call before the reservation window expired.

This usually points to a publisher-side handoff issue.

Check whether:

• The publisher is routing calls to the reserved number
• The publisher is using the reservation response correctly
• The caller is dropping before transfer
• The publisher system is delaying the call
• The reservation window is expiring before the caller is sent
• The same caller or UUID appears repeatedly without a matching call
• The publisher is sending pings but not completing the call transfer

A no-target RTB means Retreaver could not find an eligible buyer or route for the request.

Start by checking buyer availability.

Confirm that:

• Buyer business hours are open
• Geo targeting matches the caller
• Required tags or filters are present
• Buyer caps have not been reached
• Buyer concurrency is available
• The buyer is assigned to the correct campaign
• The buyer is enabled
• The buyer endpoint or webhook is responding correctly
• The buyer’s direct phone line is working

If a direct test call to the buyer goes to voicemail or fails, the issue is likely on the buyer side, not in Retreaver.

A buyer may be configured correctly but still receive few or no calls if they are too low in the routing waterfall or have restrictive settings.

Review the buyer’s:

• Campaign assignment
• Business hours
• Geo targeting
• Tags and filters
• Caps
• Concurrency
• Endpoint or webhook response
• Direct phone line
• Priority
• Weight

Routing priority and weight can significantly affect delivery.

Avoid unusual priority values like:

• -1
• 0
• inconsistent priority numbering

Use a clear ascending priority structure instead:

• Priority 1
• Priority 2
• Priority 3

A buyer with the correct filters but low priority may receive very little traffic if higher-priority buyers are taking most of the available volume.

If you are testing and cannot find your call in the Call Log, check your filters first.

Make sure to:

• Reset active filters
• Expand the date range
• Search by caller number
• Search by UUID
• Confirm the correct campaign is selected
• Confirm the correct time zone is selected
• Check whether the RTB expired before becoming a call

A narrow date range or active filter is one of the most common reasons calls appear to be missing.

Business hours can be applied at different levels, including the tracking number level.

If the tracking number itself has business hours applied, calls outside those hours may not pass through as expected.

When testing:

1. Open the tracking number.
2. Review the number-level business hours.
3. Confirm the number is open during your test window.
4. If appropriate, set the number to 24/7 while troubleshooting.
5. Test again and review both the RTB Log and Call Log.

Number-level business hours can prevent calls from passing through even when the campaign or buyer appears available.

Use this workflow when a publisher says they sent traffic, but the Call Log does not show matching calls.

1. Open the RTB Dashboard.
2. Select the correct date range.
3. Search by caller number or UUID.
4. Check whether the request was Reserved or Expired.
5. Open the Call Log in a separate tab.
6. Search for the same caller number or call UUID.
7. If the RTB exists but no call exists, the publisher likely did not send the call into Retreaver.
8. Share the RTB details with the publisher so they can confirm their routing and handoff logic.

Use this workflow when RTB requests are returning no-target.

1. Open the RTB Dashboard.
2. Set the date range to the affected period.
3. Add a drilldown: Type → Campaign → Status.
4. Identify which campaigns have the highest no-target volume.
5. Add another drilldown level for Publisher or Postback Key.
6. Review whether no-targets are concentrated around one source.
7. Check buyer availability, business hours, caps, geo targeting, required tags, and routing priority.
8. Test the buyer’s direct phone line if needed.

Use this workflow to evaluate whether publisher traffic is matching your buyer coverage.

1. Open the RTB Dashboard.
2. Drill down by Publisher → Postback Key → Status.
3. Review the ratio of claimed, expired, no-target, and rejected requests.
4. Identify publishers with high expired or no-target volume.
5. Compare their RTB activity against actual calls in the Call Log.
6. Export the results as a CSV if you need to share the data.
7. Follow up with the publisher if they are sending mismatched traffic or failing to complete reserved calls.

Use this workflow when a buyer says they are not receiving enough calls.

1. Open the RTB Dashboard.
2. Filter by the affected campaign.
3. Drill down by Call Buyer → Status.
4. Review whether requests are being rejected, no-targeted, or routed elsewhere.
5. Check the buyer’s business hours, caps, filters, geo coverage, and endpoint response.
6. Review routing priority and weight.
7. Confirm whether higher-priority buyers are taking the available volume.
8. Run a direct test call to confirm the buyer line is active.