Tag Archives: dfp_api

Announcing the 2018 Ad Manager API Workshop

We’re excited to announce our Ad Manager API Workshop on October 31, 2018. It may be Halloween, but there are no tricks, some treats, and a lot of information on how you can get more out of the Ad Manager API.

What is it?

A half-day event featuring technical talks by Google engineers and office hours with Google's Developer Relations team. Agenda with description for each of the talks is available on the registration site.

Who is the target audience?

The event is targeted toward developers who use or are interested in using the Ad Manager API. The talks will be technical, thus technical background is recommended for all attendees. This event is an opportunity for you to learn more about the API's capabilities and its newest features. This is also an opportunity for you to share feedback and influence direction by talking directly with Googlers who work on the API.

Where is it?

Google’s Chelsea Market Office
75 Ninth Avenue,
New York, NY 10011

How do I sign up?

To register, please visit registration site. Seating is limited, and after you register, we will reach back out to you to confirm your spot at the workshop.

Sunset of the Ad Manager API v201711

On Friday, November 30, 2018, in accordance with the deprecation schedule, v201711 of the Ad Manager API will be sunset. At that time, any requests made to this version will return errors.

If you’re still using this version, now is the time to upgrade to the latest release and take advantage of new functionality with Preferred Deals, forecasting, and reporting.

To upgrade, check the release notes to identify any breaking changes, grab the latest version of your client library, and update your code.

Significant changes include:

This is not an exhaustive list, so be sure to check the release notes for a list of all changes. As always, don't hesitate to reach out to us with any questions.

To be notified of future deprecations and sunsets, join the Ad Manager API Sunset Announcements group and adjust your notification settings. If you are an administrator on your network, you can now also receive notifications when an application is making requests to your network using a deprecated version, as explained in this post.

Introducing the Improved Ad Manager API Sunset Notifications

We’ve heard your feedback regarding the current API sunset notifications, and today we’re pleased to share some upcoming improvements.

Greater User Control
Network administrators will be able to choose whether or not to receive these notifications via the Notification Settings panel in the Ad Manager UI. Check the box next to Deprecated API in use to opt-in to the notifications. Administrators will be automatically opted-in at launch.








More Meaningful Information

Our communications already include a list of applications that are using the deprecated API version. The improved email notification also shows how many requests each application made to the deprecated API. We hope this will help you prioritize which applications need to be upgraded first and expedite the API upgrade process.


UI Notifications

Alongside the email notification, you will also receive a notification card in the Ad Manager UI. Both will be sent on the second Tuesday of each month.







These updates will be rolling out to network administrators in the coming weeks and we will announce in the release notes when they’re available. As always, upcoming deprecation and sunset dates are available on the deprecation schedule page. If you have any questions or feedback, please feel free to reach out to us on the Ad Manager API forums.

Announcing v201808 of the Google Ad Manager API

We're happy to announce that v201808 of the Google Ad Manager API is available starting today. This version brings several new forecasting features, including forecast breakdowns by date and targeting. You can also forecast for AMP-only traffic and Proposal Line Items.

For video users, note that the new requestPlatformTargeting field is required when creating video line items.

For a full list of API changes in v201808, see the release notes.

If you're using one of our client libraries, you'll notice they've been updated to reflect our new name, so allow extra time for upgrading. A migration guide for each client library is available on GitHub: For questions about this or any other API changes, reach out to us on the Ad Manager API forums.

DFP API is becoming Google Ad Manager API



With DoubleClick for Publishers becoming Google Ad Manager, the API will be undergoing changes to follow suit. Over the next month, there will be changes to our documentation and client libraries, but no API entities are changing yet.

Documentation

In late July, references to “DFP” will become “Google Ad Manager” or just “Ad Manager”. Also, the documentation URL will change from https://developers.google.com/doubleclick-publishers/ to https://developers.google.com/ad-manager/.

We will support redirects to all documentation pages. For example, if you have a bookmark for the ReportService, you don’t need to do anything for this bookmark to continue working.

Client Libraries

Each of our client libraries will be updated to remove references to DFP in the v201808 release, which is currently scheduled for August 14, 2018. For example, in the Java client library, the DfpServices class will be renamed to AdManagerServices.

Each client library will have its own guidelines for what needs to be updated. In the announcement blog post for v201808 we will link to these guides. Keep in mind that you’ll only need to refactor your code once upgrading to v201808 and beyond, so using the DFP names will still be supported by some versions of the client library until August, 2019.


As always, if you have any questions or suggestions, feel free to reach out to us on our forum.

Sunset of DFP API v201708

On Friday, August 31, 2018, in accordance with the deprecation schedule, v201708 of the DFP API will be sunset. At that time, any requests made to this version will return errors.

If you’re still using this version, now’s the time to upgrade to the latest release and take advantage of fluid AdUnit sizes, Dynamic Ad Insertion options for video ads, and new reporting functionality.

In order to upgrade, check the release notes to identify any breaking changes, grab the latest version of your client library, and update your code.

Significant changes include:

This is not an exhaustive list, so be sure to check the release notes for a list of all changes. As always, don't hesitate to reach out to us with any questions. To be notified of future deprecations and sunsets, join the DFP API Sunset Announcements group and adjust your notification settings.

Announcing v201805 of the DFP API

We're happy to announce that v201805 of the DFP API is available starting today. This release brings several new features for DFP Video advertising services, including a new service for DAI authentication and support for CdnConfigurationService actions.

This version also brings support for interstitial and native AdUnits.

For reporting users, v201805 adds support for filtering on many more AD_EXCHANGE dimensions. It also removes several deprecated dimensions and columns.

For a full list of API changes in v201805, see the release notes.

As always, if you have any questions, feel free to reach out to us on the DFP API forums.

Improvements to the DFP API documentation

An API is only as good as its documentation, which is why we’re pleased to announce some exciting improvements to the DFP API documentation based on user feedback. We hope these changes will make your workflow a little easier.

Additional information on report entities. We have added documentation for each Dimension, DimensionAttribute, and Column that states its UI name. This mapping from API entity names to UI entity names should make it easier to mimic report queries from the UI. Also, each of these report entities now has a list of compatible report types to help you determine which entities can be used with each other before running a report query.

Filtering report entity tables. There are a large number of Dimensions, DimensionAttributes, and Columns over which you can query a report. Also, as mentioned, we have added even more useful information to these entities. In order to better navigate this large body of documentation, you can now filter these entities on their name or description by entering keywords in the textbox that appears above each table.



Overall DFP documentation search. In addition to the reporting documentation improvements, we have also improved the overall search functionality on the DFP API documentation site. When you type a query into the search bar at the top of each page, the list of suggested results are now pulled only from the latest version, which allows more results to be shown instead of showing the same result across multiple versions.


As always, if you have any questions or suggestions, feel free to reach out to us on our forum.

Sunset of DFP API v201705

On Thursday, May 31, 2018, in accordance with the deprecation schedule, v201705 of the DFP API will be sunset. At that time, any requests made to this version will return errors.

If you’re still using this version, now’s the time to upgrade to the latest release and take advantage of new features such as Preferred Deal support, reporting time zone configuration, and reporting currency configuration.

In order to upgrade, check the release notes to identify any breaking changes, grab the latest version of your client library, and update your code.

Significant changes include:

This is not an exhaustive list, so as always, don't hesitate to reach out to us with any questions. To be notified of future deprecations and sunsets, join the DFP API Sunset Announcements group and adjust your notification settings.

AdWords and DFP client library for Java will soon require Java 8+

Starting on July 1, 2018, all releases of the Google Ads API Client Library for Java will only be compatible with Java 8 (1.8) and higher.

Why this change is happening
The primary reasons for this change are:
Next steps
If you are using Java 8 or higher, no action is required.

If you are still using Java 7, you'll have to migrate your runtime to Java 8 or higher. Check out the Java 8 adoption guide from Oracle to get started.

Still have questions? Feel free to file an issue on the library's issues page or contact us via our Google+ page.