Ad requests allowing programmatic rejection reasons
Review the following table to understand the rejection reasons found under the "Ad requests allowing programmatic" card in Ads traffic navigator.
Here's a breakdown of what you can view in each column:
- Rejection reason: This column describes the rejection reason in detail.
- Suggested action: This column suggests actions you can take to resolve the rejection reason. If there's no suggested action, the entry shows "No action recommended."
Rejection stage: This column indicates the rejection stage in a card's visualization where you'll find the rejection reason.
To filter the table:
- Click Filter with a few keywords, and enter one or more keywords in the search box.
- Click Narrow by and select a rejection stage.
| Rejection reason | Suggested action | Rejection stage |
|---|---|---|
| Google policy issue Programmatic ads can't serve to this request due to Google policy. | View how to fix policy issues that affect ad serving. | |
| Unspecified No additional details are available. | No action recommended. | |
| App open ads blocked "App open" ads are not allowed for this publisher. | If your app is in Google Play’s Designed for Families program, it isn’t eligible for app open ads. Learn more about trafficking app open ads. | |
| Offline ads blocked An offline ad request was blocked because the publisher has not been enabled. | Contact your account manager to determine if your apps should be allowed to make offline ad requests. | |
| Native request not using MediaView for main asset Programmatic native ads using native advanced must use MediaView (not ImageView) for main image assets. | Review the Mobile Ads SDK developer documentation for native advanced (Android). | |
| Native templates missing The request was missing a native template. | Set up templates for native inventory. Learn more about native ad settings. | |
| App not set up The app can't serve ads because it isn't set up in Ad Manager. Learn more about setting up an app in Ad Manager. | Finish setting up the app. | |
| Buyer blocked in regulated US states The buyer is not one of your active ad partners in regulated US states. | Review your US state regulations settings and the partners that help to show ads on your site or app. | |
| App missing SDK rendering support The app is unable to use the third-party SDK. | Review and update your SDK bidding configuration as needed. | |
| App missing creative SDK The app does not support a third-party SDK required by the buyer. | Install the buyer’s SDK into your mobile app and configure SDK bidding. | |
| Bidder configuration The bid request was not sent due to buyer configuration. | You may want to contact the buyer to make them aware of the issue. For more details, try troubleshooting Open Bidding health issues, or Authorized Buyer bid response troubleshooting. | |
| Buyer needs user ID The bidder requires a user ID, but none was available. | Consider configuring user identifiers and allowing them to be sent to buyers. | |
| Unconsented buyer Bid requests can only be sent to buyers with whom users have consented to share data. | Be sure to clearly identify each party with whom data will be shared. Learn more about ad technology providers and how to comply with the EU user consent policy. | |
| Buyer needs app ID The bidder requires an app ID, but none was available. | You may want to contact the buyer to make them aware of the issue. For more details, try troubleshooting Open Bidding health issues. | |
| Secure signals needed Secure signals required by the bidder were not available. | Learn how to troubleshoot your secure signal setup. | |
| Bidder error The bid request was skipped due to previous bid response errors. | You may want to contact the buyer to make them aware of the issue. | |
| Request missing ad unit mapping The ad request’s ad unit is not mapped to the SDK bidder. | Learn more about ad unit mapping for SDK bidding. | |
| Buyer blocked for LGPD The bidder is not eligible for LGPD-applicable requests. | To view certified providers, visit Ad Technology Providers for the LGPD. For a more general overview, visit Helping users comply with the Lei Geral de Proteção de Dados (LGPD). | |
| Inventory context needed The bid request was skipped because the bidder requires information about the site or app showing the ad, which is not provided. | You may want to contact the buyer to make them aware of the issue. For more details, try troubleshooting Open Bidding health issues. | |
| Unspecified No additional details are available. | No action recommended. | |
| All blocked by buyer protection All buyers represented by a bidder are blocked. | Review buyers you have blocked through Protections or the Ad Review Center, and update as needed. | |
| Network error skipped request The system didn't send the bid request due to a network error. | This is likely a temporary issue. | |
| Bidder timeout The bid request timed out waiting for a bid response. | You may want to contact the buyer to make them aware of the issue. | |
| Invalid response The bid request returned an invalid response. | You may want to contact the buyer to make them aware of the issue. | |
| Network error There was an error sending the bid request. | This is likely a temporary issue. | |
| Buyer behavior: Bidder did not bid The bid request returned a valid response, but without any bids. | Please contact the buyer for further information. | |
| Duplicate in pod The creative was rejected because it is already in the pod. | Review requirements for creatives in optimized pods. | |
| Blocked by category protection One or more detected categories were excluded by the publisher through protections. | Review your category protections. | |
| Open Auction blocked Open Auction backfill is not allowed for the request, and this bid is not First Look or a deal. | Check requirements for Open Auction and other transaction types. | |
| Unconsented creative vendors The user did not consent to vendors detected to be called by this creative. | You may want to review how consent is gathered and passed. | |
| Publisher blocked via Ad Review Center Creative was blocked in the Ad Review Center by the publisher. | Review blocked creatives in the Ad Review Center, and allow creatives as desired. | |
| VPAID blocked by publisher The creative is disallowed because it calls out to a vendor that the publisher has not opted in to, or that is not fully compliant. | In Protections, review your Interactive video ads (VPAID) opt-in. | |
| User data usage blocked by protection The creative is disallowed. It uses user data in a way that the publisher has blocked via ad content protections. | Review blocks for data uses. | |
| Bid below publisher floor The bid was below a publisher-configured floor. | Review your First Look and other pricing rule configurations. | |
| Required DSA in-ad transparency information missing The Digital Services Act requires that transparency information be shown for this bid, but it's unavailable. | Review Supporting the Digital Services Act. | |
| Blocked by competitive exclusion The creative is disallowed because it conflicts with a creative already selected for another slot on the page, which would violate a publisher competition protection. | Review competition protections. | |
| Video creative filtered The video was filtered because it historically had a high error rate or very low view rate. | Buyers need to resolve the issue. If you see very high spikes of this period-over-period, you can contact the Authorized Buyer. | |
| Blocked by Ad experience Protection The creative is blocked by an Ad experience Protection. | Review your Ad experience Protections. | |
| Blocked by advertiser protection The advertiser or its creative URL was blocked by the publisher. | Review your blocks on advertisers or advertiser URLs. | |
| Blocked by buyer protection The buyer who submitted this bid is blocked. | Review buyers you have blocked through Protections or the Ad Review Center, and update as needed. | |
| Creative URL not yet reviewed by Google Before an ad can be shown, the landing page URL needs to be crawled and reviewed by Google. | Check back in a few hours, as the filtering should disappear. If it remains, you can try contacting the buyer to make them aware of the issue, sharing this link with them. | |
| Ad format blocked by deal The bid is filtered because it doesn't match the format of the chosen deal. | Buyers need to resolve the issue. If you want to contact buyers so they’re aware of the issue, you can include this link to the Authorized Buyers Help Center. | |
| Google creative policy violation The creative can't serve due to Google policy. | Review Google Policy guidelines, or creative restrictions. | |
| Request vs creative property mismatch The creative is not compatible with the ad request. | Various reasons may apply, such as SSL compatibility. | |
| Blocked by language protection The creative’s language has not been allowed by the publisher. | In Protections, review your Languages opt-in. | |
| Bidder error The bid is ineligible because of a bidder error. | Buyers need to resolve the issue. | |
| Conflict with ad in pod The creative can't be served along with another ad selected for the pod due to a competitive exclusion. | Review competition protections. | |
| Non-fully compliant creative blocked by publisher The creative is disallowed because it has unknown behavior or is not fully compliant, and the publisher has not opted in to such creatives. Note: This currently only includes video ads that don't adhere to the Out-stream video ad policy. | In Protections, review the Ad experience opt-in "Allow unknown or minimum platform policy compliance only ads." | |
| Unspecified No additional details are available. | No action recommended. | |
| Blocked by video settings Video settings prevented the ad from serving. | Review your video settings to ensure your skippable, non-skippable, and audio values are as intended. | |
| Try your keywords on Google Web Search. | ||