Google Ads Developer Blog: release

Announcing v3_1 of the Google Ads API beta

Wednesday, April 29, 2020

Today we’re announcing the v3_1 release of the Google Ads API beta. To use the v3_1 features, please update your client library. If you are upgrading from v1 or v2, some of your code may require changes when you switch to the new v3 endpoint. Please see the migration guide for more information on breaking changes.

Here are the highlights:

Added support for retrieving campaign optimization score in Campaign.optimization_score.
Added new conversion action categories to ConversionActionCategory. See the release notes for details.
Added a new service OfflineUserDataJobService which supports asynchronous upload of Customer Match data and store sales (direct upload) data. These features are whitelisted.
Added support for retrieving the paying manager customer with PaymentsAccount.paying_manager_customer when making a request to PaymentsAccountService.ListPaymentsAccounts().

Where can I learn more?
The following resources can help you get going with the Google Ads API:

The updated client libraries and code examples will be published next week. If you have any questions or need additional help, please contact us via the forum.

Nadine Wang, on behalf of the Google Ads API Team

Join the beta for the new AdMob API

Thursday, April 2, 2020

Today we’re announcing the open beta release of the AdMob API v1. It offers a new and improved way to interact with AdMob reporting data programmatically. Built with app publishers in mind, the new AdMob API will replace the need for you to use the AdSense API and provide enhanced capabilities to query AdMob reporting data. For example, unlike the AdSense API that uses different definitions of certain ads metrics for app publishers, the AdMob API includes metrics that are consistent with the AdMob UI. The AdMob API v1 beta release offers the following benefits for app publishers:

Receive metrics that are more accurate and consistent with the AdMob UI.

Gain access to mediation reporting programmatically.

Integrate newer technologies like JSON REST into your product sooner.

We will continue to make improvements to the AdMob API and we encourage you to join the open beta now and provide feedback to influence the product roadmap before the general release. How can I join the beta? The beta is available to all AdMob users. You can start with the Getting Started guide or use the client libraries that we have created for you. Additional client library samples will be coming soon. Where can I learn more?

Guides

Reference

Client Library Samples

If you have any questions or need additional help, please contact us via the forum. We look forward to hearing your feedback.

- Amira Badreldin, AdMob API team

Introducing Display & Video 360 API v1

Monday, March 9, 2020

Today we’re releasing the Display & Video 360 API v1. It offers a new, improved way to interact with your Display & Video 360 resources programmatically.

This initial API release includes new asynchronous Structured Data File (SDF) download functionality. This allows for the generation and downloading of large SDFs without worrying about individual API requests timing out. This is a change compared to the existing DoubleClick Bid Manager (DBM) API SDF Download service. Along with this change, other major changes include:

New default version logic that utilizes the default version of the partner or advertiser specified by the user.
New filter capabilities, including the ability to specify the exact resources to include in the generated files.
New response format that returns the generated SDFs as a .zip file to download, rather than JSON.

The Display Video 360 API SDF Download service will be replacing the DBM API SDF Download service. The deprecation of that service will be announced soon, and an immediate migration to the new API is advised. You can get started setting up the Display & Video 360 API here, and downloading Structured Data Files here.

More functionality will be coming to the Display & Video 360 API in the coming months, including line item management and targeting. Keep an eye out for future announcements!

- Trevor Mulchay, Display & Video 360 API Team

Announcing v3_0 of the Google Ads API beta

Thursday, February 27, 2020

Today we’re announcing the v3_0 release of the Google Ads API beta. To use the v3_0 features via the new endpoint, please update your client libraries. If you are upgrading from v1 or v2, some of your code may require changes when you switch to the new v3 endpoint. Please see the migration guide for more information on breaking changes.

Here are the highlights:

Added the ability to stream results from GoogleAdsService.SearchStream(). This is the recommended way for retrieving large scale data from GoogleAdsSearch. Please see this guide for more details.
Added support for moving a client customer to a new manager customer with CustomerManagerLinkService.MoveManagerLink().
Added PaymentMode.GUEST_STAY to enable the pay per stay mode of Hotels Commissions campaigns. This payment mode can only be used in conjunction with campaigns with AdvertisingChannelType.HOTEL, BiddingStrategyType.COMMISSION, and BudgetType.HOTEL_ADS_COMMISSION.

Where can I learn more?
The following resources can help you get going with the Google Ads API:

The updated client libraries and code examples will be published next week. If you have any questions or need additional help, please contact us via the forum.

Nadine Wang, on behalf of the Google Ads API Team

Announcing v202002 of the Google Ad Manager API

Tuesday, February 11, 2020

We're happy to announce that v202002 of the Google Ad Manager API is available starting today. This version includes several new features around video ads.

For “Ad Exchange historical” reports, there are several new video Columns available beginning with “AD_EXCHANGE_VIDEO_”. Here are a few of the new metrics:

AD_EXCHANGE_VIDEO_START – the number of impressions where the video was played for video ads by Ad Exchange properties
AD_EXCHANGE_VIDEO_SKIPS – The number of times a skippable video is skipped
AD_EXCHANGE_VIDEO_UNMUTE – The number of times a user unmutes the video ad

You can now associate a video Creative with an ad registry, such as Ad-ID or Clearcast. Video metadata is also getting enhanced with the addition of Content.contentBundleIds to show which ContentBundles a Content object belongs to and Content.cmsMetadataValueIds to show which CmsMetadataValues are associated with a Content object.

The release notes contain the full list of API changes for v202002 and all other active API versions.

Feel free to reach out to us on the Ad Manager API forum with any API-related questions.

- Donovan McMurray, Ad Manager API Team

Announcing v201911 of the Google Ad Manager API

Tuesday, November 5, 2019

We're happy to announce that v201911 of the Google Ad Manager API is available starting today. This version brings new reporting and video features, unlocking new possibilities for automation in your Ad Manager network.

Reporting

Video

If you’re on an older version of the Ad Manager API, now is a great time to upgrade to take advantage of these and other recent features like the TargetingPresetService, which was added in v201905. The release notes contain the full list of API changes for v201911 and all other active API versions.

Feel free to reach out to us on the Ad Manager API forum with any API-related questions.

- Donovan McMurray, Ad Manager API Team

Announcing v201908 of the Google Ad Manager API

Tuesday, August 13, 2019

We're happy to announce that v201908 of the Google Ad Manager API is available starting today. There are several highly requested features in this new version of the API.

Reporting

Programmatic

Programmatic LineItems and ProposalLineItems now have an allowedFormats field, which gives publishers more control over what types of creatives a buyer can add.

LiveStreamEvents

You can now use the slateCreativeId field to programmatically set live stream slates, which are shown during gaps in a live stream ad break that cannot be filled with a dynamically served ad.

The release notes contain the full list of API changes for v201908.

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

- Donovan McMurray, Ad Manager API Team

Announcing v2_1 of the Google Ads API beta

Thursday, August 8, 2019

Today we’re announcing the v2_1 releases of the Google Ads API beta. To use the v2_1 features via the new endpoint, please update update your client libraries. If you are upgrading from v1, some of your code may break when you switch to the new v2 endpoint. Please see the migration guide for more information on breaking changes.

Here are the highlights:

Introduced AdService for updating existing ads that were created using AdGroupAdService. Updating ads maintains existing metrics.
Introduced summary rows when retrieving data from GoogleAdService.Search() by setting return_summary_row to true in the request. The summary row contains the report totals.
Introduced the AdGroupAdAssetView resource for querying ad asset metrics.
Introduced the DistanceView resource (equivalent to the User Ad Distance Report in the AdWords API).
Introduced the UserLocationView resource (equivalent to the Geo Performance Report where isTargetingLocation is false in the AdWords API).
Added the ability to retrieve all label resource names associated with the AdGroup resource using AdGroup.labels and with the Campaign resource using Campaign.labels.
Added time_zone, test_account, manager, descriptive_name, currency_code, and id to CustomerClient to make it easier to retrieve customers in an account hierarchy.

Where can I learn more?
The following resources can help you get going with the Google Ads API:

The updated client libraries and code examples will be published by August 16. If you have any questions or need additional help, please contact us via the forum.

Nadine Sundquist, on behalf of the Google Ads API Team

Announcing v1_3 of the Google Ads API

Wednesday, May 22, 2019

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:

Added support for campaign drafts and experiments with the CampaignDraft and CampaignExperiment resources (equivalent to Campaign Drafts and Experiments in the AdWords API).
Added the ability to retrieve all label resource names associated with the Campaign resource using Campaign.labels.

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

Announcing v201905 of the Google Ad Manager API

Tuesday, May 21, 2019

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.

- Chris Seeley, Ad Manager API Team

Announcing v1_2 of the Google Ads API

Tuesday, April 30, 2019

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:

Release Notes
Guides
Migration Guides
Reference

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

Announcing v1_1 of the Google Ads API

Wednesday, March 27, 2019

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

Tuesday, March 5, 2019

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

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

Monday, March 4, 2019

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.

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.

--Google Ads API Team

Announcing v201902 of the Google Ad Manager API

Tuesday, February 12, 2019

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.

- Donovan McMurray, Ad Manager API Team

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

Friday, February 8, 2019

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!

- Jonathon Imperiosi, DCM API Team

Announcing v0_7 of the Google Ads API

Wednesday, January 30, 2019

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:

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.

Nadine Sundquist, on behalf of the Google Ads API Team

Announcing v0_6 of the Google Ads API

Thursday, November 29, 2018

Updated on Nov 30: Added highlight for Billing. 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:

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.

Nadine Sundquist, on behalf of the Google Ads API Team

Announcing v0_5 of the Google Ads API

Wednesday, October 31, 2018

Today we’re announcing the beta release of Google Ads API v0_5. 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:

Billing. Multiple services are available for managing billing.
- BillingSetupService
  - Create a new billing setup
  - Cancel an approved billing setup that is scheduled to start in the future
  - Cancel a pending billing setup that is not yet approved
- AccountBudgetService
  - View all approved account-level budgets, including budget adjustments
  - View currently pending account-level budget proposals (if any)
- AccountBudgetProposalService
  - Create account-level budget proposal to update a budget or create a new budget
  - View all account-level budget proposals. All approved values and proposed budget values are visible. Approved values will be exposed as fields prefixed with approved_.
Conversion tracking. Conversion tracking lets you measure the performance of your advertising against your business goals.
- Conversion actions - Set up and edit the settings associated with your conversion actions, including website tracking and call-conversion tracking
Shopping. The ProductGroupView resource provides Shopping campaign statistics aggregated at the product group level (also called listing group in the Google Ads API). Results always reflect the current set of product groups. An impression for a product will be attributed to all product groups that contain the product. ProductGroupView provides features equivalent to the Product Partition Report of AdWords API.
Location and Demographics. You can now create criteria with CriterionType AGE_RANGE, GENDER, INCOME_RANGE, PARENTAL_STATUS, PLACEMENT, PROXIMITY, TOPIC, YOUTUBE_CHANNEL, and YOUTUBE_VIDEO. The GeoTargetConstantService lets you input locations and receive suggested geos.
Account Management. CustomerService.ListAccessibleCustomers provides the capability to manage Google Ads accounts.

To get started with the API, review these helpful resources:

The updated client libraries and code examples will be published within the next 48 hours. If you have any questions or need help, please contact us via the forum.

Nadine Sundquist, on behalf of the Google Ads API Team

Announcing v0_4 of the Google Ads API

Monday, September 24, 2018

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

Retrieve the AdGroupAdPolicySummary to determine why an ad has been disapproved.

Change History.

AD_GROUP
AD_GROUP_AD
AD_GROUP_CRITERION
CAMPAIGN
CAMPAIGN_CRITERION

Search for changed resources using GoogleAdsService.Search.

Conversion tracking. Conversion tracking lets you measure the performance of your advertising against your business goals. The API allows you to set up and edit your conversion tracking setup. With ConversionActions, you can set up and edit the settings associated with your conversion actions supporting:

AD_CALL
CLICK_TO_CALL
GOOGLE_PLAY_DOWNLOAD
GOOGLE_PLAY_IN_APP_PURCHASE
UPLOAD_CALLS
UPLOAD_CLICKS
WEBPAGE
WEBSITE_CALL

Shopping. Shopping campaigns help you promote your online and local inventory, boost traffic to your website or local store, and find better qualified leads.

This release supports the creation of standard Shopping campaigns with Shopping Product Ads. Portfolio and campaign-local bidding strategies are supported types MANUAL_CPC, ENHANCED_CPC, TARGET_SPEND, TARGET_ROAS. Product offers can be subdivided into groups using the ListingGroupInfo criterion (equivalent to Product Groups in the Google Ads user interface), which currently supports the following dimension types: Product Condition, Product Type, Listing Brand, Listing Custom Attribute (L0-4), Product Channel, Product Channel Exclusivity, Product Offer Id.

Video.

Retrieve information about your video campaigns from GoogleAdsService.Search, which includes video-specific metrics including video views, video view rate, video quartiles, and view-through conversions.

Ruby client library. When upgrading your client library, please look at the ChangeLog as the require path and namespace have changed in this version.

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

The updated client libraries and code examples will be published within the next 48 hours. If you have any questions or need help, please contact us via the forum.

Nadine Sundquist, on behalf of the Google Ads API Team

Ads Developer Blog

Announcing v3_1 of the Google Ads API beta

Join the beta for the new AdMob API

Introducing Display & Video 360 API v1

Announcing v3_0 of the Google Ads API beta

Announcing v202002 of the Google Ad Manager API

Announcing v201911 of the Google Ad Manager API

Announcing v201908 of the Google Ad Manager API

Announcing v2_1 of the Google Ads API beta

Announcing v1_3 of the Google Ads API

Announcing v201905 of the Google Ad Manager API

Announcing v1_2 of the Google Ads API

Announcing v1_1 of the Google Ads API

Google Ads API Policy Notes

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

Announcing v201902 of the Google Ad Manager API

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

Announcing v0_7 of the Google Ads API

Announcing v0_6 of the Google Ads API

Announcing v0_5 of the Google Ads API

Announcing v0_4 of the Google Ads API

Labels

Archive

Feeds

Google Ads API [+]

AdWords API [+]

Google Ads scripts [+]

Content API for Shopping [+]

Google Ad Manager API [+]

DCM API [+]

Mobile Ads [+]

IMA SDK [+]