Tag Archives: release

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.

Announcing v201905 of the Google Ad Manager API

We're happy to announce that v201905 of the Google Ad Manager API is available starting today. This version introduces a long-requested feature: Targeting Presets. The new TargetingPresetService allows you to read your network's targeting presets in a familiar Targeting object that can be applied to line items, forecasts, and proposal line items.

This release also introduces support for configuring and reporting on custom dimensions, and new Programmatic features such as Pause and Resume actions for Proposals.

For a full list of API changes in v201905, see the release notes.

For questions about these or any other API changes, reach out to us on the Ad Manager API forums.

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.

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.

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.

Upgrade to the new Google Ads API to get the latest services

Today we’re announcing the production-ready release of the Google Ads API. You should start using v1 in your production systems as we are now out of beta. The v0 beta version of Google Ads API will sunset on April 30, 2019. After this date, all v0 requests will begin to fail. You’ll be pointing to a new v1 endpoint which is different from the v0 endpoint. Please update your client libraries to use the v1 endpoint.

What is the Google Ads API?
The Google Ads API is the replacement of our AdWords API and brings significant advances in innovation and developer productivity. It can be accessed via gRPC with our client libraries and JSON REST for debugging. We are working on getting the last few features released so that all the features in the AdWords API also exist in the Google Ads API. In addition, new features are being added to the Google Ads API that will not be available in the AdWords API.
  • Google Ads Query Language makes querying more flexible.
  • Querying returns objects that can immediately be updated in the API.
  • Coding becomes easier as interacting with lists is more intuitive.
  • Querying and managing budgets is available to everyone for accounts using consolidated billing.
  • You can query, apply, and dismiss Recommendations.
  • Most resources can be mutated synchronously through a single service.
  • Querying change status in the API is more detailed.
How do I get started?
For existing AdWords API developers:
  • Use your existing developer token from the AdWords API.
  • Important: The Terms and Conditions have changed. You’ll need to accept the updated Terms and Conditions and update your contact information in API center. If you don’t, you will get an error when trying to access v1.
    • Sign into the API Center of the manager account where you have your developer token at ads.google.com/aw/apicenter.
    • Scroll down to API contact email, and update it.
    • Scroll down to Principal place of business, accept the new conditions, and click Save.
For new API developers, sign up for a developer token.

Everyone should go through our Quickstart guide to enable Google Ads API and retrieve the newest client libraries.

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

Announcing v201902 of the Google Ad Manager API

We're happy to announce that v201902 of the Google Ad Manager API is available starting today. The two main areas that are getting new API functionality are forecasting and video.

In v201902, you can set LineItems to be paced based on their projected traffic instead of their historical traffic by setting DeliveryForecastSource to FORECASTING. This API version also adds the AdjustmentService to manage traffic forecast adjustments. For example, if you’re expecting an increase in traffic for an upcoming holiday, you can manually adjust your forecasts to take that increase into consideration.

There are also several updates to video features in this version of the API. You can now target LineItems by CmsMetadataValues (content targeting) and custom AdSpots (position targeting).

For a full list of API changes in v201902, see the release notes.

For questions about this or any other API changes, reach out to us on the Ad Manager API forum.

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

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

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.2, which will sunset on August 31, 2019. After this date, any requests made against v3.2 will begin returning errors.

As a final reminder, API version 3.1 will be sunset on February 28, 2019. 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!

Announcing v0_7 of the Google Ads API

Today we’re announcing the beta release of the Google Ads API v0_7. With this version, you’ll continue pointing to v0 as your endpoint; however, you'll need to update your client libraries. Here are the highlights:
  • Request Parameters. These parameters give you the ability to change how a request is processed.
    • Set validate_only to true as a request parameter to only validate the request, but not perform it. This was added to all services including GoogleAdsService.Mutate().
    • Set partial_failure to true as a mutate parameter to continue on failure and commit valid operations even if other operations in the same request failed.
  • Reporting. All segment fields are now in a segments, which means all queries must be updated to include segments. before the segment field name.
  • Manager accounts. We've added support for mutating your customer hierarchy with CustomerManagerLink and CustomerClientLink.
  • Client accounts. We’ve introduced fields to identify if a customer is a test account or a manager account. The conversion tracking settings of a customer are now available.
  • Ad formats. We’ve added support for managing ad parameters with the AdParameterService.
  • Audiences. The targeting setting in campaigns and ad groups is now available. We’ve added support for rule-based, logical, and basic user lists. You can now manage remarketing actions for a basic user list.
  • Criteria types. Creating criteria with CriterionType MOBILE_APP_CATEGORY, WEBPAGE, OPERATING_SYSTEM_VERSION, and APP_PAYMENT_MODEL is now possible.
To get started with the API, review these helpful resources: The updated client libraries and code examples will be published within the next 2 business days. If you have any questions or need help, please contact us via the forum.

Announcing v0_6 of the Google Ads API

Today we’re announcing the beta release of Google Ads API v0_6. This release brings you the features listed in Required Minimum Functionality (RMF). Now that the core functionality of this new API is available, you should get started planning, designing, and coding against it. With this version, you’ll continue pointing to v0 as your endpoint, however, you'll need to update your client libraries. Here are the highlights:
  • Manager account authentication: If you’re authenticating as a manager account, the manager account you want for authorization must be in the header as login-customer-id. You then set the customer you want to interact with in the request as usual. This tells the API the level of manager account hierarchy you want to authenticate with.
  • Mix mutate operations: Pass in multiple kinds of operations with GoogleAdsService.Mutate.
  • Hotel Ads: We extended the GoogleAdsService to enable users to query hotel performance metrics that were previously available in the Travel Partner API with the HotelPerformanceView. Supported performance metrics are cost, clicks, impressions, and average lead values. Some derived metrics are also precomputed: average position, average cost per click, average cost per thousand impressions, and click-through rate. These metrics can be segmented by:
    • Itinerary segments: check-in date, check-in day of week, booking window days, and date selection type
    • Hotel segments: hotel center ID, hotel ID, class, city, state, and country
    • Date segments: hour, date, day of week, week, month, quarter, and year
    • Others: campaign, ad group, ad network, and device
  • Feeds: Manage and retrieve feeds with AdGroupFeedService, CustomerFeedService, FeedService, CampaignFeedService, and FeedMappingService.
  • Account management:
    • We introduced CustomerClient, which provides the ability to get an expanded hierarchy of customer clients (both direct and indirect) for a given manager customer.
    • This release also supports the creation of new customer clients under a manager using the CustomerService.CreateCustomerClient method.
    • CustomerService now supports mutates.
  • Recommendations: Added the DismissRecommendation method to the RecommendationService, making it possible to dismiss the recommendations listed in our guide.
  • Ad formats: Gmail ads and image ads are now supported.
  • Search query reporting: The SearchTermView resource is now available, providing metrics aggregated at the search term level. SearchTermView provides functionality similar to the Search Query Performance Report of the AdWords API.
  • Audiences: Create audiences using UserListService.
  • Criteria types: You can now create criteria with CriterionType LANGUAGE, CARRIER, USER_LIST, USER_INTEREST and IP_BLOCK.
To get started with the API, review these helpful resources: The updated client libraries and code examples will be published within the next 2 business days. If you have any questions or need help, please contact us via the forum.