Category Archives: Ads Developer Blog

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

Upcoming changes to conversion action management

Starting August 22, 2022, the include_in_conversions_metric field of the ConversionAction resource will become read-only. Requests that attempt to set this value will result in a FieldError.IMMUTABLE_FIELD error.

Why is this change happening?
As part of the addition of conversion goals in Google Ads, the new primary_for_goal field replaced the include_in_conversions_metric field. To ease the transition to the new field while we enabled goals on all accounts, the Google Ads API allowed you to continue to set the deprecated include_in_conversions_metric field, and the API would automatically update primary_for_goal accordingly. However, now that conversion goals are enabled in all Google Ads accounts, we're preventing setting include_in_conversions_metric to avoid conflicts with primary_for_goal.

What should you do?
Modify any code that sets include_in_conversions_metrics to instead set primary_for_goal. In addition, review and modify any of your application logic that uses the conversion_action.include_in_conversions_metric field in reports. Check out the conversion goals guide for more information on how the primary_for_goal setting impacts bidding and reporting.

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

Upcoming changes to conversion action management

Starting August 22, 2022, the include_in_conversions_metric field of the ConversionAction resource will become read-only. Requests that attempt to set this value will result in a FieldError.IMMUTABLE_FIELD error.

Why is this change happening?
As part of the addition of conversion goals in Google Ads, the new primary_for_goal field replaced the include_in_conversions_metric field. To ease the transition to the new field while we enabled goals on all accounts, the Google Ads API allowed you to continue to set the deprecated include_in_conversions_metric field, and the API would automatically update primary_for_goal accordingly. However, now that conversion goals are enabled in all Google Ads accounts, we're preventing setting include_in_conversions_metric to avoid conflicts with primary_for_goal.

What should you do?
Modify any code that sets include_in_conversions_metrics to instead set primary_for_goal. In addition, review and modify any of your application logic that uses the conversion_action.include_in_conversions_metric field in reports. Check out the conversion goals guide for more information on how the primary_for_goal setting impacts bidding and reporting.

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

Announcing Bid Manager API v2

We are pleased to announce that version 2 of the Bid Manager API is now available. Notable features added in this version include: This new version also includes significant changes to be aware of, such as:
  • The changing of the base Bid Manager API URL.
  • The renaming of existing services and methods.
  • The restructuring of Query and Report resources to use new named object types and enums.
  • The updating of method functionality to require queries to be run manually after creation.
  • The rewording of existing error messages to be more detailed and prescriptive.
More detailed information about this update can be found in the Bid Manager API release notes. Follow the steps on our migration guide to help you migrate from v1.1 to v2.

If you run into issues or need help with these new features or samples, please contact us using our support contact form.
- Trevor Mulchay, Display & Video 360 API Team

Get started scripting with Google Ads scripts templates

Today we’re launching scripts templates, a quick and easy way to get started with scripting in Google Ads. Instead of starting your script from scratch, you can choose from a list of templates, edit to fit your account, and deploy them.

To get started, visit the scripts page and click on the plus (+) button, then Start from a template:

Next, pick a template and click Customize to begin editing.

If you have any questions or feedback regarding the new experience, please leave a post on our forum so that we can help.
Posted by David Stevens, Product Manager, Google Ads

The Video.js-IMA plugin adds DAI support for HLS streams

The IMA Dynamic Ad Insertion (DAI) SDK lets apps make stream requests for ad and content video streams, either VOD or live content. The SDK then enables a video player to play the combined stream so you don't have to manage switching between ad and content video within your apps.

To improve support for HTML5 publishers, we have expanded the features provided by the Video.js-IMA plugin to include DAI for HLS streams. With the latest version of the plugin, you can enable a Video.js player to request ads and content in a single HLS stream. Check out the new DAI sample app and the DAI README file for implementation details on how the Video.js-IMA plugin can simplify your IMA DAI integration.

For more information on IMA DAI, please see the IMA HTML5 DAI getting started guide. If you have any questions or feedback about using DAI with the Video.js-IMA plugin, please raise an issue on GitHub.

 - Jackson Sui, Interactive Media Ads Developer Relations

Merchant IDs as 64-bit in Content API for Shopping

In the Content API for Shopping, Merchant IDs are now 64-bit signed integers. Applications that integrate with the Content API must be able to handle ID values in that range.

Historically, Merchant IDs in the Content API for Shopping were within the maximum value of a 32-bit signed integer, but have recently exceeded this range. In order to avoid any issues, please make sure your applications are fully compliant with IDs within a range of 64-bit signed integer values.

If you have any questions or concerns, please don't hesitate to contact us via the forum.
Benji Rothman, Content API for Shopping Team

Announcing v4 of the Campaign Manager 360 API

Today we're releasing v4 of the Campaign Manager 360 API. This release adds support for the following Billing Services:
  • Advertiser Invoices
  • Billing Assignments
  • Billing Profiles
  • Billing Rates
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 depreciation period for v3.5, which will sunset on Feb 15, 2023. After this date, any requests made against v3.5 will begin returning errors.

See the migration guide for details. For most, you just need to upgrade to the latest version of your preferred client library. We recommend you to review the release notes to learn about important changes you might need to be aware of.

If you have questions about this or anything else Campaign Manager 360 API related, feel free to reach out to us on our support forum.

Learn More
As with every new version of the Campaign Manager 360 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!
- Yan Liu, CM360 API Team

Announcing v11 of the Google Ads API

Today, we’re announcing the v11 release of the Google Ads API. To use some of the v11 features, you will need to upgrade your client libraries and client code. The updated client libraries and code examples will be published next week.
Here are the highlights: Where can I learn more?
The following resources can help you get started: If you have any questions or need additional help, contact us via the forum.
Thanet Knack Praneenararat, on behalf of the Google Ads API Team

Google Ads API v9 sunset reminder

Google Ads API v9 will sunset on July 13, 2022. On this date, v9 API requests will begin to fail. Please migrate to a newer version before July 13, 2022 to ensure your API access is unaffected.

We've prepared various resources to help you with the migration: If you have questions while you’re upgrading, please reach out to us on the forum or at [email protected].
- Thanet Knack Praneenararat, Google Ads API Team

AdWords API has Officially Sunset

As previously announced, the error rate for requests to the AdWords API will start increasing toward 100% beginning on May 31, 2022. If you are currently using the AdWords API, you need to upgrade to the Google Ads API now or your applications will experience an increased rate of errors per the schedule below:
Starting Date AdWords API Error Rate
June 1, 2022 50% errors
July 1, 2022 60% errors
July 8, 2022 70% errors
July 15, 2022 80% errors
July 22, 2022 90% errors
July 31, 2022 100% errors
Starting July 31, 2022 all requests to the AdWords API will fail.

Where do I start?
See the following resources to get started: Here are some tools to help you migrate: Where can I get support?
If you have questions while you’re upgrading, please reach out to us on the forum or at [email protected].
- Cory Liseno, Google Ads API Team