Inquiry About creative_status_code
32 views
Skip to first unread message
edison yang
Mar 13, 2025, 2:50:46 AM
Mar 13
to Authorized Buyers API Forum
Hello Support,
We encountered the following three status codes during our testing:
- 72 Creative filtered due to publisher's advertiser exclusion settings
- 83 The ad was part of a winning passback chain and will only show if preceding requests in the chain pass back
- 119 Creative filtered by publisher's exclusion rules
We have reviewed the documentation provided by ADX but are unsure the reason and how to avoid them.
For these 3 failures, Could we get some field information from the bid request and then adjust the bid response accordingly, or are these issues caused by the publisher?
Thank you.
Edison
Authorized Buyers API Forum Advisor
Mar 13, 2025, 8:35:33 PM
Mar 13
to ironbo...@gmail.com, google-doubleclick-a...@googlegroups.com
Hello Edison,
Status codes 72 and 119 are based on the publisher's settings–for example, consider this relevant publisher-facing documentation . Your bids can be filtered due to various blocks placed by the publisher, though successful bids can still be made if you're able to avoid what the publisher blocked.
In the case of status code 72 , it sounds like the publisher blocked a buyer seat (advertiser), which can be seen via the BidRequest.wseat field. If specified, BidRequest.wseat acts as an allowlist that identifies buyers that may bid on the impression. Otherwise, it is expected that there are no restrictions on buyers that may bid.
Status code 119 is similar, but less specific. Exclusion rules are created by publishers and can refer to several different details that they seek to exclude; one example is the landing page URL (currently only observable via publisher settings files). There are a lot of fields this can refer to, but if your bidding logic is considering publisher exclusions with fields such as PublisherSettings.excluded_url , or BidRequest.bcat , we don't anticipate you would normally encounter this kind of filtering often. If you see it a lot for a specific publisher it could be that their exclusions are very broad, and it may be worth considering an adjustment to your pretargeting to avoid that publisher. If you see it non-trivially across multiple publishers though, it might warrant a closer look.
Status code 83 isn't something you can avoid with changes on your end as far as I'm aware. Describing this is going a bit beyond the scope of Authorized Buyers protocols and APIs that I cover here, but a high-level summary is that it indicates that you won the auction on our exchange, but your creative would only render (and thus be billable) if preceding links in the "passback chain" (other ad networks) didn't place an ad. It is referring to a fallback mechanism that is used to fill ad inventory.
Thanks,
Status codes 72 and 119 are based on the publisher's settings–for example, consider this relevant publisher-facing documentation . Your bids can be filtered due to various blocks placed by the publisher, though successful bids can still be made if you're able to avoid what the publisher blocked.
In the case of status code 72 , it sounds like the publisher blocked a buyer seat (advertiser), which can be seen via the BidRequest.wseat field. If specified, BidRequest.wseat acts as an allowlist that identifies buyers that may bid on the impression. Otherwise, it is expected that there are no restrictions on buyers that may bid.
Status code 119 is similar, but less specific. Exclusion rules are created by publishers and can refer to several different details that they seek to exclude; one example is the landing page URL (currently only observable via publisher settings files). There are a lot of fields this can refer to, but if your bidding logic is considering publisher exclusions with fields such as PublisherSettings.excluded_url , or BidRequest.bcat , we don't anticipate you would normally encounter this kind of filtering often. If you see it a lot for a specific publisher it could be that their exclusions are very broad, and it may be worth considering an adjustment to your pretargeting to avoid that publisher. If you see it non-trivially across multiple publishers though, it might warrant a closer look.
Status code 83 isn't something you can avoid with changes on your end as far as I'm aware. Describing this is going a bit beyond the scope of Authorized Buyers protocols and APIs that I cover here, but a high-level summary is that it indicates that you won the auction on our exchange, but your creative would only render (and thus be billable) if preceding links in the "passback chain" (other ad networks) didn't place an ad. It is referring to a fallback mechanism that is used to fill ad inventory.
Thanks,
Mark Saniscalchi
Authorized Buyers API Team
Feedback
How was our support today?
[2025-03-14 00:35:27Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02vH9M0:ref" (ADR-00293983)
Reply all
Reply to author
Forward
Search
Clear search
Close search
Google apps
Main menu
