Best practices for DoubleClick Rich Media ad serving

  • Is the latest DoubleClick iframe solution properly installed?
    See the DoubleClick iframe solution.

  • Will the ad serve to the intended site placement, rather than elsewhere on the page and then dynamically move?
    We support ad-tag implementation directly on the site. If there's a problem with a rich media unit that's being dynamically served into the site placement, it's up to the site to address it. Our teams are always willing to help you troubleshoot but are not responsible for the methods that a site uses to serve a rich media unit dynamically on a page.

  • Does the creative click through properly, including any site-side click strings that may run?
    For more information, see the Click-through troubleshooter article.

  • To avoid certain issues with iframes, we recommend that you implement JavaScript tags for rich media.

  • Because our creatives are set to a high z-index default (999999-1000000) to avoid expansion issues, we recommend that you set any site-side drop down-menus (or float units) to a z-index higher than 1000001.
    This will ensure that drop-down menus expand properly over rich media. (For more information, see Site navigation drop-down menus are expanding under my rich media.)

  • Be aware of any container divs that the ad is placed with...
    ...divs that use the style attribute overflow:hidden;. It's recommended that you change this to overflow:visible;. (For more information, see Expanding ad isn't expanding out of placement or over webpage.)

  • Does the issue occur when the tags are placed directly on the page?
    DoubleClick doesn't support custom publisher implementations that move ads into place on a webpage. Examples of unsupported implementations include using DOM methods like appendChild and innerHTML to move ads around the page and dynamically writing an ad with custom JavaScript.

    In these scenarios place the ad tag directly on the page and confirm the issue. If the issue persists, contact DoubleClick support. If the issue is resolved, then it's a problem on the publisher's side.