Google Ads Developer Blog

Sunset of the Ad Manager API v201805

2019-04-08T08:19:00.000-07:00

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.

- Donovan McMurray, Ad Manager API Team

Announcing v201902 of the Google Ad Manager API

2019-02-12T12:02:00.000-08:00

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.

- Donovan McMurray, Ad Manager API Team

Subscribe to our RSS feed to get blog posts via email

2019-02-08T09:31:00.000-08:00

(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:

- Mike Cloonan, Ads Developer Relations Team

Announcing the 2018 Ad Manager API Workshop

2018-10-11T08:25:00.001-07:00

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.
- Donovan McMurray, Ad Manager API Team

Sunset of the Ad Manager API v201711

2018-10-08T22:10:00.000-07:00

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:

The removal of creativePersistenceType from LineItems, impacting the LineItemService and ForecastService.
The removal of VpaidLinearCreative and VpaidLinearRedirectCreative as part of the Flash creative deprecation.
The replacement of old partner metrics with new PARTNER_MANAGEMENT fields.
Changes to how time zones are handled in Sales Manager and Ad Exchange Historical reports. You should now use timeZoneType.

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.

- Donovan McMurray, Ad Manager API Team

Introducing the Improved Ad Manager API Sunset Notifications

2018-10-04T13:40:00.000-07:00

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.

- Nevin Mital, Ad Manager API Team

Announcing v201808 of the Google Ad Manager API

2018-08-21T11:30:00.001-07:00

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.
- Chris Seeley, DFP API Team

DFP API is becoming Google Ad Manager API

2018-07-12T11:11:00.003-07:00

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.

- Donovan McMurray, DFP API Team

Sunset of DFP API v201708

2018-07-09T12:52:00.003-07:00

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:

The replacement of the header and footer fields on CreativeWrapper with htmlHeader and htmlFooter strings.
The removal of creativePersistenceType from LineItems, impacting LineItemService and ForecastService.
The replacement of old partner metrics with new PARTNER_MANAGEMENT fields.
Changes to how time zones are handled in Sales Manager and Ad Exchange Historical reports.

- Donovan McMurray, DFP API Team

Announcing v201805 of the DFP API

2018-05-15T10:27:00.000-07:00

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.

- Chris Seeley, DFP API Team

Improvements to the DFP API documentation

2018-04-13T12:58:00.000-07:00

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.

- Donovan McMurray, DFP API Team

Sunset of DFP API v201705

2018-04-09T12:41:00.000-07:00

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:

Support for Preferred Deal line items.
Editing AdUnit assignments to Placements now happens in the Placement Service.
AdUnit.inheritedAdSenseSettings has been replaced with AdUnit.adSenseSettings and AdUnit.adSenseSettingsSource.
Old partner metrics have been replaced by new PARTNER_MANAGEMENT fields.

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.

- Gabe Rives-Corbett, DFP API Team

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

2018-03-29T08:15:00.001-07:00

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:

Java 7 was first introduced in July, 2011, and Oracle's support for Java 7 is approaching some key end dates.
Maintaining support for Java 7 means code examples cannot leverage useful features of Java 8, such as lambda expressions, default methods, and stream API support for collections.
Supporting Java 9 in the client library will require upgrading several dependencies to versions that may not support Java 7.
Use of Java 7 among Google Ads API Java Client Library developers is declining, with most users on Java 8 or above.

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.
- Josh Radcliff, AdWords API Team

Ad Exchange Seller REST API Deprecation Reminder

2018-03-21T06:57:00.000-07:00

The Ad Exchange Seller REST API is deprecated. Existing API clients should migrate to the DoubleClick for Publishers API before July 26, 2018. After this date, all requests to the Ad Exchange Seller REST API will return errors.

This migration guide provides instructions for getting started, as well as a mapping of each Ad Exchange reporting metric to its equivalent in the DFP API.

For more details about reporting in the DFP API, see the reporting guide.

For general assistance with the DFP API or your migration, reach out on our developer forum.

- Chris Seeley, DFP API Team

Announcing v201802 of the DFP API

2018-02-13T10:19:00.001-08:00

Today we’re pleased to announce several additions and improvements to the DFP API with the release of v201802. Here are the highlights:

LineItemService: The API now supports the Preferred Deals lineItemType, which allows you to programmatically offer inventory to specific buyers. Check out our Preferred Deals overview for more information.

PublisherQueryLanguageService: There are several new columns available through PQL in v201802. In the Audience_Segment PQL table, the newly added PpidSize column contains the number of unique viewers in a segment. In the Programmatic_Buyer PQL table, the new EnabledForPreferredDeals and EnabledForProgrammaticGuaranteed columns allow you to validate whether a buyer can be associated with a proposal based on the types of proposal line items it contains.

ReportService: A number of reporting features have made it from the UI into the API in v201802. The Demand Channel dimension is now available through the API via DEMAND_CHANNEL_NAME and DEMAND_CHANNEL_ID. Also, the Request Type can be accessed via REQUEST_TYPE. You can now filter proposal line items with the PROPOSAL_LINE_ITEM_TYPE dimension attribute. Finally, you can specify the currency type with adxReportCurrency for Ad Exchange Historical reports. You can read more on how Ad Exchange report currency works in Help Center.

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

Like sands through the hourglass, so are the deprecations of our lives. If you're using v201705 or earlier, it's time to look into upgrading. Also, remember that v201702 will be sunset at the end of March 2018.

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

Sunset of DFP API v201702

2018-01-31T13:29:00.000-08:00

On Friday, March 30, 2018, which is a one-month extension from the traditional deprecation schedule, v201702 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 support for creating ImageOverlayCreatives, and new Ad Exchange reporting dimensions and columns. 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:

Reporting dimensions and columns are now at parity with Ad Exchange.
Editing AdUnit assignments to Placements now happens in the Placement service.
AdUnit.inheritedAdSenseSettings has been replaced with AdUnit.adSenseSettings and AdUnit.adSenseSettingsSource.
The AdUnit fields mobilePlatform, partnerId, isSharedByDistributor, and crossSellingDistributor have been removed.
Placement fields adSenseTargetingLocale, isAdsenseTargetingEnabled, targetingDescription, targetingSiteName, and targetingAdLocation have been removed to align with the UI.
Company.Type enumerations AFFILIATE_DISTRIBUTION_PARTNER and CONTENT_PARTNER have been removed.
CrossSellingDistributor has been removed.
Old partner metrics have been replaced by new PARTNER_MANAGEMENT fields.

- Gabe Rives-Corbett, DFP API Team

Announcing v201711 of the DFP API

2017-11-14T12:07:00.000-08:00

Today we're pleased to announce several additions and improvements to the DFP API with the release of v201711. This release includes a new service, CdnConfigurationService, which manages the configuration of DAI (Dynamic Ad Insertion) content ingestion and delivery networks.

Please note that Ad Exchange historical reports will be run in the Pacific timezone in v201711. This will allow you to report on Bid and Deals metrics. If you need to continue running Ad Exchange historical reports in your network timezone, please stay on v201708. Future versions will support both options.

Additionally, the release adds the ability to generate in-site preview URLs for native styles, and you can now determine if an AdUnit supports fluid sizes by looking at the new isFluid attribute.

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

With each new release comes a deprecation. If you're using v201611 or earlier, it's time to look into upgrading. Also remember that v201702 will be sunset at the end of February 2018.

As always, if you have any questions, feel free to drop us a line on the DFP API forum.

- Gabe Rives-Corbett, DFP API Team

Ad Exchange Seller REST API Deprecation

2017-10-26T07:29:00.000-07:00

The Ad Exchange Seller REST API is being deprecated as of October 26, 2017. No new API clients will be supported after this date. Existing API clients will need to migrate to the DoubleClick for Publishers API before July 26, 2018. After this date, all requests to the Ad Exchange Seller REST API will return errors.

What action is required

Current Ad Exchange Seller REST API users will need to migrate to the DoubleClick for Publishers API before July 26, 2018. This migration guide provides a mapping of each Ad Exchange reporting metric to its equivalent in the DFP API.

For more details about reporting in the DFP API, see the reporting guide.

For general assistance with the DFP API or your migration, reach out on our developer forum.

Why this is happening

As a part of our effort to provide a unified tool to manage your ad business and monetize your inventory, the DoubleClick for Publishers API now supports all of the features of the Ad Exchange Seller REST API. The DFP API is more robust and has more frequent updates.

What isn't changing

Users will not need to create new accounts. All Ad Exchange Seller users already have a DoubleClick for Publishers account.

No data is changing. The only change is how you programmatically access that data.

- Chris Seeley, DFP API Team

Sunset of DFP API v201611

2017-10-09T10:45:00.000-07:00

On Thursday, November 30th, 2017, in accordance with the deprecation schedule, v201611 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 like support for creating ImageOverlayCreatives, new Ad Exchange reporting dimensions and columns, and the change history table. 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:

Reporting dimensions and columns are now at parity with Ad Exchange.
Editing AdUnit assignments to Placements now happens in the Placement service.
AdUnit.inheritedAdSenseSettings has been replaced with AdUnit.adSenseSettings and AdUnit.adSenseSettingsSource.
The AdUnit fields mobilePlatform, partnerId, isSharedByDistributor, and crossSellingDistributor have been removed.
Placement fields adSenseTargetingLocale, isAdsenseTargetingEnabled, targetingDescription, targetingSiteName, and targetingAdLocation have been removed to align with the UI.
Company.Type enumerations AFFILIATE_DISTRIBUTION_PARTNER and CONTENT_PARTNER have been removed.
CrossSellingDistributor has been removed.
Old partner metrics have been replaced by new PARTNER_MANAGEMENT fields.

- Gabe Rives-Corbett, DFP API Team

Announcing v201708 of the DFP API

2017-08-15T11:48:00.001-07:00

Today we’re pleased to announce several additions and improvements to the DFP API with the release of v201708.

CreativeService: The API now supports the skippableAdType attribute on VideoCreatives and the mezzanineFile asset on VideoRedirectCreatives.

CreativeWrapperService: The HTML header and footer fields have been renamed to htmlHeader and htmlFooter, and they are now strings instead of CreativeWrapperHtmlSnippets.

ProposalService: Proposals are now automatically synced with marketplace. Therefore, the proposal action SyncProposalsWithMarketplace has been removed (sending this action with performProposalAction is now a no-op in previous API versions).

PublisherQueryLanguageService: In v201702 the Change_History table was introduced. Now, new entities for Sales Management have been added to the EntityType column. The new entities are BASE_RATE, PREMIUM_RATE, PRODUCT, PRODUCT_PACKAGE, PRODUCT_PACKAGE_ITEM, PRODUCT_TEMPLATE, PROPOSAL, PROPOSAL_LINK, PROPOSAL_LINE_ITEM, PACKAGE, RATE_CARD, and WORKFLOW.

ReportService: DateRangeType now supports a new LAST_3_MONTHS option. Also, several deprecated reporting metrics have been removed. They can be replaced with their corresponding partner management metrics, so you will need to update any code using those fields. For more information, check out the support entry for partner management reporting metrics.

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

With each new release comes a new deprecation. If you're using v201611 or earlier, it's time to look into upgrading. Also, remember that v201608 will be sunset at the end of August 2017.

As always, if you have any questions, feel free to reach out to us on the DFP API forums or the Ads Developer Google+ page.
- Donovan McMurray, DFP API Team

Sunset of DFP API v201608

2017-07-07T04:02:00.002-07:00

On Thursday, August 31st, 2017, in accordance with the deprecation schedule, v201608 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 like support for creating ImageOverlayCreatives, Partner companies, new team actions, and the change history table. To do so, check the release notes to identify any breaking changes, grab the latest version of your client library, and update your code.

Significant changes include:

Reporting dimensions and columns are now at parity with Ad Exchange.
Editing AdUnit assignments to Placements now happens in the Placement service.
AdUnit.inheritedAdSenseSettings has been replaced with AdUnit.adSenseSettings and AdUnit.adSenseSettingsSource.
The AdUnit fields mobilePlatform, partnerId, isSharedByDistributor, and crossSellingDistributor have been removed.
Placement fields adSenseTargetingLocale, isAdsenseTargetingEnabled, targetingDescription, targetingSiteName, and targetingAdLocation have been removed to align with the UI.
Company.Type enumerations AFFILIATE_DISTRIBUTION_PARTNER and CONTENT_PARTNER have been removed.
CrossSellingDistributor has been removed.
Added actions to support programmatically activating and deactivating teams.

- Gabe Rives-Corbett, DFP API Team.

Improvements to the DFP Python Library

2017-06-07T14:22:00.001-07:00

We've recently released some improvements to the DFP Python Library alongside support for v201705. Our goal was to reduce the boilerplate required to construct entities and DFP statements—keep reading to see what's new.

Improved statement creation utility

Previously you had to construct filtering statements manually out of strings, and write a lot of code to bind variables into statements. Here's what the code commonly looked like:

values = [{
    'key': 'startDateTime',
    'value': {
        'xsi_type': 'DateTimeValue',
        'value': {
            'date': {
                'year': start_date.year,
                'month': start_date.month,
                'day': start_date.day
            }
        }
    }
},{
    'key': 'orderName',
    'value': {
        'xsi_type': 'TextValue',
        'value': 'My Order%'
    }
}]
statement = dfp.FilterStatement('WHERE startDateTime > :startDateTime AND '
                                'orderName LIKE :orderName', values)

Dealing directly with strings opens up many potential errors, and we decided that the above was way too much typing just to bind variables. To make things easier, we've introduced a new utility called StatementBuilder. Now you can write code as simple as:

statement = (dfp.StatementBuilder()
             .Where('startDateTime > :startDateTime AND orderName LIKE :orderName')
             .WithBindVariable('startDateTime', start_date)
             .WithBindVariable('orderName', 'My Order%'))

StatementBuilder will automatically infer your variable types and construct the values object. You can then pass this to an API request in the same way that you did with FilterStatement:

response = creative_service.getCreativesByStatement(statement.ToStatement())

Automatic datetime unwrapping

Previously, you had to break out dates and datetimes into our format when constructing entity dictionaries:

line_item = {
    'orderName': 'Awesome New Order',
    'startDateTime': {
        'date': {
            'year': start_date.year,
            'month': start_date.month,
            'day': start_date.day
        },
        'hour': start_date.hour,
        'minute': start_date.minute,
        'second': start_date.second,
        'timezoneid': start_date.tzinfo.zone,
    },
    # ...
}

Starting in this version, you can simply pass a native Python date or timezone-aware datetime object directly:

start_date = datetime.datetime(2017, 6, 1, 9, 0, 0,
                               tzinfo=pytz.timezone('America/New_York'))
line_item = {
    'orderName': 'Awesome New Order',
    'startDateTime': start_date
    # ...
}

Our library will unwrap the datetime object into our format automatically. We're continuing to support passing the full dictionary, so there's no requirement to migrate your code.

We hope these changes will make building DFP integrations in Python easier. As always, please feel free to get in touch on the forum with any questions.

- Gabe Rives-Corbett, DFP API Team

Announcing v201705 of the DFP API

2017-05-23T11:16:00.001-07:00

Today we’re pleased to announce the v201705 release of the DFP API. This release updates the ReportService to be at parity with the Ad Exchange Seller REST API.

Additionally, v201705 adds support for creating ImageOverlayCreatives and new Partner companies.

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

With each new release comes a new deprecation. If you're using v201608 or earlier, it's time to look into upgrading. Also remember that v201605 will be sunset at the end of May 2017.

As always, if you have any questions, feel free to drop us a line on the DFP API forums or the Ads Developer Google+ page.
- Chris Seeley, DFP API Team

Sunset of DFP API v201605

2017-04-05T11:22:00.000-07:00

On Wednesday, May 31, 2017, in accordance with the deprecation schedule, v201605 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 like native ad styling, additional DAI fields, and the change history table. To do so, check the release notes to identify any breaking changes, grab the latest version of your client library, and update your code.

Significant changes include:

The integer AdRule.id was replaced with the long AdRule.adRuleId. The values of existing IDs are the same.
Removed paging support from ProposalService.getMarketplaceCommentsByStatement.
getCustomTargetingValuesByStatement() now properly enforces the requirement of a custom targeting key ID in the filter statement.
Added PROPOSAL_OUT_OF_SYNC_WITH_MARKETPLACE that will be thrown in rare cases where a programmatic proposal is out of sync with its Marketplace version.
ProposalAction.DiscardProposalDrafts has been renamed to ProposalAction.DiscardLocalVersionEdits to more accurately reflect its purpose.
Order.programmaticSettings has been removed in favor of Proposal.ProposalMarketplaceInfo.
AD_SERVER_DELIVERY_INDICATOR has been renamed to LINE_ITEM_DELIVERY_INDICATOR and is now a dimension attribute.
Team.companyIds, Team.adUnitIds, and Team.orderIds have been removed. Use Company.appliedTeamIds, AdUnit.appliedTeamIds, and Order.appliedTeamIds instead.
GrpProvider.COMSCORE has been renamed to GrpProvider.GOOGLE.

- Gabe Rives-Corbett, DFP API Team

Reminder to PHP users - upgrade to the new Ads PHP library!

2017-04-05T08:13:00.001-07:00

Hello PHP developers! In December 2016, we announced the stable release of the new ads PHP library and the deprecation of the old one. This is a reminder to upgrade to the new library by July 31, 2017.

The new PHP library has many improvements such as support of namespaces and Composer installation. It is currently available as the master branch on GitHub. We also provide an upgrading guide to help you during this upgrade.

The old library has been moved to the deprecated branch with reduced support and will reach end of life (EOL) on July 31, 2017. We recommend you complete your upgrade before that date. Past this date, the deprecated branch can still be used until all of the AdWords / DFP API versions it supports are sunset, but we will not add support and examples for new API versions, nor fix any bugs.

If you have questions about upgrading or need help, as always, feel free to ask on the GitHub issues page. If you have questions regarding AdWords or DFP API, please drop us a line on the AdWords or DFP API forums.
- Thanet Praneenararat, Ads Developer Relations Team