Ad requests allowing header bidding trafficking rejection reasons
Review the following table to understand the rejection reasons found under the "Ad requests allowing Header bidding trafficking" 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 byand select a rejection stage.
| Rejection reason | Suggested action | Rejection stage |
|---|---|---|
| View how to fix policy issues that affect ad serving. | ||
| 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 . | ||
|
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). | |
| Set up templates for native inventory. Learn more about native ad settings . | ||
| Contact your account manager to determine if your apps should be allowed to serve offline ad requests. | ||
| No action recommended. | ||
| To learn more, visit Header bidding trafficking . | ||
| Review your First Look and other pricing rule configurations. | ||
| No action recommended. | ||
| Review your blocks on advertisers or advertiser URLs . | ||
| Review your category protections . | ||
| Try your keywords on Google Web Search . | ||
