How to read call logs
Trace a single call from arrival to outcome: narrow the time range, find the row, read the routing decision, and decide whether the problem is configuration or delivery.
Calls not connecting, RTB no-bids, high processing time, and calls arriving without revenue.
Troubleshooting
Articles
8How to troubleshoot high RTB processing time
Diagnose high inbound RTB processing time by checking buyer response latency, timeout settings, fanout, routing complexity, request data, and traffic volume.
How to troubleshoot RTB no-bid responses
Use RTB Logs to diagnose no-bid responses by checking request quality, buyer eligibility, bid economics, response status, timeouts, and routing setup.
Troubleshooting: “Please unblock challenges.cloudflare.com to proceed” Error
When attempting to access moja ai portal, you may see the following error
Why am I getting calls but no revenue?
Diagnose why calls appear in Call Logs with $0 revenue by checking duration, buyer qualification, payout configuration, publisher payout, postbacks, and RTB outcomes.
Why Am I Seeing RTB Logs but No Call Logs?
Trace an inbound RTB request from its response and allocation to call delivery, and distinguish a missing call log from a call that did not connect.
Why are my calls not connecting?
Diagnose why calls are not connecting by checking call-log fields, routing eligibility, buyer/target availability, RTB results, and SIP response codes.
Why are there many RTB requests but no calls?
Find where inbound RTB traffic stops progressing: request acceptance, usable offers, publisher call delivery, or buyer connection.