Tag Archives: google_ads_api

Search Terms Report Improvements

With the updates listed below, we're improving the search term reports returned from both the Google Ads API and the AdWords API across all active versions.

Starting Sep 9, 2021, you'll be able to see more queries that meet our privacy standards in the search terms report for Search and Dynamic Search Ads campaigns. This new data will return for all searches on or after February 1st, 2021 when using the following reports and resources:

This update can help you identify more relevant keyword themes, making it easier to optimize your ads, landing pages, and more. Metric totals from search terms reports will now be consistent with other reports, such as campaign, ad group, and ad reports in Google Ads.

As part of our ongoing commitment to privacy, we’re working to make our privacy thresholds consistent across Google. Over the next few months, you’ll see more changes across our other tools–including how we handle historical data. In Google Ads, this means that historical query data in your account that was collected prior to September 1st, 2020 will be available until February 1st, 2022. At that point, any historical queries that no longer meet our current privacy thresholds will be removed from your search terms report.

If you have any questions about this change or any other API feature, please contact us via the forum.


Announcing The Google Ads API Migration Workshop

Today, we’re announcing The Google Ads API Migration Workshop, which will be presented live in three regions, to provide you with knowledge, resources, and support to migrate from the AdWords API to the Google Ads API.
Session DatesGet to know the team supporting your migration during this three-day virtual workshop as we:
  • Teach you about the new API
  • Walk through interactive demonstrations
  • Help you create a migration plan
  • Discuss best practices for migrating your application

Whether you’re new to the Google Ads API or want to level up your skill set, we'll have a variety of sessions to help you achieve your goals. We’ll be delivering several talks to discuss what’s new in the Google Ads API and explain key concepts. Tune into our interactive sessions as we demonstrate how to migrate components of your application and leverage the suite of developer tools supporting the Google Ads API.


Throughout the workshop, you’ll have the opportunity to interact with our team via live Q&A and breakout sessions. We’ll also host a panel featuring the Tech Leads of the Google Ads API Engineering and Developer Relations teams.


Follow the event link to register for the event and view the full agenda. We look forward to seeing you!

Feed-based Extensions Migration Reminder and Opt Out Instructions

As previously announced, all ad extensions are migrating to the new Asset-based extension paradigm. You must update extensions support in your implementation and migrate existing Feed-based extensions to Asset-based extensions. See the migration schedule for all the important migration and sunset dates.

The first automatic migration will start on October 20, 2021 and will take several weeks to complete. You have a choice to migrate your own extensions, allow the automatic migration to proceed, or to opt client accounts out of it. During the migration, Feed-based Callout, Promotion, Sitelink, and Structured Snippet extensions within client accounts will be copied into new Asset-based extensions. The new Asset-based extensions will then serve instead of the Feed-based extensions.


What will be the impact of the automatic migration?

After an account has been migrated, there will be a new Asset instance for each Feed-based Callout, Promotion, Sitelink, and Structured Snippet extension. The new Assets will be linked to the same ad groups, campaigns, and customers as the Feed-based extensions from which they were copied. The new Assets will have new IDs, and there will be no connection between Assets created during the automatic migration and the original Feeds, including historic metrics. All subsequent extension-related metrics will only be accessible from the asset_field_type_view report. Additionally, you will no longer be able to issue CREATE or MUTATE requests that affect Callout, Promotion, Sitelink or Structured Snippet extensions in the account through the following services:

Service API Reference
ExtensionFeedItemService Google Ads API
AdGroupExtensionSettingService AdWords API Google Ads API
CampaignExtensionSettingService AdWords API Google Ads API
CustomerExtensionSettingService AdWords API Google Ads API
FeedService AdWords API AdWords API
FeedItemService AdWords API Google Ads API
FeedMappingService AdWords API Google Ads API
AdGroupFeedService AdWords API Google Ads API
CampaignFeedService AdWords API Google Ads API
CustomerFeedService AdWords API Google Ads API
GoogleAdsService Google Ads API
BatchJobService AdWords API Google Ads API


If you choose to allow the automatic migration to proceed, you will know that an account has been migrated when any MUTATE or CREATE request to the above listed services affecting Callout, Promotion, Sitelink, or Structured Snippet extensions returns an error.


What will be the impact of opting out?

You can opt out individual customer accounts from the October automatic migration. Opting out will only defer the automatic migration until the second automatic migration begins on February 15, 2022. If you choose to opt out, no resources will be created or modified in opted out accounts during the October automatic migration, and only the opted out accounts will be able to continue to issue CREATE and MUTATE requests after the October automatic migration.

You cannot opt out of the February 15, 2022 automatic migration. All remaining Feed-based extensions will be automatically migrated starting February 15, 2022 as described in the migration schedule. After this second automatic migration, all CREATE and MUTATE requests affecting Feed-based extensions will return errors.

What do I need to do?

We strongly recommend that you migrate your extensions yourself if feasible. Please follow our extension migration documentation for guidance on migrating your own extensions. Be sure to remove the Feed-based extension once you have successfully copied an extension to an Asset to avoid duplication during the automatic migration.

If you choose to allow the automatic migration to proceed, you need to only update your implementations to detect when an account has been migrated and to thereafter switch over to managing Assets instead of Feeds.


If you choose to opt out, the automatic migration will make no changes to the opted out accounts. Your existing API implementations will continue to work until the second automatic migration begins on February 15, 2022. To opt out, you must complete this form with the following:
  • A contact email at which you can be reached should any issues arise during the opt out process.
  • The developer token that you use to manage the accounts.
  • Acknowledgements of the effects of opting out.
  • An uploaded text file containing the customer IDs that you wish to opt out, one per line. If you need to generate a list of customer IDs, we recommend utilizing the GetAccountHierarchy example in each client library’s AccountManagement directory. This example will return the resource names of all accounts reachable from a given manager account.
The form will open for submissions on August 30, 2021. Note that the developer token must have been used to issue requests on the customer account after July 16, 2021. The form will close on October 13, 2021.


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

Announcing v8_1 of the Google Ads API

Today, we’re announcing the v8_1 release of the Google Ads API. To use some of the v8_1 features, you 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’s what we added: Where can I learn more?
The following resources can get you started: If you have any questions or need additional help, contact us through the forum.

Google Ads API v6 sunset reminder

Google Ads API v6 will sunset on September 8, 2021. After this date, all v6 API requests will begin to fail. Please migrate to a newer version prior to September 8, 2021 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].

Updates to how Google Ads API Smart Bidding strategies are organized

We previously announced changes to how Smart Bidding strategies are organized to help advertisers choose the right one. Google Ads API developers can now create new or update existing Search campaigns using the following bidding strategies: What’s changing
Starting on September 30, 2021, Google Ads API developers won’t be able to create new TargetCpa or TargetRoas standard bidding strategies in Search campaigns. This change will prevent creating new Search campaigns that use these strategies, as well as prevent updating existing Search campaigns to use these strategies. Instead, use the new optional target CPA field with MaximizeConversions, and the new target ROAS field with MaximizeConversionValue. This change will not affect portfolio (shared) bidding strategies.

AdWords API
AdWords API users can continue to use the old style TargetRoasBiddingScheme and TargetCpaBiddingScheme bidding strategies, since v201809 of that API does not contain the MaximizeConversions.target_cpa field required to migrate to the new style bidding strategies. Their usage will sunset when the AdWords API itself sunsets in April, 2022. Switch to using the new bidding strategies when you migrate your code to the Google Ads API.

What to do
Update any code that creates or updates standard (non-portfolio) TargetCpa or TargetRoas Search campaigns. Use MaximizeConversions or MaximizeConversionValue strategies with their target_cpa (mutable starting in v8) or target_roas fields instead.

There will be no impact to bidding behavior due to this update. Using MaximizeConversions with target_cpa will have the same bidding behavior as TargetCpa. Likewise, using MaximizeConversionValue with target_roas will have the same bidding behavior as TargetRoas.

Refer to our product level announcement for more details on this change.

All existing campaigns using TargetCpa or TargetRoas will continue to run as usual, and you will still be able to manage their bidding strategies and budgets as before. We’ll give advance notice before automatically migrating these old bidding strategies to the new format in 2022.

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

Google Ads API 2022 release and sunset schedule

We’re announcing our tentative 2022 release and sunset schedule for upcoming versions of the Google Ads API to bring greater clarity to your planning cycle. Please keep in mind that these dates are only estimates and may be adjusted going forward. Additionally, releases may be added, removed or switched between major and minor. Check back with our release notes and deprecation schedule for updates.

Note: The AdWords API will sunset in April 2022. Migrate all requests to the Google Ads API by then to continue managing your Google Ads accounts.
Version Planned Release
Type*
Projected launch* Projected sunset*
v7 Major April 28, 2021 (launched) January/February 2022
v8 Major June 9, 2021 (launched) March/April 2022
v8_1 Minor August 2021 March/April 2022
v9 Major October 2021 June/July 2022
v10 Major February/March 2022 October/November 2022
v10_1 Minor April/May 2022 October/November 2022
v11 Major June/July 2022 March/April 2023
v11_1 Minor August/September 2022 March/April 2023
v12 Major October/November 2022 June/July 2023
*Estimated and subject to change
Where can I learn more?
The following resources can help you with your development planning: If you have any questions or need additional help, contact us via the forum.

Broad match modifier upcoming changes in Google Ads

On February 4, 2021, we announced changes to phrase match and broad match modifier (BMM). As advised in that post, as of today all Google Ads languages have now been updated to use the new phrase match definition. Also as of today, all legacy BMM keywords will continue to serve but will now behave as phrase match keywords. Creation of new BMMs using the legacy BMM notation (+keyword) and modifications to existing BMM keyword text will no longer be permitted as of August 2, 2021 (AdWords API, Google Ads API, Google Ads scripts).

Updates of other targeting criteria fields (such as status, bid, url, labels) will still be permitted.

Partners are encouraged to follow the guidance in this article. As detailed in the article, if you choose to convert BMM keywords to phrase match, performance statistics will not carry over to the new instances. Smart bidding users are encouraged to use the broad match type.

Note: The changes to phrase match and BMM will not impact exact match, broad match, or negative keyword match types. Learn more about keyword matching options.

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

Asset-based Extensions: Updated Availability and new ValueTrack Parameter

As previously announced, all ad extensions are migrating to the new Asset-based extension paradigm. You must update extensions support in your implementation and migrate existing Feed-based extensions to Asset-based extensions. See the migration schedule for important sunset dates.

What has changed

The following Asset-based extension types are now available to all accounts:
Though originally scheduled for release later this year, Asset-based Image extensions will not be available in the Google Ads API until 2022. When available, we will publish an updated sunset timeline for Feed-based Image extensions to this blog and in our extension migration documentation.

Lastly, the new {extensionid} ValueTrack parameter will be available beginning June 24, 2021. You can use this parameter to track clicks on your Asset-based extensions. The {extensionid} parameter for Asset-based extensions mirrors the behavior of the existing {feeditemid} parameter for Feed-based extensions.

What you need to do

Migrate Callout, Promotion, Sitelink, and Structured Snippet extensions in your accounts to Asset-based extensions using the Google Ads API. We encourage you to do so as soon as possible so as to continue to be able to modify your extensions; Callout, Promotion, Sitelink, and Structured Snippet Feed-based extensions will automatically migrate to Asset-based extensions on October 20, 2021. You will soon be able to opt individual Google Ads client accounts out of this auto migration; the opt out process will be announced on this blog when available. Please see our extension migration guide for the most up-to-date and relevant information. Note that Asset-based extensions are not supported in the AdWords API.

You can now use the {extensionid} ValueTrack parameter to track clicks on any Asset-based extensions that you have created. The {feeditemid} parameter does not apply to any clicks on Asset-based extensions, and {extensionid} does not apply to clicks on Feed-based extensions. To continue attributing clicks correctly, you should update any URLs that currently use the {feeditemid} ValueTrack parameter to also include the new {extensionid} ValueTrack parameter. You should therefore set both {feeditemid} and {extensionid} in the same URL, though only one will be populated depending on the source of the click.


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

Filtering Non-video Resources from Video Reports in the Google Ads API

Beginning on August 4, 2021, all video-related performance reports will begin filtering out campaigns, ad groups, and ad group ads that are not part of video campaigns (advertising_channel_type = VIDEO). This change will cause performance metrics retrieved from the video resource to change across all supported Google Ads API versions.

If you would like to generate reports that combine metrics from video and non-video resources, you should use the respective resource-specific performance report, for instance: campaign, ad_group, or ad_group_ad.

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