Search
Clear search
Close search
Google apps
Main menu

DFP Small Business releases

September 19, 2016
  • Highlight
    • Ad Exchange in DoubleClick for Publishers
  • DFP Small Business releases
    • See why line items didn't deliver
    • Learn which ads did deliver and why (open beta for mobile web and deskop)
    • Mobile ad network creative type deprecation
    • Code snippet deprecation for Ad Exchange line items
    • Admin tab reorganization
  • Coming soon...
    • Limits dashboard
    • Learn which ads did deliver and why (for video and mobile apps)
    • GPT Light passback tags

Highlight

  • 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. The current Ad Exchange interface remains available and unchanged. Ad Exchange users who do not have access to DFP will not experience any change. Learn more
    Ad Exchange in DoubleClick for Publishers

DFP Small Business

  • 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

  • Learn which ads did deliver and why (open beta for mobile web and desktop)
    While the feature above lists why your line items didn’t deliver, this new feature helps you troubleshoot ad delivery in the context of inventory. The details can 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. In DFP, from the Delivery tab, click Troubleshoot in the sidebar, and then enter a URL to troubleshoot. Note that this feature is currently in open beta, is available only for mobile web and desktop, and will be fully launched soon as part of the improved DFP 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 is now largely obsolete. As a result, the Mobile ad network creative type has been deprecated in DFP. 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 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 was 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

  • Admin tab reorganization

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

Coming soon...

  • 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 (for video and mobile apps)

    The feature that helps you analyze why unexpected ads deliver (described above) will soon also have support for video and mobile apps.

  • 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 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).

If you use Ad Exchange, visit the Ad Exchange Release Notes to learn about the latest feature releases.
 
Was this article helpful?