Tag Archives: dfp_api

Sunset of the Ad Manager API v201805

On Friday, May 31, 2019, in accordance with the deprecation schedule, v201805 of the Ad Manager API will be sunset. At that time, any requests made to this version will return errors.

If you’re using any of Google’s client libraries, you should allow extra time to migrate off of v201805, since it was the last version before the DFP API became the Google Ad Manager API. For details on what’s changed, each client library has a migration guide: Java, Python, .NET, PHP, and Ruby.

When you’re ready to upgrade, check the release notes to identify any breaking changes (such as the change to the capitalization of DateTime.timeZoneId in v201811). Then, grab the latest version of your client library and update your code. As always, don't hesitate to reach out to us on the developer forum with any questions.

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

Announcing v201902 of the Google Ad Manager API

We're happy to announce that v201902 of the Google Ad Manager API is available starting today. The two main areas that are getting new API functionality are forecasting and video.

In v201902, you can set LineItems to be paced based on their projected traffic instead of their historical traffic by setting DeliveryForecastSource to FORECASTING. This API version also adds the AdjustmentService to manage traffic forecast adjustments. For example, if you’re expecting an increase in traffic for an upcoming holiday, you can manually adjust your forecasts to take that increase into consideration.

There are also several updates to video features in this version of the API. You can now target LineItems by CmsMetadataValues (content targeting) and custom AdSpots (position targeting).

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

For questions about this or any other API changes, reach out to us on the Ad Manager API forum.

Subscribe to our RSS feed to get blog posts via email

(If you want to continue getting email updates about our blog posts, read on. If you don't want email updates from this blog, you can skip this post.)

For some products, the Google Ads Developer team has used Google groups as a way to allow API users to subscribe and get new relevant blog posts delivered to their email address. Starting now, the way you can get email updates about blog posts is changing. We will no longer send an email to the Google group for each new blog post. We will continue to use the Google groups for other important updates, however.

For users who still want email updates, we've introduced new FeedBurner links on the right-hand panel of our blog homepage. You can subscribe to the RSS feed by clicking on the link for the product you're interested in, or subscribe by email by clicking on the [+] link to the right of the product name.

If you use any of the APIs that we discuss on this blog, make sure you subscribe to the feed to keep up with the latest news and updates:

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.