Today we’re releasing an update to the Display & Video 360 API that includes the following features:

• Support for targeting by content duration, stream type, and genre.
• A new billableOutcome field in the InsertionOrder object.
• The ability to manage whether a resource using a MaximizeSpendBidStrategy will apply the advertiser floor price for targeted deals through a new raiseBidForDeals field.

More detailed information about this update can be found in the Display & Video 360 API release notes. Before using these new features, make sure to update your client library to the latest version.

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

As previously announced, if you are a developer currently using the AdWords API, you must upgrade to the Google Ads API by April 27, 2022. On that date, the AdWords API will sunset and requests to the AdWords API will fail.

Where do I start?
If you need some resources to get started, check out:

• Migration checklist
• Migration workshop
• Migration videos

Here are some tools to help you migrate:

• Query migration tool
• Query builder
• Query validator

Where can I get support?
If you have questions while you’re upgrading, please reach out to us on the forum or at googleadsapi-support@google.com.
Nadine Wang, Google Ads API Team

Google Ads API v7 and v8 will sunset on May 11, 2022. After this date, all v7 and v8 API requests will begin to fail. Please migrate to a newer version prior to May 11, 2022 to ensure your API access is unaffected.

We've prepared various resources to help you with the migration:

• Upgrading to the newest version
• Release notes

In addition, using the Google Cloud Console, you can view the list of methods and services to which your project recently submitted requests:

1. Open the Dashboard page (found under APIs & Services) in the Google Cloud Console.
2. Click on Google Ads API in the table.
3. On the METRICS subtab, you should see your recent requests plotted on each graph. At the bottom of the page, you’ll see the Methods table, where you can see which methods you’ve sent requests to. The method name includes a Google Ads API version, a service, and a method name, e.g., google.ads.googleads.v10.services.GoogleAdsService.Mutate.In this way, you can see all versions that you’ve used recently.
4. (Optional) Click on the time frame at the top right of the page if you need to change it.

If you have questions while you’re upgrading, please reach out to us on the forum or at googleadsapi-support@google.com.
 - Thanet Knack Praneenararat, Google Ads API Team

As we announced in January, existing and future Smart Shopping campaigns (SSC) will automatically upgrade to Performance Max campaigns between July and September 2022.

As mentioned in the prior blog post, users will be able to self-upgrade in the UI starting April 2022. Developers will be able to self-upgrade in the API before the end of June. We expect the vast majority of accounts managed by the API will opt to wait to self-upgrade once the tool is available in the API in June. However, campaigns may be upgraded manually by advertisers in the UI starting in April. We recommend you implement Performance Max in your application now to ensure support for any new or upgraded Performance Max campaigns.

An upgraded SSC will be marked as REMOVED status (metrics will continue to be available in the legacy campaign for historical purposes). There will also be a mapping from the previous campaign ID to the new Performance Max campaign ID. Budgets, assets, and settings of the existing SSC are preserved.

The prior blog post had April / May 2022 as the estimated availability date for the API's new self-upgrade recommendation type. This will be available before the end of June. There will still be a six week period between availability of the new recommendation type in the API and the start of auto-upgrades.

Note that once a campaign has been upgraded, either by the UI or API, there is no means to revert the upgrade. Metrics will continue to be available in the legacy campaign for historical purposes.

Additional information

If you have any questions or need additional help, contact us via the forum.

David Wihl, Google Ads API Team

Today we’re launching the full version of the new Google Ads scripts experience. The beta has been running since June of last year, and now the final batch of features to match the functionality of legacy scripts has been released.

Starting soon, all new scripts will default to the new scripts experience, although you can still disable it on a script by script basis if necessary. Existing scripts won't be affected until September of 2022. After that, we will migrate all scripts to the new experience. You should manually move your scripts over to the new experience before then to ensure continued functionality. We've tried to implement backwards compatibility, but we can't guarantee every script will work without changes, so definitely take some time to confirm yourself.

Here are some highlight features in the new experience:

• Support for ES6, including let, classes, for..of loops, and more.
• Improved throughput, meaning you can process more entities in the same amount of time. We've also removed the entity limits on processing, although time limits remain in place.
• Support for new asset-based extensions.
• Enhanced bidding strategy support.

The following features are added in this release:

• Manager account scripts
• Bulk upload
• Video campaigns

See the updated Google Ads scripts site for full information on the new experience, including migration information, performance improvements, and updated best practices. This replaces the documentation for the legacy scripts experience, but if you must reference that we will preserve it at a new location until the legacy scripts sunset: https://developers.google.com/google-ads/scripts-legacy

If you have any questions or feedback regarding the new experience, please leave a post on our forum so that we can help.
- Mike Cloonan, Google Ads Scripts Team

What’s changing?
Starting the week of March 28, 2022, the Google Ads API will no longer throw an AssetError.CANNOT_MODIFY_ASSET_NAME in versions v7, v8 and v9 when uploading an asset with duplicate content but a different Asset.name. Instead, the Google Ads API will ignore the new name and return the resource name of the existing asset.

This change affects the following asset types.

• Image
• Media Bundle
• Text
• Call to Action
• Book on Google

Background
When creating a new asset using AssetService.MutateAssets, the Google Ads API detects if the uploaded asset has the same content as an existing asset but a different name and raises an AssetError.CANNOT_MODIFY_ASSET_NAME in versions v7, v8 and v9. We observed that it was not easy for users to troubleshoot this error, so starting with version v10, the Google Ads API ignores the new name and returns the resource name of the existing asset if an asset with duplicate content is detected. To keep the API experience consistent, we are making the same changes to versions v7, v8 and v9 of Google Ads API.

What should you do?
Once this change goes live, the AssetError.CANNOT_MODIFY_ASSET_NAME error won’t be thrown when uploading an asset with duplicate content and a different name. If your application handles this error, please review and make changes to match the new API behavior.

If you have any questions or need additional help, contact us using any of the following support options:

• Email: googleadsapi-support@google.com
• Support forum: https://groups.google.com/forum/#!forum/adwords-api

- Anash P. Oommen, Google Ads API Team