Category Archives: Ads Developer Blog

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

Changes to handling duplicate assets in Google Ads API

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. 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: - Anash P. Oommen, Google Ads API Team

Announcing v202202 of the Google Ad Manager API

We're pleased to announce that v202202 of the Google Ad Manager API is available starting today, February 28th. This release brings a long-awaited feature – Ad Manager hosted video creatives. Simply provide a URL for the video asset, and Ad Manager will read and transcode it.

While API support has been added, this feature is still rolling out to Ad Manager networks and may not yet be available in yours. Networks with this feature disabled will continue to receive CreativeSetError.CANNOT_CREATE_OR_UPDATE_VIDEO_CREATIVES.

MCM companies now include information about the status of onboarding tasks and Sellers.json identifiers.

There are also some maintenance updates removing deprecated features, like AdExclusionRuleService and Proposal pause information.

For the full list of changes, check the release notes. Feel free to reach out to us on the Ad Manager API forum with any API-related questions.

- Chris Seeley, Ad Manager API Team

Important changes to placement reporting for App Campaigns

On January 5, 2022, we removed all App campaign placement data from the following reports:

Google Ads API AdWords API / Google Ads scripts We made this change because the data provided didn’t fully represent the complete view of the placements that help developers monitor brand safety for their advertisers. If you use these reports, see the App Campaigns Brand Safety Placement report in the Google Ads UI.

If you have AdWords API or Google Ads API related questions about this change, please reach out to us on the API forum or at [email protected]. Note: AdWords API developers must migrate to Google Ads API by April 27, 2022

If you have any Google Ads scripts related questions, please reach out to us on the scripts forum.
Ian Ballantyne, Google Ads API Team

Changes in Network Settings for the Google Ads Standard Shopping Campaigns

On February 14, 2022, Google Ads stopped serving standard Shopping campaigns on the Google Display Network, including on Gmail, Discover, and some YouTube placements. As a result, the AdWords API, Google Ads API and Google Ads scripts will make similar changes to their behavior starting the week of February 28, 2022.

AdWords API
The AdWords API will sunset on April 27th, so you must migrate to the Google Ads API by then.

In the AdWords API, the Campaign.NetworkSetting.targetContentNetwork field will always return false for standard Shopping campaigns, which are defined as campaigns where the advertisingChannelType is set to SHOPPING, and the advertisingChannelSubType is unset. If you try to set Campaign.NetworkSetting.targetContentNetwork to true, it will be ignored.

When running reports, the API will stop returning metrics for AdNetworkType1 and AdNetworkType2 of type: CONTENT, YOUTUBE_SEARCH, or YOUTUBE_WATCH for standard Shopping campaigns for date ranges after February 14, 2022. You can still download historic metrics for these fields and values.

Google Ads API
Versions v8 and v9 of the Google Ads API will behave the same way as the AdWords API – the network_settings.target_content_network field will return false, and if you try to set this field to true, it will be ignored. In version v10 and beyond, if you try to set this field to true a CANNOT_TARGET_CONTENT_NETWORK error will be returned.

When running reports, the API will stop returning metrics for these campaigns for segments.ad_network_type of type: CONTENT, YOUTUBE_SEARCH, or YOUTUBE_WATCH for date ranges after February 14, 2022. You can still download historic metrics for this field and values.

Google Ads scripts
If you use bulk uploads to target a standard Shopping campaign for Google Display Network, the server will ignore the setting.

When generating reports, the behavior will be the same for standard Shopping campaigns, independent of the method that you use:
  • With the AdsApp.report() method, reports will stop returning metrics for AdNetworkType1 and AdNetworkType2 of type: CONTENT, YOUTUBE_SEARCH, or YOUTUBE_WATCH for date ranges after Feb 14, 2022.
  • With the AdsApp.search() method, the API will stop returning metrics for segments.ad_network_type of type: CONTENT, YOUTUBE_SEARCH, or YOUTUBE_WATCH for date ranges after Feb 14, 2022.
Historical metrics will still be available.

If you would like to retrieve any existing standard Shopping campaigns before their network settings are changed, be sure to do so before Feb. 28, 2022.

If you have any questions about this change, please feel free to contact us through the forum or at [email protected] for additional help.
- Ben Karl, on behalf of the Google Ads API Team

Google Ads API v10 RMF Update

Effective with Google Ads API version 10, we updated the Required Minimum Functionality (RMF) to use the Google Ads API. This is to reflect the evolution of the Google Ads platform, including the upgrade of Smart Shopping and Local Campaigns to Performance Max. We also published the requirements for Standard Shopping, Hotel-only and App Promotion-only tools.

There is a new product specific RMF for Smart Campaigns. This is not a requirement for all tools, only those that implement Smart Campaigns. If you use Smart Campaigns, this defines the minimum set of features that are required.

The minimum set of features for Performance Max campaigns are now available.

These changes will affect the following tools:
  • Shopping-only, Smart Shopping-only API tools
  • Special purpose tools that offer campaign creation or management functionality
These changes will not affect full-service, Hotel-only, App Promotion-only or reporting-only tools.

For precise details, see the updated Google Ads API Required Minimum Functionality.

Requirements for the AdWords API remain unchanged.

Standard Shopping Campaigns
With the release of Google Ads API v9, we simplified RMF requirements for Full-service tools. We are now making the same changes to Standard Shopping Campaigns.

The following features are still required but simplified or reduced in scope:
Item Number Functionality Change
C.190 Create ad group Optional: ability to create multiple ad groups
C.525 Add first (root) product partition This is a required step for creating a shopping campaign and it is done automatically. It is not separately invoked by the merchant. A new campaign should have a root partition otherwise it would not serve.
M.10 Edit campaign settings Only settings required at creation time would be required at change time (e.g. NetworkSettings would not be required to edit, since C.50 is no longer a requirement).
R.10 Customer Optional if only implementing one campaign.

The following features are no longer required. Developers may continue to use these features (unless already sunset), but they are no longer required in order to maintain compliance with the Terms & Conditions of using the Google Ads API. All these features, unless already sunset, are considered optional.

Item Number Functionality
C.14 Set mobile platform bid adjustment
C.15 Set tablet and desktop platform bid adjustments
C.21 Enable distance targeting
C.25 Set geo bid adjustment
C.50 Opt in/out of networks
C.90 Set bidding option: Manual CPC
C.95 Set bidding option: Enhanced CPC
C.101 Set bidding option: Maximize clicks (Portfolio)
C.140 Set delivery method
C.191 Set ad group max CPC bid
C.192 Set ad group max CPA
C.193 Set ad group target ROAS
C.320 Account-level tracking template
C.321 Campaign-level tracking template
C.325 Campaign-level custom parameters
C.326 Ad group-level custom parameters
C.328 Account-level final URL suffix
C.329 Campaign-level final URL suffix
C.700 Create ad group/campaign criterion that targets/excludes user list
C.710 Set userlist targeting bid adjustment for search network campaigns and ad groups
M.15 Edit mobile, tablet, and desktop platform bid adjustments
M.20 Edit ad group settings (all ad group-related required settings in Creation Functionality)
M.25 Edit geo bid adjustment
M.101 Edit bidding option: Maximize clicks (Standard)
M.120 Pause / enable / remove ad group
M.180 Edit product partition max CPC*
M.320 Manage all tracking templates in creation functionality
M.325 Manage all custom parameters in creation functionality
M.328 Manage all final URL suffixes in creation functionality
M.700 Edit ad group/campaign criterion that targets/excludes user list
M.710 Edit userlist targeting bid adjustment for search network campaigns and ad groups
R.30 Ad Group
R.80 Geographic View
R.150 Campaign Audience View
Ad Group Audience View

For more information
If you have questions specific to RMF, please contact the Google Ads API Compliance team at https://services.google.com/fb/forms/apicontact/.

If you have any questions or need additional help with the API, contact us via the forum.
, Google Ads API Team

Announcing v10 of the Google Ads API

Today we’re announcing the v10 release of the Google Ads API. To use some of the v10 features, you’ll need to upgrade your client libraries and client code. The updated client libraries and code examples will be published next week.

Note: Developers must migrate from the legacy AdWords API to Google Ads API by April 27, 2022. Here are the highlights of v10:
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

Sunset of the Ad Manager API v202102

On Tuesday, March 1, 2022, in accordance with the deprecation schedule, v202102 of the Ad Manager API will sunset. At that time, any requests made to this version will return errors.

If you’re still using v202102, now is the time to upgrade to a newer release and take advantage of additional functionality. For example, in v202105 and newer versions we added support for pushing creative previews to linked devices.

When you’re ready to upgrade, check the full release notes to identify any breaking changes. Here are a few examples of changes that may impact your applications:

As always, don't hesitate to reach out to us on the developer forum with any questions.

 - Donovan McMurray, Ad Manager API Team

February 2022 update to Display & Video 360 API v1

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

In addition to these new features, this update also doubles existing default API request limits for the Display & Video 360 API. The updated quota values can be found on our usage limits documentation.

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. We have also added a new Use Audiences guide featuring a page on uploading Customer Match audience data using the Display & Video 360 API.

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

Introducing the new Merchant Center Status Dashboard

At Google, we strive to provide the highest level of service possible to our users. Still, from time to time, unexpected service disruptions do occur. When your team experiences an outage or other technical challenge, one of the first evaluations they need to make is whether the issue is with a third-party service provider or in-house. As part of our commitment to transparency and speed when communicating the status of our products, and incidents when they happen to occur, we’re pleased to roll out the Merchant Center Status Dashboard.

Check the status of a service
A look at the Merchant Center Status Dashboard

If a major incident is identified, we will generally post an outage notice on the Dashboard and provide updates when the issue is resolved. If the dot is green, it means there are no issues. The Merchant Center Status Dashboard provides status information on the Content API for Shopping, Merchant Center, and Feeds.

You can check the dashboard to view the current status of any of those services. All incidents are first verified by our support engineers, so there may be a slight delay from the time they actually occurred. More information can be found on the Merchant Center Help Center.

Subscribe to the Status Dashboard RSS or JSON feeds
To get the fastest outage alerts, we recommend subscribing to the Status Dashboard RSS feed:
  1. Go to the Status Dashboard.
  2. At the bottom, click RSS Feed and copy the feed URL.
  3. In your RSS reader, paste the URL to add the Status Dashboard feed.
  4. If you want programmatic access to the Status Dashboard, for example to integrate it into your monitoring system, at the bottom, click JSON History.
Learn more
More information about the Status dashboard can be found on the Merchant Center Help Center.

To investigate the most common errors regarding the Content API for Shopping, check this page on our Developers site. For other errors or for general Content API support, visit the forum.
Ian Ballantyne, Content API for Shopping Team

Smart Shopping and Local Campaigns upgrading to Performance Max

Starting July 2022, existing and future Smart Shopping campaigns (SSC) will begin automatic upgrades to Performance Max campaigns. Local campaigns (LC) will begin automatic upgrades starting August 2022. If you manage and/or report on SSC and/or LC, you should implement Performance Max campaign features as early as possible in order to avoid loss of functionality. Closer to July, we will provide more details and precise timing.

We recommend you begin to build integrations now to ensure adequate preparation for migration.

New retail and local campaigns

Performance Max has been available in the Google Ads API since v9. We recommend you use Performance Max today for any new campaigns with online, offline or omnichannel sales goals.

SSC can be created without conversion tracking. While Performance Max campaigns, including retail, do not require conversion tracking, it is highly recommended.

Ways to upgrade

Here are the ways you will be able to upgrade existing campaigns to Performance Max:
  • [Recommended] Self-upgrade through API recommendations. In an upcoming Google Ads API release later this year, a new recommendation type will be available for per-campaign or bulk upgrades. You can use this to control the sequence of campaign upgrades or apply all recommendations at one time. There will be equivalent upgrade options available in the Google Ads UI. Self- and auto-upgraded campaigns will carry forward some learnings from the legacy campaign to help ensure continuity.
  • Auto-upgrade. Starting July 2022, SSC will be auto-upgraded to Performance Max on a rolling basis. Starting August 2022, LC will be auto-upgraded on a rolling basis.
  • Create a new Performance Max campaign through the API. This would involve creating a new Performance Max campaign with the same attributes and properties as an existing SSC or LC. Should you choose to create a new Performance Max campaign, the new campaign may not utilize the learnings of the existing SSC or LC to the same extent.

Upgrade impact on existing campaigns

An upgraded campaign, whether by self-upgrade or auto-upgrade, will:
  • Preserve budgets, assets, and settings of the existing SSC and LC
  • Mark the legacy campaign as REMOVED status (metrics will continue to be available in the legacy campaign for historical purposes)
  • Contain a mapping from the previous campaign ID to the new campaign ID
Upgraded campaigns will function like your previous campaigns and use existing assets to run on additional inventory that drives your conversion goals. We recommend adding additional assets to get the most value out of Performance Max.

Timeline


Date Event
Now Start implementing Performance Max in your application. When possible, start new campaigns with Performance Max instead of SSC or LC.
April 27, 2022 Sunset of AdWords API
April 2022 Self-upgrade period begins in the UI
April / May 2022 Self-upgrade period begins with the API's new recommendation type
July 2022 Start of SSC auto-upgrade
August 2022 Start of LC auto-upgrade
September 30, 2022 Completion of most SSC and LC auto-upgrades


Guidance for AdWords API developers

The AdWords API will sunset on April 27, 2022. Developers using SSC via the AdWords API should migrate to the Google Ads API using SSC as early as possible. The self-migration by the Google Ads API will only be available after the sunset of the AdWords API.

Additional information



For additional information, see the Google blog post about this upgrade.
If you have any questions or need additional help, contact us via the forum.
, Google Ads API Team