Why Am I Seeing RTB Logs but No Call Logs?
A common question when troubleshooting inbound RTB traffic is why RTB logs are being generated while no corresponding call logs appear in the Call Logs section.
In most cases, this behavior is expected and indicates that the RTB request did not progress far enough to create a call!
Understanding the Difference
Section titled “Understanding the Difference”RTB Logs
Section titled “RTB Logs”RTB Logs are created whenever Moja AI receives an inbound RTB request.
These logs record the bidding process, including:
-
Incoming RTB requests
-
Buyer responses
-
Bid amounts
-
Rejections
-
Processing times
-
Routing decisions
An RTB log can exist even if no call is ultimately created.
Call Logs
Section titled “Call Logs”Call Logs are only created when an actual call enters the platform and begins call processing.
If no call is initiated or transferred after the RTB process, no call log will exist.
Common Reasons:
Section titled “Common Reasons:”No Buyer Won the Bid
Section titled “No Buyer Won the Bid”If all buyers return no-bids or are filtered out by campaign requirements, the RTB request will be logged, but no call will be created.
Check the RTB Log for:
-
Reject reasons
-
Missing required parameters
-
Buyer responses
-
Bid activity
The Request Was Only a Ping
Section titled “The Request Was Only a Ping”Many RTB integrations use a Ping/Post workflow.
During the Ping stage, buyers are asked whether they are interested in the traffic.
Because no call exists yet, only an RTB log is created.
A call log will only appear after a successful Post or call transfer occurs.
Missing Required Parameters
Section titled “Missing Required Parameters”If required fields such as state, caller ID, zip code, publisher identifiers, or custom campaign parameters are missing, buyers may reject the request.
The RTB request will still be recorded, but no call will be generated.
Buyer Filters Rejected the Request
Section titled “Buyer Filters Rejected the Request”Buyers may reject traffic based on:
-
Geographic restrictions
-
Schedule restrictions
-
Caps
-
Compliance requirements
-
Custom rules
Review the RTB log to determine why buyers declined the request.
The Call Never Reached Moja AI
Section titled “The Call Never Reached Moja AI”In some integrations, Moja AI receives bidding requests before the actual call is transferred.
If the transfer never occurs, the RTB log remains available while no call log is created.
How to Troubleshoot?
Section titled “How to Troubleshoot?”When you see RTB logs but no call logs:
-
Open the RTB Log.
-
Review buyer responses and reject reasons.
-
Verify that all required parameters were provided.
-
Confirm whether the request was a Ping or an actual call transfer.
-
Check whether a buyer won the bid.
-
Verify that the call was successfully transferred into Moja AI
Summary
Section titled “Summary”Seeing RTB logs without call logs does not necessarily indicate a problem. RTB logs track bidding activity, while call logs track actual calls, If the RTB process does not result in a transferred or connected call, an RTB log may exist without any corresponding call log.