Google Ads Developer Blog

AdWords API v201710 sunset reminder

Tuesday, 26 June 2018

AdWords API v201710 will be sunset on July 25, 2018. After this date, all v201710 API requests will begin to fail. We recommend that you skip v201802 and migrate directly to v201806. Please migrate prior to July 25, 2018 to ensure your API access is unaffected.

We've prepared various resources to help you with the migration:

As always, if you have any questions about this migration, please contact us via the forum.

- Mike Cloonan, AdWords API Team

A new guide for integrating Google Shopping ads using Google APIs

Monday, 25 June 2018

Good news for developers planning to integrate Google Shopping ads! We have just released a brand new guide explaining how to automate the delivery of Google Shopping on behalf of merchants using Google APIs.

The Shopping Automation Guide covers the steps required to set up new merchants using a combination of the Content API for Shopping and AdWords API. It describes how you can fully automate certain tasks that would otherwise be performed manually using the Merchant Center and AdWords websites.

The guide is for developers interested in feed management, campaign management, or full automation workflow that includes both. The workflows provide detailed explanations of how the different APIs can be used for each stage of the user journey. You can follow the workflow step by step or navigate straight to the article you require using the side panel.

Head over to the developer pages to get started! If you have any questions or need help, please contact us on the relevant forums:

If you have any feedback on the guide, please use the “Send Feedback” link at the top right of each page.

We also appreciate any feedback on your experience using the guide. If you would like to share it, please complete this survey.

- Ian Ballantyne, AdWords API Team

Announcing v201806 of the AdWords API

Wednesday, 6 June 2018

Today we’re announcing the release of AdWords API v201806. Here are the highlights:

Mutable ads. The new AdService allows you to edit ads in place and retain performance stats for ETA, DRA, Showcase ads, and responsive search ads. Check out the updated ads overview for details.
Responsive search ads (beta). This new ad format allows you to provide multiple headlines and descriptions in one creative. These assets are then combined into ads that can accommodate more content -- up to 3 headlines and 2 description lines -- and can improve performance. Responsive search ads are available to whitelisted users and in test accounts.
Responsive display ads (beta). This new type of display ad is available to whitelisted users and will be fully supported when it launches later this summer. Responsive display ads allow you to provide multiple text and image assets in one creative, and then AdWords combines and tests these assets to show the most relevant ads to your customers across the Google Display Network.
Smart display campaigns (beta). The AdWords API now supports creation and management of Smart display campaigns by whitelisted users, and will also be fully supported when it launches later this summer. The new accompanying guide covers all the details.
Offline conversion adjustments. The new OfflineConversionAdjustmentFeedService allows you to apply conversion adjustments using the AdWords API. The updated conversions guide has more details to help you get started with this new service.
Dynamic Search Ads criteria. WebpageConditions for Webpage criteria now support parameters based on an exact match of URLs.
New promotion extension occasions. Several new occasions were added for promotion extensions.

If you’re using v201710 of the AdWords API, please note that it will be sunset on July 25, 2018. We encourage you to skip v201802 and migrate straight to v201806. If you're using v201802, be aware it's now marked deprecated.

As with every new version of the AdWords API, please carefully review all changes in the release notes and the v201806 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.

- Josh Radcliff on behalf of the AdWords API Team

Announcing v0_1 of the Google Ads API

Tuesday, 5 June 2018

Today we’re announcing the beta release of Google Ads API v0_1. With minor updates like this one, you’ll continue to point to v0 as your endpoint, but you will want to update your client libraries. Here are the highlights:

Recommendations. Recommendations provide customized suggestions to help increase your campaigns' performance. This is the first time Recommendations is being brought to you through an API.
PHP client library. In the v0 release, we released Java, C#, and Ruby client libraries. We’re releasing a PHP client library shortly after this version.

To get started with the API, our team has put together these resources:

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

Nadine Sundquist, on behalf of the AdWords API Team

Learn with us: Google Ads API webinars

Tuesday, 29 May 2018

Thank you to the 100+ viewers from 30 different countries who joined our Google Ads API webinars on Tuesday, May 22! We had some great questions during the Q&A and hope it was helpful for everyone who attended.

For those who couldn’t attend the live events, and for anyone who would like a copy of the presentation, both the slides and a video recording of the event are available below.

Webinar Video (May 22, 2018) [1 hr, 13 mins]
Slide Deck

You can find out more about the Google Ads API in our documentation. Please contact us via the forum if you have any questions.

Adam Ohren, on behalf of the AdWords API Team

Limit line item serving with userConsentEligibility in the DFP API

Thursday, 24 May 2018

Using v201805 of the DFP API, publishers can now limit which line items are shown to users in the European Economic Area (EEA) by setting the LineItem.userConsentEligibility field. (Note: this field only takes effect if you have elected to “Limit line items” on the “EU user consent” page.) The userConsentEligibility field can be set to one of three values:

NONE (default) - Don’t serve for any EEA ad requests
CONSENTED_ONLY - Don’t serve for non-personalized ad requests
CONSENTED_OR_NPA - Don’t limit serving

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

- Donovan McMurray, DFP API Team

Announcing v3.1 of the DCM/DFA Reporting and Trafficking API

Thursday, 24 May 2018

Today we're releasing v3.1 of the DCM/DFA Reporting and Trafficking API. Highlights of this release include:

Support for in-stream audio creatives
Landing page mobile deep link management

Details of these and all other changes are covered in our release notes.

Deprecation and sunset reminder

In accordance with our deprecation schedule, this release marks the beginning of the deprecation period for v3.0, which will sunset on November 30, 2018. After this date, any requests made against v3.0 will begin returning errors.

As a reminder, API version 2.8 will be sunset on August 31, 2018. To avoid an interruption in service, all users are required to migrate to a newer version before the sunset date.

Learn More

As with every new version of the DCM/DFA Reporting and Trafficking API, we encourage you to carefully review all changes in the release notes. For those of you looking to get going right away, updated client libraries are now available. If you're just starting out, the Get Started guide is a great reference to help you get up and running quickly.

Give it a try and let us know if you have any questions!

- Jonathon Imperiosi, DCM API Team

Ads Developer Blog