Understanding Processing Time in RTB

Processing time measures how long Moja spends handling an inbound RTB request and preparing its response. Depending on the request and routing configuration, this can include eligibility checks, downstream buyer requests, bid evaluation, and allocation work.

It is not the duration of a phone call, the time a destination rings, or proof that a call connected.

What happens during processing

An inbound RTB request may involve:

Validating the request and checking campaign and publisher eligibility.
Evaluating routing rules, filters, schedules, and applicable limits.
Sending requests to eligible downstream RTB buyers.
Waiting for buyer responses or timeout.
Evaluating usable results and preparing the response and any applicable allocations.

Not every request reaches every stage. Use the recorded request details to see what happened.

Where to find processing time in Moja

Open Reporting.

In Inbound RTB Requests, review the Processing Time column for the affected request. This table displays the value in seconds.
In Inbound RTB Life Logs, expand the request and open Life Log. Where present, Request Summary → Processing Time shows elapsed processing at that logged stage. Its formatting can differ from the request table.
Use RTB Requests to inspect downstream request steps and responses.
Use Response to inspect what Moja returned, and Allocations to check whether an allocation was created.

A timing value recorded during processing may differ from the final request timing. Compare the same field and stage when assessing changes.

A bid or allocation alone does not establish that a call connected.

Why processing time matters

If the response arrives after the requesting system’s deadline, it may no longer be usable—even if Moja or a downstream buyer produced a bid.

There is no single processing-time threshold that suits every integration. Compare the affected requests with the publisher’s deadline, the configured timeouts, and the normal baseline for comparable traffic.

High processing time alone does not identify a buyer timeout, explain a no-bid result, or prove a failed transfer.

What can affect processing time?

Buyer response latency and timeouts

A slow buyer endpoint or a request that waits until timeout can increase elapsed processing time. Check the recorded response or error before concluding that the buyer timed out.

Routing and request execution

Timing depends on which destinations are eligible and how the configured requests run. RTB-group buyer requests can run concurrently, so total processing time is not simply the sum of all buyer response times.

Buyer count alone is not enough to diagnose a delay.

Request data and external dependencies

Missing or malformed data can cause rejection or make destinations ineligible. Do not assume validation repeatedly retries or that invalid data necessarily makes processing slower.

External buyer services and network paths can also introduce delay. Customers should investigate systems they control and coordinate with the buyer or Moja support for systems they do not.

How timeout settings relate to processing time

For an outbound RTB formula, open Targets / RTBs, edit the formula, and find Timeout Settings → RTB timeout (ms). This sets the maximum aggregate time across all formula steps before the bid fails.

For formulas in an RTB group, also review the group’s Ping Timeout (ms) and any formula-level Timeout Override (ms).

These controls are not the publisher’s response deadline or the destination’s call ring timeout. Review the applicable configuration before changing them.

Shorter timeouts can reduce waiting but can also discard useful bids. Longer timeouts allow more response time but may exceed the requesting system’s deadline.

Investigate a slow request

For the diagnostic workflow, see How to troubleshoot high RTB processing time.

If the main symptom is no bid, start with How to Troubleshoot No Bid Responses to distinguish request rejection, unavailable destinations, buyer rejection, and timeout.

When contacting Moja support, include the request ID, timestamp and timezone, campaign and publisher, observed processing time, and relevant response or error. Redact credentials and unnecessary personal information.