Tag Archives: google_ads_api

Expanded Text Ads (ETA) Creation and Editing will Cease on June 30, 2022

As previously announced, starting June 30, 2022:
  • You will no longer be able to create or edit Expanded Text Ads
  • If you attempt to create an ETA you will receive the error CANNOT_CREATE_DEPRECATED_ADS
  • If you attempt to modify an ETA you will receive the error CANNOT_MODIFY_AD
  • Expanded text ads will continue to serve, and you will still see reports on their performance going forward
  • You will be able to pause and resume your expanded text ads, or remove them if needed
We encourage you to transition to Responsive Search Ads (RSA).

If you have any questions, please contact us on the forum.

Changes to how Smart Bidding strategies are organized for Search campaigns

We previously announced that standard (non-portfolio) TargetCpa and TargetRoas bidding strategies are being replaced by MaximizeConversions (with target_cpa) and MaximizeConversionValue (with target_roas) for Search campaigns (those with advertising_channel_type = SEARCH).

Starting in July 2022, all remaining Search campaigns that use standard TargetCpa and TargetRoas bidding strategies will be converted to MaximizeConversions and MaximizeConversionValue strategies, with the same target_cpa and target_roas settings applied, respectively. The migration of portfolio strategies is planned later in 2023.

With this change there will be no impact to bidding behavior. Using MaximizeConversions with a target_cpa setting will have the same bidding behavior as TargetCpa. Likewise, using MaximizeConversionValue with a target_roas setting will have the same bidding behavior as TargetRoas.

Example

The following sample Campaign object illustrates what a migrated Search campaign’s bidding strategy settings would look like before and after the transition.

Existing campaign using standard TargetCpa

Previously using TargetCpa Now uses MaximizeConversions
{
bidding_strategy_type: TARGET_CPA
target_cpa: {
target_cpa_micros: 1000000
}
...
}
{
bidding_strategy_type: MAXIMIZE_CONVERSIONS
maximize_conversions: {
target_cpa: 1000000
}
...
}



Existing campaign using standard TargetRoas

Previously using TargetRoas Now uses MaximizeConversionValue
{
bidding_strategy_type: TARGET_ROAS
target_roas: {
target_roas: 2.0
}
...
}
{
bidding_strategy_type: MAXIMIZE_CONVERSION_VALUE
maximize_conversion_value: {
target_roas: 2.0
}
...
}


What to do

The Google Ads API already prohibits creating or updating standard (non-portfolio) TargetCpa or TargetRoas bidding strategies for Search campaigns. In July, any code that reads or manages remaining strategies of those types should account for the settings migrating to MaximizeConversions and MaximizeConversionValue.

If you have any questions or need additional help, contact us via the forum or at [email protected].

Change in the maximum number of mutate operations per request for BatchJobService.AddBatchJobOperations

On June 30, 2022, we’ll limit the number of mutate operations that can be sent to BatchJobService.AddBatchJobOperations to 5,000 mutate operations per request. After this change rolls out, any AddBatchJobOperations requests that contain more than 5,000 mutate operations will result in a SizeLimitError.REQUEST_SIZE_LIMIT_EXCEEDED error.

Note that this will not change the total number of operations you are allowed to add to a BatchJob. It only changes the number of operations you can add to a BatchJob in a single AddBatchJobOperations request.

What do you need to do?
  • Ensure that your code doesn’t send more than 5,000 mutate operations per AddBatchJobOperations request to the Google Ads API.
  • In rare cases, you may still encounter the SizeLimitError.REQUEST_SIZE_LIMIT_EXCEEDED error due to the total size of the request payload, even when you send a request with fewer than 5,000 mutate operations. Therefore, your code should retry the request with half the number of mutate operations until it succeeds. For instance, if 5,000 mutate operations fail, try 2,500 mutate operations. If 2,500 mutate operations fail, try 1,250 mutate operations, and so on.
If you have any questions or need additional help, contact us through the forum.

Changes to CampaignSharedSet Entities

Starting June 23, 2022, attempting to create a CampaignSharedSet with a shared_set that has a status of REMOVED will cause a MutateError.RESOURCE_NOT_FOUND error in the Google Ads API.

There will also be a one-time change to automatically update CampaignSharedSet entities to a status of REMOVED if they contain a shared_set with a status of REMOVED. Because the shared_set already has a REMOVED status, this won’t impact any active campaigns since we’re only changing CampaignSharedSet entities that don’t currently serve.

Where can I get support?

If you have questions, please reach out to us on the forum or at [email protected].

Google Ads Scripts, AdWords API and Google Ads API reporting issues on April 25 and 26, 2022

Between April 25th 2:32 PM PT and April 26th 12:24 PM PT, there was an issue which may have impacted some read report requests across Google Ads scripts, the AdWords API, and the Google Ads API. If you were using these products to request reporting data for your accounts, then a small percentage of report downloads may have been missing rows or may have had incorrect data in a given row. This issue has been resolved. As a precaution, we recommend running again any reports that you have executed during this period as the missing data has been restored.

If you have any questions, please contact us via the Google Ads API forum or the Google Ads scripts forum.

Announcing v10.1 of the Google Ads API

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

Here are the highlights of v10.1:

Where can I learn more?

The following resources can help you get started:

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

Reminder: Requests to the AdWords API will start failing April 27, 2022

As previously announced, if you are currently using the AdWords API, you need to upgrade to the Google Ads API as soon as possible. Starting on Wednesday, April 27, 2022 requests to the AdWords API will fail at a rate of 25% until May 31, 2022, increasing to 100% thereafter.

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].

The AdWords API sunsets on April 27, 2022

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: 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].

Google Ads API v7 and v8 sunset reminder

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: 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 [email protected].

Smart Shopping campaign upgrade to Performance Max – update

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.