Tag Archives: adwords_api

AdWords click measurement improvements and migration

Earlier this month, the following improvements were made available to all users:
  • Setting finalUrlSuffix at the customer, campaign, ad group, ad, and extension level in all AdWords accounts. Previously, this feature was only available in test accounts.
  • Specifying up to eight custom parameters. Previously, the maximum number of custom parameters was three.
As announced earlier this year, starting October 30, 2018, parallel tracking will be required for all AdWords accounts. With the above features in place, the AdWords API now supports all the features needed to migrate your accounts to parallel tracking, so we encourage you to get started on the migration as soon as possible. The detailed AdWords API guide and accompanying implementation checklist will walk you through the required changes.

If you have questions or need help with the migration, please email us at [email protected].
- Josh Radcliff, AdWords API Team

AdWords API v201710 sunset reminder

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

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

Announcing v201806 of the AdWords API

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

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.
    • The four Recommendations we currently provide in the API are:
      • Bid more efficiently with target CPA
      • Add new keywords
      • Add ad suggestions
      • Fix campaigns that are limited by budget
    • Search for Recommendations using GoogleAdsService.Search, which supports filtering and selecting with ad group, campaign, and campaign budget for supported Recommendations.
    • Retrieve and apply Recommendations using RecommendationService.
  • 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

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. 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

Join us live at the Google Ads API webinars

A few weeks ago, we announced the beta release of the Google Ads API. We're offering an introductory look into this new API, at two different times: The presentation will cover the new API and its features. Topics include capabilities, architecture, set up, and your first API call.

Please submit your questions now so we can answer them in the webinar. We'd love to hear from you!

If you haven’t had a chance to sign up for the beta, you can still submit an application ahead of the webinar. Please contact us via the forum if you have any questions or need help.
Nadine Sundquist, on behalf of the AdWords API Team

Click measurement changes in AdWords

AdWords now allows you to enable parallel tracking for all advertisers from frontend and API. People who click your ads will go directly to your landing page while their browser handles click measurement requests in the background. This helps reduce lost visits which can happen if a customer clicks on your ad but never sees your landing page because they navigate away before the redirect from your tracking URL completes.

All ads using third-party click measurement will begin using parallel tracking at a later date. However, you should start developing for compatibility as soon as possible to give yourself enough time for the migration. If you implement your own click measurement server or provide this service to your customers, refer to our newly published guide for help with implementation. If you are an advertiser who uses a third-party measurement solution, reach out to your service provider to prepare for the switch.

If you need additional support, please email us at [email protected].
 - , AdWords API Team

Join the beta for the new AdWords API

Today we’re announcing the beta release of Google Ads API v0. The Google Ads API is the next generation of our current AdWords API, and it can be accessed via gRPC and JSON REST from a variety of client environments. As this API gradually rolls out, it will reach full parity with the current API.

What’s in the beta?
For the beta, you have the ability to manage search campaigns from creation all the way to reporting. By getting in early, you’ll get to:
  • Integrate newer technologies like gRPC or JSON REST into your product sooner.
  • Provide feedback when requested on the beta in order to influence the new Google Ads API.
  • Try out features such as the new Google Ads Query Language that gives more querying flexibility.
  • Start using the API to query metrics with the accompanying resources and then mutate those resources. For example, you can query all the keywords that have zero impressions and then immediately mutate those keywords to change their bids.
The functionality for Google Ads API v0 includes:
  • Creating, updating, and removing search campaigns.
  • Managing campaign budgets.
  • Managing ad groups in search campaigns.
  • Managing 5 different kinds of ads in search campaigns.
  • Setting shared and portfolio bidding strategies.
  • Setting up targeting using keywords in search campaigns.
  • Retrieving detailed advertiser information.
  • Reporting on various metrics for search campaigns.
Please see the release notes for more details.

How do I join the beta?
Anyone with an existing developer token can apply to join this beta by submitting an application. People who join the beta are expected to submit feedback in order to help us make improvements.

Once you are approved, start with the Get Started guide, and get familiar with our other guides. We’ve also created client libraries for Java, C#, and Ruby with examples to help get you started.

Where do I learn more?
To get started with the API, our team has put together resources: If you have any questions or need help, please contact us via the forum.
Nadine Sundquist, on behalf of the AdWords API Team

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