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!

RTB Logs are created whenever Moja AI receives an inbound RTB request.

These logs record the bidding process, including:

An RTB log can exist even if no call is ultimately created.
​

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.
​

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:

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.

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.

Buyers may reject traffic based on:

Review the RTB log to determine why buyers declined the request.
​

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.
​
​

When you see RTB logs but no call logs:

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.