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.

What's changing?
Beginning March 26, 2018, once an AdWords account reaches 15 months without any spend, it will be canceled in order to speed up the AdWords experience and help users stay within the manager account limits. This also means that right now, if your account has reached 15 months without spend, it meets the criteria and will be canceled. After an account is canceled:
  • get requests for ManagedCustomerService will no longer return the account.
  • Any AdWords API request that specifies the account's customer ID in the clientCustomerId header will fail with an AuthorizationError.CUSTOMER_NOT_ACTIVE starting with v201802 and an OperationAccessDenied.ACTION_NOT_PERMITTED error for earlier versions of the AdWords API.
  • Any unspent prepaid amount will be refunded back to the advertiser.
  • All ads in your account will stop automatically within 24 hours.
Note: Test accounts will not be canceled.

What should you do?
If your application issues AdWords API requests against inactive accounts, make sure you download any relevant data for those accounts before the cancellation process starts. For example, you may want to run reports to gather historical stats for the date range where the account had activity.

If you are using an inactive account in order to test your integration with the AdWords API, consider creating a test account instead. Test accounts will not be canceled by the ongoing cancellation process.

To avoid issues once the cancellation process starts, you can proactively cancel accounts as follows:
  • Log into your manager account.
  • Go to the Accounts page, where you can adjust the date range and review the performance metrics for each account under the manager account to help you identify inactive accounts.
  • Check the box next to each account you want to cancel.
  • Select Edit -> Cancel account.
To reactivate an account, follow the instructions in the AdWords Help Center. If you are logged in as a manager account, you can show canceled accounts by adjusting the filter in the upper left corner as follows:

Note: If the account is under one or more manager accounts, you will only be able to reactivate the account if doing so will not exceed the manager account limits.

If you have any questions, please contact us via the forum.

Both AdWords API v201705 and v201708 will be sunset on March 28, 2018. After this date, all v201705 and v201708 API requests will begin to fail. If you haven't already migrated to v201710, we recommend that you skip v201710 and migrate directly to v201802. Please migrate prior to March 28, 2018 to ensure your API access is unaffected.

We've prepared the following resources to help you with the migration: As always, if you have any questions about this migration, please contact us via the forum.

Today we’re announcing the release of AdWords API v201802. Here are the highlights: In addition to the above changes for v201802, the following improvements were made in all versions of the AdWords API:
  • Click types for Shopping Showcase ads. The list of click types in reports now includes values for Showcase Shopping ads interactions.
  • Member uploads by mobile ID/IDFA and address. All users of the AdWords API can now upload mobile ID/IDFA and address member data to CrmBasedUserList. Previously, these features were only available to whitelisted users.
If you’re using v201705 or v201708 of the AdWords API, please note that they will be sunset on March 28, 2018. We strongly encourage you to skip v201705, v201708, and v201710 and migrate directly to v201802. If you're using v201710, be aware it's now marked deprecated and will be sunset on July 11, 2018.

As with every new version of the AdWords API, please carefully review all changes in the release notes and the v201802 migration guide. The updated client libraries and code examples will be published within the next 48 hours.

If you have any questions or need help with migration, please contact us via the forum.

On March 19, 2018, we are updating how AdNetworkType1 and AdNetworkType2 columns report zero impression rows related to video networks.

Currently, if you request AdNetworkType1 or AdNetworkType2 columns and request zero impression rows by setting the includeZeroImpressions flag to true, you get back zero impression rows for YOUTUBE_SEARCH and YOUTUBE_WATCH values only if you target these networks in your Advertiser account. After this change, we will always return zero rows corresponding to these network types irrespective of whether you advertise on these networks. Other network types are not affected by this change.

This change makes the behavior of YOUTUBE_SEARCH and YOUTUBE_WATCH network types consistent with the behavior of other network types. Once this change goes live, you may start seeing a higher number of zero impression rows than what you see today when requesting AdNetworkType1 or AdNetworkType2 columns along with zero impression rows.

If you have any questions about these changes, post them in our developer forum.


We’re excited to announce that we’ve teamed up with the Accelerated Mobile Pages team to bring you amp-ima-video, an IMA-SDK-enabled video player extension for AMP pages. This extension has been an AMP experiment for the past few months, but today we’re moving from experiment to public release.

amp-ima-video provides an AMP-enabled video player with the IMA SDK pre-integrated, so you can easily play and monetize content on your AMP pages. Simply provide your content URL and an ad tag, and we’ll handle playing back the video and ad(s). The extension currently supports linear in-stream single ads and VMAP playlists. To see it in action, check out the AMP by Example page for the extension.

If you have any questions or issues with the extension, please file them via the AMP issue tracker on GitHub.

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.