Tag Archives: google_ads_api

Google Ads API v12 sunset reminder

Google Ads API v12 will sunset on September 27, 2023. After this date, all v12 API requests will begin to fail. Please migrate to a newer version before September 27, 2023 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.v12.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 through [email protected].
 - Thanet Knack Praneenararat, Google Ads API Team

Announcing v14_1 of the Google Ads API

Today, we’re announcing the v14_1 release of the Google Ads API. To use some of the v14_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: Where can I learn more?
The following resources can help you get started: If you have any questions or need help, contact us through the forum.
 - Thanet Knack Praneenararat, on behalf of the Google Ads API Team

Change to updates of Google Ads custom audience types

Starting September 27, 2023 you will see a change if you use custom audiences. You will no longer be able to update a custom audience type once you create the custom audience. For example, if you set the type to AUTO or INTEREST, then you cannot update it to the type SEARCH in the Google Ads API. This change ensures that your campaign continues to serve by making sure that your custom audience remains eligible.

What do I need to change?

Modify your code so it avoids attempting to update the type of an existing CustomAudience. If your code attempts to update the type field after September 27, 2023 then the API will return a CustomAudienceError.INVALID_TYPE_CHANGE error.

Where can I get support?

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

Nadine Wang, Google Ads API Team

Image and Location Assets in New Accounts

What’s changing?

On July 6, 2023 we announced the auto-migration of image and location extensions to assets. Once the auto-migration starts on August 2, 2023, new accounts will only be able to create image and location assets and not extensions. New accounts will be treated as accounts that have been migrated.

How do I verify my account?

Use the following fields from v13 or greater in the Customer resource to track the status of your account:

  • bool image_asset_auto_migration_done
  • string image_asset_auto_migration_done_date_time
  • bool location_asset_auto_migration_done
  • string location_asset_auto_migration_done_date_time

What if I try to create an extension on a new or migrated account?

If your account has been migrated or is new and you attempt to create an extension the mutate request will be rejected and you will receive the error:

     LEGACY_EXTENSION_TYPE_READ_ONLY

If you have any questions, please reach out to us on the forum.

Bob Hancock, Google Ads API Team

Performance Max success story driven by Google Ads API with Kueez

Today, we’re proud to share Kueez’s success story of using the Google Ads API with Performance Max to grow ROAS for partners by 20%!

Here are the highlights:
  • Kueez leverages Google Ads to drive platform ad views from high-quality and engaged traffic across their portfolio of publisher partners, and owned and operated websites.
  • Using the power of Google Ads API, Kueez implemented Performance Max campaigns to broaden their reach, and attract additional audiences that exhibit similar or better conversion rates than they had before using Performance Max.
  • Within 45 days of activating Performance Max campaigns, Kueez achieved an increase of over 50% engaged visits at a similar CPA, and drove +20% ROAS.
Where can I learn more?
We're constantly looking to improve the Google Ads API developer experience. If you have feedback on using Performance Max in the Google Ads API, submit it through this form.

If you have any questions or need additional help, contact us via the forum.
David Stevens, Google Ads API Product Manager

Image and Location Auto-migration August 2023

What’s changing?

Beginning on August 2, 2023, we will start auto-migrating image and location extensions to assets. The auto-migration will end on September 30, 2023.

Once the image and location extensions have been migrated to assets, you won’t be able to mutate the image and location extensions. The image and location assets will be the entities that are served. Metrics for the extensions will be available until sometime in 2024.

Why is this changing?

Extensions are migrating to assets.

What do I need to do?

Upgrade to version v13 or greater of the Google Ads API since v12 will sunset at the end of September 2023. We recommend that you upgrade to v14.

The auto-migration will not keep a mapping of feed IDs to asset IDs. If you would like to keep a record of feed ID to asset ID mappings, create a new asset image or location based on your feed, and save that ID mapping locally.

Can I opt-out of the auto-migration?

No. We offered an opt-out for the first batch of auto-migration, but you can’t opt out of this auto-migration.

How will the migrations occur?

The migrations occur at an account level. During the migration of an account, which will take several minutes, you won’t be able to execute any image or location mutations of either extensions or assets. When the migration is complete, you will have access to the assets.

The image and location migrations are not synchronized. It is likely they will occur at different times for each account.

How do I know when an account has been migrated?

Use the following fields from v13 or greater in the Customer resource to track the status of the migration:

  • bool image_asset_auto_migration_done
  • string image_asset_auto_migration_done_date_time
  • bool location_asset_auto_migration_done
  • string location_asset_auto_migration_done_date_time

If you are using v12, you can instead consult the UI and you will see an alert once your account has been migrated.

What happens after the auto-migration?

Accounts that have been migrated will reject mutate calls for feed-based entities.

If you have any questions, please reach out to us on the forum.

Bob Hancock, Google Ads API Team

Upcoming changes in keyword validation

Starting on July 5, 2023 we will gradually release a backend improvement on Google Ads keyword policy validation.

You might see an increase in keyword policy violation failures when you send Google Ads API requests that create keyword criteria. The Google Ads API will catch more keywords that don’t adhere to our keyword policy as soon as you send the API request, rather than validating them offline after the keywords have been submitted.

Note that not all keywords created through successful API calls will be accepted. Keywords still undergo offline review.

Due to the new realtime check, you might need to account for new policy violation terms in the PolicyViolationDetails field of the responses you receive from the Google Ads API. Use this field to apply for keyword policy exemption; for further details on how to do so, please refer to the guide on keyword policy exemptions.

If you have any questions or concerns, please don't hesitate to contact us via the forum.

 - Mattia Tommasone, Google Ads API Team

Upcoming changes in keyword validation

Starting on July 5, 2023 we will gradually release a backend improvement on Google Ads keyword policy validation.

You might see an increase in keyword policy violation failures when you send Google Ads API requests that create keyword criteria. The Google Ads API will catch more keywords that don’t adhere to our keyword policy as soon as you send the API request, rather than validating them offline after the keywords have been submitted.

Note that not all keywords created through successful API calls will be accepted. Keywords still undergo offline review.

Due to the new realtime check, you might need to account for new policy violation terms in the PolicyViolationDetails field of the responses you receive from the Google Ads API. Use this field to apply for keyword policy exemption; for further details on how to do so, please refer to the guide on keyword policy exemptions.

If you have any questions or concerns, please don't hesitate to contact us via the forum.

 - Mattia Tommasone, Google Ads API Team