Tag Archives: adwords_api

Content API for Shopping live webinar on May 31st (Mandarin, Chinese)

We are running a live webinar this Friday, May 31, on the Content API for Shopping. This webinar is for our Chinese-speaking developers that are interested in using the API to manage products and Shopping ads at scale.

The webinar will cover topics on:
  • Content API for Shopping use case
  • Merchant Center setup
  • Content API features
  • Best practices
  • API request/response demo
You will be able to submit questions throughout the live event. We will answer questions during the Q&A session in the webinar.

Note: The webinar content will be delivered in Mandarin, Chinese.

The webinar will begin at 10:00am (China Time, GMT +8) on Friday, May 31, 2019. Please contact us via the Content API forum if you have any questions or need help.

If you’d like to review some of our previous webinars covering the Google Ads API, you can find them at the following links: Fei Xiang, Google Ads API Team

Migrating from position to impression share bidding strategies in Google Ads

In June 2019, we will shut off the ability to add new Target Search Page Location and Target Outranking Share bidding strategies. This will affect both the AdWords API and the Google Ads API. Later this year, existing campaigns on these strategies will automatically be migrated to the new Target Impression Share bidding strategy, which offers more flexible and granular controls to optimize for your desired impression share and search page location.

Read on to see how this will affect your API usage.

Google Ads API Users
Please start using the TARGET_IMPRESSION_SHARE BiddingStrategyType rather than TARGET_OUTRANK_SHARE or PAGE_ONE_PROMOTED.

If you attempt to create a TARGET_OUTRANK_SHARE or PAGE_ONE_PROMOTED after they are removed, you will get an error.

AdWords API Users
If you attempt to use the AdWords API to add a TARGET_OUTRANK_SHARE or PAGE_ONE_PROMOTED bidding strategy after they are removed, you will get an error.

All existing campaigns using the old bidding strategies will be automatically migrated to use Target Impression Share for both APIs. The AdWords API does not support the Target Impression Share bidding strategy, so we recommend migrating to the Google Ads API if you need this functionality.

If you have any questions about this change or any other API feature, please contact us via the forum.
- Mike Cloonan, Google Ads API Team

Join us for a live webinar on Google Ads API and Hotel Ads

Please join us later this week for a livestream webinar covering the latest Hotel Ads features in the Google Ads API. In particular, we’ll cover using hotel listing groups and leveraging Hotel Ads-specific reporting features. We’ll also be answering some of your questions during the event.

The webinar will begin at 11:00am EDT on Thursday, May 30, 2019.
As always, please contact us via the Google Ads API forum if you have any questions or need help.

If you’d like to review some of our previous webinars on related topics, you can find them at the following links:
Adam Ohren, on behalf of the Google Ads API Team

Announcing v1_3 of the Google Ads API

Today we’re announcing the v1_3 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_3 features.

Here are the highlights: What resources are available?
The following resources should help you get going with v1_3 of the Google Ads API: The updated client libraries and code examples will be published by May 24, 2019. If you have any questions or need help, please contact us via the forum.
Nadine Sundquist, on behalf of the Google Ads API Team

Expanding your Shopping ads to additional Google platforms

YouTube and Google Discover power visually rich experiences and play a part of millions of users’ shopping journeys. Soon your Standard Shopping campaigns will be able to reach users who discover and continue their shopping journey on these additional Google platforms.

We’re excited to announce that Shopping ads (both Product Shopping ads and Showcase Shopping ads) in your standard Shopping campaigns will be eligible to appear on YouTube and Google Discover beginning the week of July 15th, 2019. Shopping ads served on YouTube and Google Discover will be reported under the Google Display Network.

In preparation for this change, standard Shopping campaigns that are enabled for Search Network will be automatically enabled for YouTube and Discover, beginning the week of June 17th, 2019. This means that any standard Shopping campaigns that target the Search Network will automatically enabled to target the Content Network. After this process, developers using the Google Ads API or the AdWords API can give users the ability to opt-in/opt-out. They can do this by changing the campaign target network as follows:
  • Google Ads API - Modify the NetworkSettings of the standard Shopping campaign to set target_content_network to true or false.
  • AdWords API - Modify the NetworkSetting of the standard Shopping campaign to set targetContentNetwork to true or false.
Ads with these settings will only be eligible to appear on YouTube and Google Discover from the week of July 15th, 2019. During that week, you may start seeing new metrics as part of your reporting data. Depending on which API you are using you can access the metrics by doing the following: Note: If you would like to upgrade to the Google Ads API from the AdWords API, please see more information our blog.

If you have any questions or need help, please contact us via the forum.
- Ian Ballantyne, on behalf of the Google Ads API Team

Reporting issues April 30 and May 1, 2019

On May 1, at approximately 5pm PST, a bug caused Google Ads reporting for April 30 and May 1 (Pacific Time) to be incorrect. This bug impacts reports in all Google Ads interfaces, including any report data downloaded via the AdWords API, Google Ads API and Google Ads Scripts.

We are actively working on fixing the bug and correcting the data. Metrics reported for May 2nd will also be delayed until later that morning PST.

We appreciate your patience as we work to resolve this issue as quickly as possible.

If you have any questions or need help, please contact us via the forum.
Adam Ohren, Google Ads API Team

Announcing v1_2 of the Google Ads API

Today we’re announcing the v1_2 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_2 features.

Here are the highlights: What resources are available?
The following resources should help you get going with v1_2 of the Google Ads API: The updated client libraries and code examples will be published by May 2, 2019. If you have any questions or need help, please contact us via the forum.
Nadine Sundquist, on behalf of the Google Ads API Team

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.
Ben Karl, Google Ads API Team

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.
Nadine Sundquist, Google Ads API Team

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.

Resources
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.
--Google Ads API Team