Category Archives: Ads Developer Blog

The official blog for information about the AdWords, AdSense, DoubleClick and AdMob APIs and SDKs

Announcing Google Ads API Doctor

We have heard from users that correctly configuring a client library and provisioning OAuth2 credentials can be challenging, so today we are introducing Google Ads API Doctor, a new tool that will analyze your client library environment. The program will:
  • Verify that your OAuith2 credentials are correctly configured and ready to make API calls.
  • Guide you through fixing any OAuth2 problems it detects and verify the corrected configuration.
The initial version of this tool will help you analyze and fix issues related to OAuth2 configuration, including the following common issues:
  • Invalid refresh token: The program will identify this and guide you through the process to obtain a valid token, back up your configuration file, and write the new value to your active configuration file.
  • Permission denied: There are several OAuth errors that sound similar, such as user permission denied and permission denied. The program identifies that in the first case it is caused by an invalid refresh token and in the second it’s because the Google Ads API is disabled in the Google API Console.
If you want to send the output to support, you can run your scenario with the PII flag to hide your Personally Identifiable Information (PII) and copy the screen output. To gather even more information, you can use the verbose flag to see the low-level JSON that is returned.

We are releasing this project as open source per Google’s open source initiative, and we encourage contributions. See contributing to Google open source to learn more about how to contribute to this project. As always, share your feedback on the Google Ads API forum.

Announcing the 2019 NYC Google Ad Manager API Workshop

We’re excited to announce another Google Ad Manager API Workshop in NYC on May 8, 2019. If you’re a regular user of the Ad Manager API and Google Publisher Tags, then you’re sure to find something of interest at this event.

What is it?

A half-day event featuring technical talks by Google engineers and office hours with Google's Developer Relations team. Doors will open at 12:45pm and our keynote presentation will kick off at 1 o’clock. We will have talks on the following topics:
  • Serverless API integrations using Google Cloud Functions
  • Strategies and hands-on demos of tools for faster loading pages and ads
  • Advanced techniques for extracting data that isn't available in the reporting API

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 in nature, so a 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 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 our website for this event. Seating is limited, so after you register, we will reach back out to you to confirm your spot at the workshop.

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.

Python 2 Deprecation in Ads API Client Libraries

As the official End of Life date for Python 2 approaches, we will be ending support for Python 2 in both the AdWords/Google Ad Manager and Google Ads Python client libraries in 2019. After deprecation the minimum required Python version for both libraries will be 3.6+.

Deprecation will begin with the AdWords/Google Ad Manager Python client library in May. Here’s a timeline for easy reference:
  • mid-May: version 19.0.0 is released to support Google Ad Manager API v201905. Python 2 users should not upgrade to any major version beyond this.
  • mid-May - late-June: Python 2 deprecation window.
  • Last week in June: version 20.0.0 is released that is incompatible with Python 2.
  • July 1: Support for Python 2-related issues in the library ends.
If you are a user of the AdWords/Google Ad Manager client library, please take note of the following:
  • Google Ad Manager Users:
    • If you’re already using Python 3, no need to take action.
    • If you’re using Python 2 you should remain on version 19.0.0 until you’ve migrated to Python 3.
  • AdWords Users:
    • Please migrate to the new Google Ads API.
    • If you’re using Python 2 you should remain on version 19.0.0 until you’ve migrated to the Google Ads API.
  • All Users:
    • Beginning July 1, 2019 we will discontinue prioritizing work and triaging GitHub Issues related to compatibility with Python 2. Note that we will submit patches to version 19.0.0 if any major bugs arise after this deadline.
The Google Ads API client library will continue to be compatible with Python 2 until the end of 2019. We will post more information about that migration at a later date. In the meantime, Python 2 users should start planning their migration to Python 3 as soon as possible in order to avoid complications.

If you have questions about the Python 3 migration please submit an issue on the respective GitHub repository, and for general API support please reach out to us on the Google Ads API forum or the Google Ad Manager API forum.

Announcing v1_1 of the Google Ads API

Today we’re announcing the v1_1 release of the Google Ads API. With this version, you’ll continue pointing to v1 as your endpoint; however, you'll need to update your client libraries in order to use v1_1 features. If you're still on the AdWords API, now is a good time to give the new API a try.

Here are the highlights: What resources are available?
Check out these helpful resources: The updated client libraries and code examples will be published by March 29, 2019. If you have any questions or need help, please contact us via the forum.

Announcing v2.1 of the Content API for Shopping

Today we're announcing the release of v2.1 of the Content API for Shopping. This version has been available as an experimental version since late last year and is now ready for production use by all Content API users.

You can find a complete list of changes in the release notes and accompanying migration guide, but here are some highlights:
  • A more consistent product validation experience. Product insert requests no longer report non-fatal warnings or errors. This allows you to insert products and make subsequent updates to resolve issues via feed rules in the Merchant Center UI, just as you would with feeds maintained outside the API.
  • A better experience for managing Shopping Actions. Multiple improvements have been made to the Orders API based on feedback from beta users.
  • More features are on the way! Today's release contains many improvements, but more are on the way, including new ways to supply local inventory data and features to support supplemental feeds.
  • Continued v2 support. While we strongly encourage you to migrate to v2.1, support for v2 will continue at least through the first quarter of 2020. Subscribe to this blog to ensure you receive important updates on Content API releases and deprecations.
Updated client libraries
Updated client libraries with support for v2.1 are now available in multiple languages.

Learn more
Check out the v2.1 API reference documentation to explore the new version of the API, and read through the list of behavior changes and deprecations in the migration guide to help plan your upgrade to v2.1.

If you have any questions or need help with migration, please head over to our support forum.

Structured Data Files v4.2 now available in the DoubleClick Bid Manager API

Today we're announcing the general availability of Structured Data Files (SDF) v4.2 in the DoubleClick Bid Manager API. Highlights of this release include:
  • Support for TrueView connected TV bid adjustments
  • Ability to inherit Insertion Order start and end dates at the Line Item level
  • Renaming changes to better align SDF with the Display & Video 360 UI
All SDF users are encouraged to begin requesting v4.2 files to take advantage of these new features. To do so, simply pass 4.2 as the value of version when calling For users with workflows that are dependent on older SDF formats, details of the file format changes between versions can be found in the release notes.

Registration open for Google Ads scripts 2019 workshops

Join us for informative talks and interactive codelabs at our 2019 Google Ads scripts workshops in Europe, Asia, and Australia from April through June.

The curriculum at each of the 6 workshops will be the same, so make sure to sign up for the one that's most convenient for you.

Please visit the event sites below for more details and to register for an event near you. We will be hosting the following sessions: We hope to see you there!

Introducing the Google Ads Query Builder tool

Today we are excited to announce that the Google Ads Query Builder tool is now available on the Google Ads API Developer Site.

The Google Ads API has a robust reporting system that utilizes our new Google Ads Query Language. The language’s syntax allows you to select from all the resources that are available for reporting, and also filter or sort the result set on the server before they are returned to your application.

This tool provides a friendly web interface for you to explore our API’s reporting capabilities, and generate queries that you can copy and paste right into your applications. You can visit the site and try out the tool today!

Example usage of the Google Ads Query Builder: A screenshot showing a sample usage of the Google Ads Query Builder UI, including both filtering and ordering. Happy reporting!

Google Ads API Policy Notes

In our recent blog post we announced the launch of Google Ads API v1. Since the Google Ads API and AdWords API can both be used in production systems, we'd like to clarify a couple of policy items.

Terms and Conditions
You will need to accept our updated Terms and Conditions to access production-ready versions of the Google Ads API. If you attempt to access v1 without accepting the new terms, your request will fail with the error AuthorizationError.MISSING_TOS. Existing AdWords API users will not be required to re-accept the new Terms and Conditions to access the legacy API. For instructions on how to accept the new terms, please take a look at this blog post.

Rate Limits
All Google Ads API rate limits are independent of a developer's use of the AdWords API. If a developer token with Basic Access sends a request to one Ads API, the daily request limit for the other API will not be affected.

Furthermore, daily limits for Basic Access developer tokens are different in the Google Ads API than in the AdWords API. They have been set to accommodate the new GoogleAdsService, which is the unified object retrieval and reporting service. Developer tokens with Basic Access can issue 15,000 requests per day. GoogleAdsService.Search requests with the page_token field set, will not count towards the Basic Access limit.

  • Note: All developer tokens are subject to the daily limit of 1,000 get requests.
Required Minimum Functionality (RMF)
Standard Access tools will continue to be subject to RMF policies. As these tools migrate their functionalities off of the legacy API, they can achieve RMF compliance by using either the AdWords API, Google Ads API or a combination of the two. Required features that are available in both APIs will be documented on both developer sites.

The Google Ads API RMF guide will contain the most up to date RMF list. This list will be made up of RMF items available in the AdWords API as well as new required functionalities that will be made available only in the Google Ads API. RMF due dates for new features will take into account migration efforts from the AdWords API to the Google Ads API.

For more information on these policy updates, please take a look at the following Google Ads API resources: If you have any questions or need help, please contact us via the forum.