How to Fix a Rejected Ad Request Error in Ad Exchange

This post was most recently updated on August 23rd, 2019

Ad requests errors are naturally bad for your business. When Ad Exchange detects an ad unit targeting a wrong URL, it results in a rejected ad request. In effect, Adx will serve blank ads – empty ads that blend into your site’s background. When there are too many rejected ad requests, you won’t see ads on your site! Ad Exchange reports these errors via alerts in your account. Click on the alert link to see how many of these were accounted for.

The revenue impact is huge if rejected ad requests happen in tens of thousands for your site. As mentioned earlier, it can mean that you won’t be able to see any ad on your pages. Two main reasons cause rejected ad requests. One is when your content is contained in an iframe. The ad code inside an iframe is not detectable by Google – hence ad information cannot be determined. The second reason is when you’re using an SSP or a Supply-Side-Platform (i.e. ad server). In this case, contact your SSP provider to make sure the right site information is fed to your ad requests.

In order to resolve this for Ad Exchange publishers, follow the three options below:

Note: The method used to fix rejected ad requests depend on the domain that cause the errors; and the type of ad code used. In this article, we will cater to Adx publishers.

1) Ad Request Errors from googleads.g.doubleclick.net

• First, you need to create a folder in your site’s root folder, and name it as: /doubleclick
• Go to //storage.googleapis.com/support-kms-prod/SNP_2621920_en_v3 to download the file: DARTIframe.html
• Upload DARTIframe.html file inside the /doubleclick folder

Once done properly, in 3-5 days you will no longer get alerts about rejected ad requests. If the errors continue to show up after 5 days, there is no recommended course of action to take. Rest assured, Doubleclick engineers are working out a fix for you.

2) Ad Request Errors from other domains

If your rejected ad requests come from other domains that do not use googleads.g.doubleclick.net, your option is to use google_page_url to target the right URL. If you’re using the synchronous ad code, this is how you can add google_page_url to your ad code:

The synchronous ad code looks like this:

<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>

This is how your ad code will look like once google_page_url is 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://domain.com/fullpath”;

</script>

<script type=”text/javascript”

src=”//pagead2.googlesyndication.com/pagead/show_ads.js”>

</script>

Note: Make sure you replace http://domain.com/fullpath with your own website URL. Also, all your ad units should reflect the newly-updated code if they returned rejected ad requests.

3) Ad Request Errors from other domains using the asynchronous ad code

If you are now using the asynchronous ad code, you will have to use the data-page-URL to point to the correct URL. Here’s how to add data-page-URL into your ad code:

If you use asynchronous ad code on your site and you see rejected ad requests in your reporting from anywhere else other than googleads.g.doubleclick.net, you’ll need to use data-page-URL to target the correct URL.

If you’re using asynchronous ad code, see below for how to add the data-page-url to your ad code:

The asynchronous ad code looks like this:

<script async src=”http://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js”> </script>

<ins class=”adsbygoogle”

style=”display:inline-block;width:300px;height:250px”

data-ad-client=”ca-pub-xxxxxxxxxxxxxxxx”

data-ad-slot=”6440411535″>

<script>

(adsbygoogle = window.adsbygoogle || []).push({});

</script>

Now this is how you ad code will look like once data-page-URL is integrated:

<script async src=”http://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js”> </script>

<ins class=”adsbygoogle”

style=”display:inline-block;width:728px;height:90px”

data-ad-client=”ca-pub-xxxxxxxxxxxxxxxxxx”

data-ad-slot=”xxxxxxxxxx”

data-override-format=”true”

data-page-url = “http://www.domain.com”> </ins>

<script>

(adsbygoogle = window.adsbygoogle || []).push({});

</script>

Conclusion

Note: Make sure you replace http://www.domain.com with your own website URL. Also, all your ad units should reflect the newly-updated code if they returned rejected ad requests.

Read more about Ad Exchange on this page.

If you need further assistance in resolving your rejected ad requests, contact our Support Team. Sign up free as an Adx Publisher with MonetizeMore to get personalized help and better ad revenue-generating strategies.

---

Related Posts:

• Troubleshoot DFP with the Google Publisher Console
• Common AdSense Crawler Issues and How to Fix Them
• Why are Blank Ads Appearing?