Troubleshoot callout filtering

In addition to bid response filtering based on Google filters, mismatches between your bid and publisher configurations, or simply because of auction dynamics, your bids may be filtered because of an error or misconfiguration with your callout.

Callout filters
Bid response callouts return a status when filtered from the auction, allowing you to troubleshoot potential errors. We list status codes here, with corresponding troubleshooting steps and additional information.
Internal error An internal Authorized Buyers HTTP infrastructure failure occurred. There could be multiple reasons causing this (for example, there was a failure sending a bid request, a setup failure, or the request may have been too large). This filtering reason corresponds to callout status code 2. Expand all  Collapse all Learn more about what you can do Contact your account team if this number exceeds 10%.
Unknown status This status covers a few rare situations that could indicate a potential bug in Authorized Buyers. This filtering reason corresponds to callout status code 4. Learn more about what you can do Contact your account team if this number exceeds 10%.
Out of quota The bidder endpoint maximum QPS has been reached. This filtering reason corresponds to callout status code 5. Smart Throttling for Bidders optimizes for bid requests on which you are most likely to bid. Learn more about what you can do Verify that you are not using HTTP endpoints for matches that require HTTPS. Unless you are in China, you need to bid using HTTPS. Refine your pretargeting settings so you’re receiving only traffic that you intend to bid on. Increase the maximum QPS on your endpoints if you have capacity to handle more bid requests. Ensure your network error rate is less than 15%.
Bidding endpoint not configured The bidding endpoint has not ben configured. This filtering reason corresponds to callout status code 29. Learn more about what you can do Verify that you are not bidding in a location where you don't have an endpoint (for example, you are buying EMEA traffic but you don't have EMEA server endpoint set). Your technical team should verify this prior to contacting your account team.
Throttled due to high response error rate The bid request rate is exceeding the calculated error quota limit. This filtering reason corresponds to callout status code 30. Learn more about what you can do Verify that your network error rate is less than 15%.
Predicted to be ignored This is the result of an attempt by Authorized Buyers to maximize your bidder's profits. This filtering reason corresponds to callout status code 6. Learn more about what you can do This is a normal and expected occurrence. You should not need to do anything, but you can contact your account team with any questions.
Callout HTTP request timed out The callout HTTP request timed out. This filtering reason corresponds to callout status code 7. Learn more about what you can do You can learn how to avoid closed connections using the Best Practices for RTB Applications or the guide to Latency Restrictions and Peering.
HTTP response contained no data Your bidder may not be returning a valid response. This filtering reason corresponds to callout status code 8. Learn more about what you can do Review the guide to build the response guide and ensure that you're returning a valid response. If you do not wish to bid on an impression, you can set the processing_time_ms field and leave all of the other fields empty.
HTTP response could not be parsed The HTTP protocol may not be implemented correctly. This filtering reason corresponds to callout status code 9. Learn more about what you can do Review the guide to build the response and ensure that you're returning a valid response.
Unknown HTTP status code or TCP error Authorized Buyers detected an unknown HTTP status code or TCP error. This filtering reason corresponds to callout status code 10. Learn more about what you can do Review the best practices for RTB applications and ensure that you're managing connections and handling errors appropriately.
Bidder returned an HTTP 3xx status code Your bidder returned an HTTP status code indicating a redirect. This filtering reason corresponds to callout status code 11. Learn more about what you can do Review the best practices for RTB applications and the recommendations for handling latency restrictions and peering to avoid HTTP errors.
Bidder returned an HTTP 4xx status code Your bidder returned an HTTP status code indicating a client error. This filtering reason corresponds to callout status code 12. Learn more about what you can do Review the best practices for RTB applications and the recommendations for handling latency restrictions and peering to avoid HTTP errors.
Bidder returned an HTTP 5xx status code Your bidder returned an HTTP status code indicating a server error. This filtering reason corresponds to callout status code 13. Learn more about what you can do Review the best practices for RTB applications and the recommendations for handling latency restrictions and peering to avoid HTTP errors.
Bid response too large Your bid response is greater than the acceptable limit. This filtering reason corresponds to callout status code 15. Learn more about what you can do The default size limit for a bid response is 100 kB. If you believe you have a valid business reason for sending inflated bid responses, you can contact your account team to increase this limit.
BidResponse proto could not be parsed Your bidder is either using the Authorized Buyers bidding protocol or the OpenRTB protocol and the HTTP payload is not a valid response. This filtering reason corresponds to callout status code 16. Learn more about what you can do Review the current version of the RTB protocol, or the OpenRTB protocol and ensure that you're returning a valid bid response.
DNS lookup failed The host server for your bidding endpoints could not be found. This filtering reason corresponds to callout status code 17. Learn more about what you can do Ensure that the DNS record for your bidding endpoints is up to date and configured correctly.
All ads in response filtered This could either be due to serving problems, creative disapprovals, or a combination of both. This filtering reason corresponds to callout status code 18. Learn more about what you can do You can view the status of your creative approvals and get detailed information on why creatives were disapproved in the Creatives section, or get a breakdown of your ad and snippet statuses using the snippet status report.
Testing mode was enabled Your bidder is likely working correctly, but set to testing mode. This is a step in the bidder turn up procedure when Authorized Buyers processes your response normally, but then drops all ads prior to the auction. This filtering reason corresponds to callout status code 19. Learn more about what you can do Contact your account team to disable testing mode.
No ads returned with bid response Your bidder returned a "no-bid" bid response. This filtering reason corresponds to callout status code 20. Learn more about what you can do This is a normal and expected occurrence. You should not need to do anything; this is a correct way to refrain from bidding.
SSL certificate error Your bidder is bidding using HTTPS and the SSL certificate is invalid. This filtering reason corresponds to callout status code 21. Learn more about what you can do Review the SSL implementation guide and ensure that your SSL certificate is valid.
Conditional ad policy violation Your creative is being filtered because the context of the inventory was incompatible with ad content, according to ad policy. This filtering reason corresponds to callout status code 151. Learn more about what you can do Go to the Troubleshooting, and then Creatives in Authorized Buyers to check the details of the creative and fix any policy issues found.  If detailed rejection reasons are related to Gambling or Social Casino Games, please reference our Gambling and games policy to explore certification.
Filtered by pretargeting quota The QPS limit for all eligible pretargeting groups has been reached. This filtering reason corresponds to callout status code 26. Learn more about what you can do Refine your pretargeting settings so you’re receiving only traffic that you intend to bid on. Increase the QPS limit on your pretargeting groups if you have capacity to handle more bid requests.

 

---

Learn how to troubleshoot bid response filtering.