Why are there many RTB requests but no calls?

If you see a high number of inbound RTB requests but very few or no calls, Moja AI is receiving ping traffic, but those pings are not turning into connected calls.

This usually means the issue is happening somewhere between the RTB request, buyer bidding, and call transfer. It is common during testing, new buyer setup, low-demand periods, or when traffic does not match buyer requirements.

What this means

An RTB request is not the same thing as a call. An RTB request means a publisher or traffic source asked whether buyers want a potential call. A call is created only when the flow advances far enough for an actual phone call to enter Moja AI and route to a buyer.

So it is possible to have thousands of RTB requests and very few calls if buyers are not bidding, the request is missing required data, or the caller never connects after the ping.

Common causes

• No buyers are bidding. Buyers may reject the traffic or return no bid.

• Bid amounts are too low. A buyer may bid, but not high enough to win the traffic.

• Required parameters are missing. Common examples include caller ID, ZIP/postal code, state, vertical, publisher ID, or custom campaign fields.

• Buyer filters do not match the traffic. Filters such as geography, hours, campaign, duplicate rules, TCPA rules, or caller profile can prevent a bid or route.

• The ping was valid, but the call never arrived. In ping/post or ping-to-call flows, a request can be logged even if the caller never transfers into Moja AI.

• Processing time is too high. Slow buyer responses or long RTB group timers can cause the call opportunity to expire before routing completes.

• Routing or campaign configuration is incomplete. Inactive buyers, inactive targets, missing routing plans, caps, or schedule rules can prevent calls from routing.

Example

If you see:

• 10,000 inbound RTB requests

• Many no-bid or rejected responses

• 0 connected calls

That usually means buyers are receiving the pings but are not accepting the traffic, or the traffic source is not sending a call after the ping stage.

What to check first

1. Check buyer responses in RTB logs. Look for no-bids, reject reasons, missing fields, timeout errors, or low bid amounts.

2. Confirm required fields are present. Compare the inbound request against the buyer’s required parameters.

3. Review filters and targeting rules. Check geography, hours, vertical, duplicate rules, caller profile rules, and any custom tag filters.

4. Check active buyers and targets. Make sure the buyer, target, routing plan, and campaign are active and eligible to receive traffic.

5. Review processing time. High processing time can mean buyer endpoints are slow or the RTB flow is waiting too long before routing.

6. Compare RTB requests to call logs. If RTB logs exist but call logs do not, the request likely did not become an actual call.

Metrics to review

• Ping-to-call ratio: Shows how often RTB pings become calls.

• Converted-to-call ratio: Shows how often accepted opportunities become connected calls.

• Inbound RTB requests: Shows request volume by source, campaign, buyer, and time period.

• RTB trends over time: Helps identify whether the issue is temporary, buyer-specific, or traffic-source-specific.

• Processing time by buyer: Helps identify slow buyer endpoints or timeout problems.

How to narrow it down

What you see	Likely cause	What to check
Many requests, many no-bids	Buyer demand or filters	Reject reasons, buyer filters, traffic requirements
Requests but no call logs	Ping did not become a call	Ping/post flow, publisher transfer behavior, call source setup
Bids returned but no connected calls	Routing or transfer issue	Routing plan, target status, transfer number/SIP, call logs
High processing time	Slow buyer responses or long RTB timers	Processing time by buyer, timeout settings, RTB group timer
Only some buyers reject	Buyer-specific criteria	Buyer filters, required fields, caps, business hours

When to contact support

Contact Moja AI support if you have confirmed that required fields are present, buyers are active, and routing is configured correctly, but RTB requests still are not becoming calls.

When reaching out, include:

• Campaign name

• Approximate time range

• Example RTB request IDs

• Buyer or target names involved

• Expected result versus what happened

Including request IDs and a time range helps support trace the exact point where the request stopped progressing.

Summary

High RTB request volume with few or no calls is usually caused by buyer response, missing data, filtering, processing time, or ping-to-call transfer behavior. Start with RTB logs and reject reasons, then compare those requests against call logs and routing configuration.