How to Troubleshoot No Bid Responses
Identify why an inbound RTB request receives no bid, distinguish buyer rejection from request errors, and use Moja’s request details to find the next action.
Start with the request outcome
Section titled “Start with the request outcome”A no-bid result means the request did not produce an accepted bid. It does not, by itself, identify the cause.
First distinguish between:
- An inbound request that was rejected or limited.
- A request with no eligible destinations.
- A downstream buyer that returned no bid or failed to respond in time.
- A bid or allocation that did not result in a call.
An empty or failed RTB formula test is not automatically a buyer no-bid response.
Find the request in Moja
Section titled “Find the request in Moja”Open Reporting and locate Inbound RTB Life Logs. Select the relevant date range and campaign or publisher filters, then expand the affected request.
Review the available tabs:
- Life Log: inspect the processing sequence and recorded reasons.
- Response: inspect the response returned for the inbound request.
- RTB Requests: inspect downstream RTB steps and their responses.
- Allocations: check whether the request produced an allocation.
Record the request ID and timestamp, including the timezone. If you cannot find the request, check the endpoint and reporting filters before assuming it reached Moja.
Common causes and what to check
Section titled “Common causes and what to check”Missing or incorrect request data
Section titled “Missing or incorrect request data”Compare the actual request with the endpoint’s integration requirements. Check caller ID and any required ZIP, state, sub-ID, or consent fields.
Verify parameter names, values, and mappings. A field present in the publisher’s system may still be absent from the request received by Moja.
Use the actual response or Life Log reason; rejection wording varies by integration.
Caller ID or geographic targeting
Section titled “Caller ID or geographic targeting”Confirm the caller ID uses the format required by the endpoint. Check ZIP, state, and any area-code targeting against the campaign and destination configuration.
Do not change location or consent data merely to obtain a bid. Correct the request or use destinations that accept the actual traffic.
Availability, filters, and caps
Section titled “Availability, filters, and caps”Check that the campaign and intended destinations are active and available for the request’s time and targeting.
Review the applicable routing plan or call flow, destination membership, filters, schedules, and volume, spend, or concurrency limits.
Use the request details to distinguish a destination excluded before a buyer request from a buyer that received the request and declined it.
Price or payout conditions
Section titled “Price or payout conditions”If the request details identify a price-related rejection, compare the requested price and applicable payout conditions with the configured integration.
Confirm the expected currency and units. Do not increase payouts or change pricing based only on a low bid rate.
Duplicate or suppression checks
Section titled “Duplicate or suppression checks”If the recorded reason identifies duplicate traffic or a suppression/compliance check, review the applicable rule and its scope.
Avoid repeatedly testing the same caller where duplicate rules apply. Use an authorized test caller and valid test data. Do not bypass compliance checks to force a bid.
Slow or failed buyer requests
Section titled “Slow or failed buyer requests”In the request’s Life Log and RTB Requests tabs, inspect the affected step, response, and available timing information.
Distinguish a timeout from an explicit buyer no-bid response. Check the endpoint and integration with the buyer before changing timeout settings.
Invalid RTB formula URLs
Section titled “Invalid RTB formula URLs”For downstream RTB formulas, open the formula under Targets / RTBs and review each request URL.
Correct whitespace in the URL path or query-parameter names. Moja displays validation errors and blocks testing or saving affected steps until corrected.
Do not indiscriminately remove spaces from query values; preserve the values required by the buyer’s integration.
Inbound publisher request limits
Section titled “Inbound publisher request limits”In the campaign’s Inbound RTB Publishers section, check the publisher’s Rate limit and the actual request frequency.
The current editor requires a whole number from 1 to 10 requests per minute, with a default of 10 for new entries. Older entries may display legacy values that need correction before saving.
Check the actual request response for evidence of throttling. A rate-limit rejection is not evidence that a downstream buyer declined the call.
Retest and escalate
Section titled “Retest and escalate”After correcting the identified issue, send a controlled test using valid data and inspect the new request.
Compare its request data, processing events, response, and allocations with the original. A bid alone does not establish that a call connected.
If the cause remains unclear, send Moja support:
- Request ID and timestamp with timezone.
- Campaign and publisher.
- The observed response or error.
- Expected outcome and the change already tested.
Redact API keys, authentication tokens, and unnecessary personal data before sharing request examples.