Fix Ad Exchange rejected ad requests

What to do when alerted that ad requests are rejected

Ad requests are rejected when your ad unit targets the wrong URL. When Google can't determine the correct site information for an ad request, "blank ads" that blend into the background of your pages are served. This results in lower relevancy for your ads and lower revenue as we do not know the actual content of your page.

How to know if ad requests are being rejected

Google Ad Manager notifies you when ad requests are being rejected. Click the link in the alert to see how many ad requests were rejected. If the total number is low, your revenue is likely unaffected. However, if you're seeing rejected ad requests in the tens of thousands or if you can't see ads on your site because of rejected ad requests, then we'd recommend implementing one of the solutions below.

Common reasons ad requests are rejected

Ad requests are rejected when your ad unit is within an iframe, and has no content. Here are some possible reasons you're seeing these errors:

Your ad code is nested within multiple iframes: If your ad code is nested within multiple iframes, Google can't determine the correct site information for an ad request.
You're using a Supply-Side Platform (SSP): If you make use of a Supply-Side Platform, such as a third-party ad server or yield manager, for ad optimization and you're receiving rejected ad request errors with their URLs, contact the Supply-Side Platform to ensure the correct site information is passed in your ad requests.

Fix rejected ad requests from googleads.g.doubleclick.net

If the requests transact through Google Ad Manager, consider using the Rich Media iframe solution.

For other Ad Exchange requests, follow these steps:

Create a folder in your website's root directory named /doubleclick
Download DARTiframe.html and save it to the new /doubleclick folder in your root directory

If successful, your rejected ad request alerts should disappear within 3-5 days. If your rejected ad requests persist after 5 days, then unfortunately there is no further action you can take. Our engineers are aware of the issue, and are working on a solution.

Fix rejected ad requests from all other domains

If the requests transact through Google Ad Manager, use one of the solutions below:

If using Google Publisher Tags, pass the correct URL by adding the following syntax to your Ad Manager ad call, replacing "URL" with your own URL: googletag.pubads().set("page_url", "URL");
For a mobile app running web tags, switch tags to the AdMob SDK.

For other Ad Exchange requests, use google_page_url to target the correct URL. If you use asynchronous ad code on your site, use data-page-URL to target the correct URL.

Synchronous code example

<script type="text/javascript">

    google_ad_client = "ca-pub-XXXXXXXXXXXX";

    /* 728x90, 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>

Asynchronous code example

<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.example.com"> </ins> 

    <script>

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

    </script>

For both of these examples, make sure you replace http://myurl.com/fullpath or http://www.example.com with your own URL.

Was this helpful?

How can we improve it?