Clear search
Close search
Google apps
Main menu

DFP Premium and Ad Exchange Sell releases

September 19, 2016
  • Highlight
    • Ad Exchange in DoubleClick for Publishers
  • DFP Premium releases
    • See why line items didn't deliver
    • Mobile ad network creative type deprecation
    • Code snippet deprecation for Ad Exchange line items
    • View mobile audience segment composition
    • Admin tab reorganization
  • Coming soon...
    • Limits dashboard
    • Learn which ads have delivered and why
    • GPT Light passback tags
    • Changes to DFP Data Transfer


  • Ad Exchange in DoubleClick for Publishers

    Users with access to both Ad Exchange and DoubleClick for Publishers can now enjoy access to Ad Exchange product features in the DoubleClick for Publishers interface. This streamlines the user workflow and reduces the need to access separate products. Ad Exchange users who do not have access to DFP will not experience any change. The current Ad Exchange interface remains available and unchanged. Learn more
    Ad Exchange in DoubleClick for Publishers

DFP Premium

  • See why line items didn’t deliver

    The “Non-delivery causes” tool provides detailed information on the delivery patterns of your line items for the past 7 days. It explains why a line item that was eligible for an ad request didn’t deliver. To access this tool, navigate to the line item in DFP and click the new Troubleshoot tab. This launch is the first of many you’ll see over the coming weeks to improve troubleshooting tools. Learn more

  • Mobile ad network creative type deprecation

    The Mobile ad network creative type allowed publishers to traffic ad network tags that were called server-side by DFP. However, with the widespread availability of Mediation, this creative type became largely obsolete. As a result, the Mobile ad network creative type has been deprecated. All deprecated creatives will remain in DFP indefinitely for historical reporting purposes.

    If your network was using it, we recommend discussing your options with DFP support, such as re-trafficking with an alternative creative type.

  • Code snippet deprecation for Ad Exchange line items

    The Ad Exchange "code snippet" text box in creative settings for Ad Exchange display/mobile line items has been removed, as well as the "channels" and "Ad Exchange Tag ID" text boxes for Ad Exchange video line items, for publishers who aren't already using these fields. The code snippet is no longer needed, as you can now use Ad Exchanges rules to target DFP inventory (such as ad units, placements, and key-values) instead. This is part of an eventual deprecation of this field for all publishers. Learn best practices for trafficking Ad Exchange in DFP

  • View mobile audience segment composition

    New columns added to the Audience segments table in the Inventory tab allow you to see a breakdown of the types of mobile device identifiers that compose each audience segment. Learn more

  • Admin tab reorganization

    The settings and features within the Admin tab have been reorganized for better usability. No setting or features have been removed as part of this change.

Coming soon...

  • DFP Limits dashboard

    The limits dashboard allows network administrators to view the system maximums and limits that apply to your network and whether you're close to reaching them.

  • Learn which ads did deliver and why

    This feature will help you troubleshoot ad delivery in the context of inventory. The details will answer which ads delivered on your page, why these ads delivered and not others, which line item would deliver if you were to request the ad slot again, and more. It will be part of the improved DFP troubleshooting tools.

  • GPT Light passback tags

    GPT Light passback tags are optimized for speed, while retaining most features of Standard GPT passbacks: compact syntax, key-value targeting, click tracking, page URL overrides, and category exclusions. They use simpler, declarative syntax and typically have lower latency than Standard GPT passback tags, which may reduce discrepancies with third-party ad servers. Learn more about GPT Light passbacks

    GPT Light passback tags support only one size per ad unit. For multi-size ad requests, consider using Standard GPT passback syntax instead. GPT Light should only be used for passback tags; for any other situations, please use Standard Google Publisher Tags (GPT).

  • Changes to DFP Data Transfer
    • New DFP Data Transfer field

      We've now added a way for you to measure your revenue from inventory trafficked in DFP but actually monetized by Ad Exchange or AdSense. This information is then exposed via DFP Data Transfer in a new column called EstimatedBackfillRevenue. 

    • DoubleClick First Look in DFP Data Transfer

      All "First Look" impressions will soon be identified as such in the Product column in DFP Data Transfer.

Was this article helpful?