How to fix rejected ad request errors

Do you received “rejected ad request” in your adsense account ? If you google, many publisher around the world received similar alerts in their adsense account. Many of the adsense publisher received this alerts in their adsense dashboard.

The errors listed below will result in blank ads being displayed on affected pages starting August 15, 2012. Please make sure that you fix these errors before then.  The following ad units have made ad requests with incorrect site information. This occurs when the URL of the server from which the ad unit has been served differs from the URL of the actual page where the ad will be displayed.

Eventhough Google has provides guidelines How to fix rejected ad request errors, but many publishers still unsure how to solve this problem and most of the error are at wordpress platform.

According to Google, if you see rejected ad request errors, this means  your ad unit is crawling and targeting the wrong URL.  This occurs when our URL detection has determined our ad unit is within an iframe, and has no content. This results in lower relevancy for your ads and lower revenue as we do not know the actual content of your page. As a result, google will serve “blank ads” that blend into the background of your pages.

There are two reasons given by Google why this error occur :

• Your ad code is nested within multiple iframes.
• You’re using a Supply-Side Platform (SSP).

Google has also provides few options to solve rejected ad request errors.  We received the same options as well however until now, we havent 100% sure yet how to solve this using “google_page_url = “http://myurl.com/fullpath”

The method for fixing targeting depends on the domain that triggers the ad request error. In general, to fix these errors in AdSense and Ad Exchange, you will need to pass to AdSense and Ad Exchange, the URL of the actual page where your ad unit is located in the ad request.

• If using DoubleClick for Publishers, please look into the following solutions:
  • If using DART, you can pass the correct URL using the dc_ref parameter in conjunction with the google_page_url parameter in AdSense and Ad Exchange. For more information, access the DART for Publishers Help Center .
  • If using Google Ad Manager, you can pass the correct URL by adding the following syntax to your DFP ad call:
    GA_googleAddAdSensePageAttr("google_page_url", "URL");
  • If using Google Publisher Tags, you can pass the correct URL by adding the following syntax to your DFP ad call:
    googletag.pubads().set("page_url", "URL");
  • If you have a mobile app, and are running AdSense and/or Ad Exchange web tags, you’ll need to switch those tags for the AdMob SDK .
• If you have tag.admeld.com errors within your report, please contact your Admeld representative and ask for JavaScript tags as opposed to iFrame tags. This will remove the nesting iframe effect and should improve the targeting.
• For all other domains, you will need to use google_page_url to target the correct URL.

Typical ad code:
<script type=”text/javascript”>
google_ad_client = “ca-pub-XXXXXXXXXXXX”;
/* 728×90, creado 14/04/08 */
google_ad_slot = “XXXXXXXXXXXX”;
google_ad_width = 728;
google_ad_height = 90;
</script>
<script type=”text/javascript”
src=”//pagead2.googlesyndication.com/pagead/show_ads.js”>
</script>

Ad code with google_page_url added:
<script type=”text/javascript”>
google_ad_client = “ca-pub-XXXXXXXXXXXX”;
/* 728×90, creado 14/04/08 */
google_ad_slot = “XXXXXXXXXXXX”;
google_ad_width = 728;
google_ad_height = 90;
google_page_url = “http://myurl.com/fullpath”;
</script>
<script type=”text/javascript”
src=”//pagead2.googlesyndication.com/pagead/show_ads.js”>
</script>

There are many discussion on How to fix rejected ad request errors, but most of the discussion end without any solution. Google has also created guideline How to fix misconfigured ad request notifications.

If you know how to fix rejected ad request errors, we would appreciate if you could share with us how to handle it. Tq