Ad requests with targeted line items rejection reasons
Review the following table to understand the rejection reasons found under the "Ad requests with targeted line items" 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 |
|---|---|---|
| Line item displayed max times on page/stream/pod The line item served the maximum allowable times on a page, stream, or pod, as configured on the line item or ad rule. | Learn how to control the display of creatives on a line item. | |
| Below pricing floor Remnant line item price is below the specified floor for this request. | Learn more about pricing rule floors. | |
| Unconsented creative vendors The user has not consented to one or more vendors present in the creative. | Learn about checking RTB creatives for user consent and the reservation vendor filtering option. | |
| Invalid creative configuration Your buyer's creative is invalid. | Work with the advertiser, or examine the creative's settings if it's publisher hosted. | |
| Unfilled redirect A third-party line item did not return a creative. | Contact the advertiser to learn why it's not returning a creative. | |
| Unavailable pod position targeting The request could not accommodate the line item's pod position targeting. | The line item was unable to serve due to its position targeting within a video pod. For example, it may target position 1, which was occupied by a higher-value line item, while the targeting restricts it from serving to another empty position. This is generally working as intended, but you may want to consider relaxing the pod position targeting of the line item. | |
| Unfilled VAST redirect A VAST redirect did not return a creative. | Contact the advertiser to learn why it's not returning a creative. | |
| Sequential rotation creative unavailable Sequential rotation stops working correctly if any creative set to rotate can’t serve to the impression. When the next creative in the sequence is unable to fill an ad slot, the line item stops serving until the next time period begins. | Learn more about the non-delivery cause "next creative in rotation not available." | |
| Required companion ad unavailable The line item has a required companion ad, but the ad request could not accommodate it. | Review companion delivery settings for the line item. | |
| Unable to accommodate storyboard The line item is a storyboard, but the stream could not accommodate it. | Review storyboard setup. | |
| Exclusion labels / same creative exclusion The ad did not serve due to exclusion labels, or because the creative was already served on the page view. | Learn more about non-delivery due to exclusion labels or same creative exclusion. | |
| Frequency cap reached This non-delivery cause means that a frequency cap on the number of times the ad or format can be used has been reached. | Check the frequency caps set for this line item and make sure that they’re not overly restrictive. | |
| Blocked by video settings Video settings prevented the line item from serving. | Learn more about configuring optimized pods. | |
| Line item ahead of schedule To get as many of your campaigns as possible to complete, Ad Manager allocates impressions to other campaigns when the line item is on or ahead of the schedule to meet its target. | No action required: the line item is delivering on schedule and working as intended. | |
| User identifiers unavailable for frequency capping User IDs were unavailable for frequency capping, and caused a line item with a frequency cap to be excluded from serving. | Learn more about frequency capping eligibility. | |
| Roadblocks prevented delivery The line item could not serve due to roadblock settings. Either the line item is a roadblock that could not serve all creatives, or another roadblock line item needed to serve. | Consider changing the order of requests on your page, or using Google Publisher Tags with a single-request architecture callout. Learn more about troubleshooting line item delivery. | |
| Google creative policy violation The creative can't serve to this request due to Google policy. | Review Google Policy guidelines, or creative restrictions. | |
| Unspecified No additional details are available. | No action recommended. | |
| Not selected to compete For each ad request, all eligible line items are compared against each other, and one (or a few in some cases, such as video pods) is selected to compete in the auction. All other eligible line items are not selected to appear and are counted here. | Generally, this is working as intended, as Ad Manager selects line items to serve based on their schedule and priority. To confirm that a line item has sufficient inventory, use Ad Manager forecasting, or learn more about troubleshooting line item delivery. | |
| Creative not retrieved Programmatic Guaranteed and Preferred Deal line items are compared along with other eligible line items. In addition to being selected, their creative must be retrieved from the deal’s buyer. This counts deals that were unable to retrieve valid creatives. | This rejection reason is typically caused by the deal’s buyer failing to bid on the deal, or the bid being rejected. If this happens, the specific reason should appear in the programmatic flow. | |
| Try your keywords on Google Web Search. | ||