Google Ads Developer Blog

Changes to location targeting in Google Ads Search, Shopping, Display, and Performance Max campaigns

2023-02-27T11:36:00.000-08:00

Starting on April 14, 2023, there will be changes made to the location targeting settings for Search, Shopping, Display, and Performance Max campaigns in the Google Ads API. We are making this change to simplify the location targeting portfolio and improve advertiser performance. All versions will throw errors if you try to set the location target settings to one of the values shown below.

Campaign.geo_target_type_setting fields
`positive_geo_target_type` can no longer be set to `SEARCH_INTEREST` for Search, Shopping, and Display campaigns. The default value is `PRESENCE_OR_INTEREST`.
`negative_geo_target_type` can no longer be set to `PRESENCE_OR_INTEREST` for Performance Max, Search, Shopping, and Display campaigns. The default value is `PRESENCE`.

The error returned if these values are used is SettingError.SETTING_VALUE_NOT_COMPATIBLE_WITH_CAMPAIGN.

On April 24, 2023, we will start performing any necessary auto-migration of fields to the new default values until no more invalid combinations exist. The auto-migration will occur on a per-campaign basis. You can confirm that the migration is complete for a Google Ads account by checking that these two queries return zero rows.

SELECT campaign.id, campaign.geo_target_type_setting.positive_geo_target_type, campaign.advertising_channel_type FROM campaign WHERE campaign.advertising_channel_type IN ('DISPLAY', 'SEARCH', 'SHOPPING') AND campaign.geo_target_type_setting.positive_geo_target_type = 'SEARCH_INTEREST' LIMIT 1

SELECT campaign.id, campaign.advertising_channel_type, campaign.geo_target_type_setting.negative_geo_target_type FROM campaign WHERE campaign.geo_target_type_setting.negative_geo_target_type = 'PRESENCE_OR_INTEREST' AND campaign.advertising_channel_type IN ('DISPLAY', 'PERFORMANCE_MAX', 'SEARCH', 'SHOPPING') LIMIT 1

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

RSA Combination Report Policy Update for Google Ads

2022-11-08T10:03:00.000-08:00

What is changing?
Beginning on January 15, 2023, advertisers will no longer be able to retrieve the Ad Group Ad Combination Report (ad_group_ad_asset_combination_view) for Responsive Search Ads for the entire time period that their ad was serving. Instead, the Ad Group Ad Combination Report will return data for a 12 month period ending with the current month on a rolling basis. At any given time, only the data for the twelve month window will be available, and any older combination data will be deleted.

Why is this changing?
To optimize the Ad Group Ad Combination Report for upcoming features.

What do I need to do?
If you want to retain combination data from January 2022 or before, we recommend that you download it before January 15, 2023.

After January 15, 2023, we recommend downloading the combinations report on an ongoing basis if you'd like to retain historical combinations.

If you have any questions, please reach out to us on the forum.
Bob Hancock, Google Ads API Team

AdWords API has Officially Sunset

2022-05-27T10:43:00.001-07:00

As previously announced, the error rate for requests to the AdWords API will start increasing toward 100% beginning on May 31, 2022. If you are currently using the AdWords API, you need to upgrade to the Google Ads API now or your applications will experience an increased rate of errors per the schedule below:

Starting Date	AdWords API Error Rate
June 1, 2022	50% errors
July 1, 2022	60% errors
July 8, 2022	70% errors
July 15, 2022	80% errors
July 22, 2022	90% errors
July 31, 2022	100% errors

Starting July 31, 2022 all requests to the AdWords API will fail.

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 googleadsapi-support@google.com.
- Cory Liseno, Google Ads API Team

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

2022-05-03T09:03:00.000-07:00

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.

- David Stevens, Google Ads API Product Manager

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

2022-04-26T15:02:00.000-07:00

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 googleadsapi-support@google.com.

- David Stevens, Google Ads API Product Manager

The AdWords API sunsets on April 27, 2022

2022-03-30T07:00:00.000-07:00

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 googleadsapi-support@google.com.
Nadine Wang, Google Ads API Team

Important changes to placement reporting for App Campaigns

2022-02-28T10:05:00.000-08:00

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 googleadsapi-support@google.com. 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

Google Ads API v10 RMF Update

2022-02-09T14:31:00.000-08:00

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.
David Wihl, Google Ads API Team

Announcing v10 of the Google Ads API

2022-02-09T12:23:00.001-08:00

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:

Smart Campaigns are now in general availability
Added support for Audience, which you can add as an AdGroupCriterion to Discovery and Video Action Campaigns
- The Audience resource will be used for targeting when use_audience_grouped is set to true for an audience_setting of an ad group
Performance Max Campaigns now support asset group signals consisting of Audience criteria to tell who's most likely to convert for the campaigns
Added a new ExperimentService with a set of new resources. This replaces the deprecated campaign experiments.
Added support for Local Services Ads campaigns as open beta with the following options:
- You can retrieve campaigns and their metrics using Search and SearchStream
- You can update the campaign status and campaign budget amount using mutate. Note other mutate operations aren’t supported.
Added a new meta parameter that you can use to make GoogleAdsService return only resource name fields that you explicitly request in the SELECT clause of your query
Added the following for Hotel campaigns:
- hotel_reconciliation.campaign for Hotel campaigns that use commission as the bidding strategy, to show the campaign associated with the commission
- The following metrics:
  - metrics.hotel_commission_rate_micros
  - metrics.hotel_expected_commission_cost
You can now segment SKAdNetwork conversions by user type, ad event type, and source app ID (if available in the postback sent to us by Apple)
ad_group_ad_asset_combination_view now supports responsive search ads

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

Revised Schedule for the Auto-migration of Feeds

2022-01-26T08:44:00.002-08:00

We previously announced schedules for migrating feeds to assets.

If you’re still using legacy feeds, your API calls will start to fail after the auto-migration is complete.

Please migrate to assets as soon as possible.

The following table indicates the current status of each feed sub-type. After the auto-migration is complete, you will no longer be able to mutate or remove your feeds.

Legacy Type	Subtype	Status	Auto Migration Starts
Extensions	Promotion, Callout, Sitelink, Structured Snippet	AUTO MIGRATION IN PROGRESS	10 January 2022
Extensions	App, Call, Hotel Callout, Price	Developers can start migrating on 25 January 2022	8 April 2022
Dynamic Search Ads & Dynamic Remarketing	Page Feed, Education Feed	Developers started migrating on 3 November 2021	27 April 2022
Dynamic Remarketing	Custom, Flight, Hotel, Real Estate, Travel, Job, Local Deals	Developers can start migrating on 27 April 2022	5 October 2022
Extensions	Image	Developers can start migrating in Q3 2022	ETA January 2023
Extensions	Location	Developers can start migrating in Q3 2022	ETA January 2023

What do I need to do?
You need to support the new asset types as soon as possible.

If you would like to keep a record of feed IDs to asset IDs, then you need to migrate these manually and save that ID mapping locally. The auto-migration does not keep a mapping of feed IDs to asset IDs.

See the following migration guides for details:

What happens after the auto-migration?
Accounts that have been migrated will reject mutate calls for feed-based entities. Reporting metrics will be removed for the legacy feed-based entities in 2023. Equivalent reporting data will be available for assets, as described in the preceding migration guides.

Can I opt-out of the auto-migration?
No. We offered an opt-out for the first batch of auto-migration, but this isn’t available for future migrations.

If you have any questions, please reach out to us on the forum.
Bob Hancock, Google Ads API Team

Upcoming changes to Simulations in the Google Ads API and Bid Landscapes in the AdWords API

2021-12-20T10:34:00.000-08:00

We are changing the way ad group simulations with SimulationModificationMethod = DEFAULT are calculated in the Google Ads API and the AdWords API.

What’s changing?

For an ad group with keyword bid overrides, we provide estimated traffic for different values of the ad group’s default bid. Currently, all keywords with bid overrides are excluded from this estimate. This results in a lower-than-expected traffic estimate.

Starting the week of January 17, 2022, we will modify our estimation to include both keywords using the default bid and keywords with bid overrides when calculating ad group simulations. We will further assume that only the ad group default bid would change in the simulation, and all keyword bid overrides will remain the same. This may affect the simulations returned by the GetAdGroupSimulation method of the AdGroupSimulationService service in the Google Ads API and the getAdGroupBidLandscape and queryAdGroupBidLandscape methods of the DataService service in the AdWords API.

What should you do?

If you use this feature, we recommend that you ensure that your code continues to work with the modified results returned by these methods.

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

Reminder: Share your feedback about the Google Ads (AdWords) API. Take the 2021 AdWords API and Google Ads API Annual Survey.

- Anash P. Oommen, Google Ads API Team

Set asset names by February 9, 2022

2021-12-15T13:14:00.000-08:00

Starting in the upcoming Google Ads API v10 release, you’ll have to use unique asset names within your Google Ads account. This affects asset names for image and media bundle asset types. The reason we’re making this change is to make it easier to identify assets with human readable names as your collection of assets grows.

Starting on February 9, 2022 a default asset name will be assigned during creates and updates for all existing Google Ads API and AdWords API versions. If you wish to set the asset name yourself, then update your code to set the asset name before this date.

If you have questions while you’re updating your code, please reach out to us on the forum or at googleadsapi-support@google.com.
Nadine Wang, Google Ads API Team

Warning: deprecation and sunset of Feeds

2021-12-14T06:14:00.001-08:00

Update (Jan 26, 2022): published revised schedule for the Auto-migration of Feeds.

We previously announced that we’re migrating Feeds to Assets. We’ve started auto-migrating accounts. If you’re still using legacy Feeds, your API calls will start to fail. Please migrate to Assets as soon as possible.

The following table shows the current status and key dates for the automatic migration.

Feed Type	Subtype	Status	Auto Migration Date
Extensions	Promotion	AUTO MIGRATION IN PROGRESS	October 20, 2021*
Extensions	Callout Sitelink Structured Snippet	AUTO MIGRATION IN PROGRESS	October 20, 2021*
Extensions	App Call Hotel Callout Price	DEPRECATED	February 15, 2022
Extensions	Image	Not ready to migrate until mid 2022	September 2022
Dynamic Search Ads	Page feed	DEPRECATED	27 April 2022
Dynamic Remarketing	Education	DEPRECATED	27 April 2022
Dynamic Remarketing	Custom Flight Hotel Real estate Travel Location Job	Deprecation planned for April 2022	5 October 2022

* Delayed until January 10 2022.

I thought Image extensions were migrating in February 2022?
That was the original plan, however we have delayed the Image extensions migration until September 2022.

What do I need to do?
You need to support the new Asset types as soon as possible.

To trace migration between Feed IDs and Asset IDs you need to migrate these manually. There is no way to get this relationship through the auto-migration.

See the following migration guides for more detail:

What happens after the automated migration?
Accounts that have been migrated will reject mutate calls for Feed-based entities. Reporting stats will be removed for the legacy Feed-based entities in the near future. Equivalent reporting data will be available for assets, as described in the preceding migration guides.

Can I opt-out of the auto-migration?
No. We offered an opt-out for the first batch of auto-migration, but this isn’t available for future migrations.

If you have any questions, please reach out to us on the forum.
Nick Birine, on behalf of the Google Ads API Team

Google Ads (AdWords) API Annual Developer Survey 2021

2021-12-07T13:10:00.000-08:00

The Annual Google Ads (AdWords) API Developer Survey for 2021 is closing on December 31st. Please take 10-15 minutes to share your feedback with us before the end of the month.

Here is our original blog post for reference.
- Cory Liseno, Google Ads API Team

Updated schedule of Google Ads API 2022 releases and sunsets

2021-11-11T07:33:00.000-08:00

We’re announcing an update to the Google Ads API 2022 release and sunset schedule to help developers migrate from the AdWords API. Google Ads API v7 and v8 are expected to sunset in April/May 2022 in order to align their sunset with that of the AdWords API.

Please keep in mind that these dates are only estimates and may be adjusted going forward. Releases may be added, removed or switched between major and minor. Check our release notes and deprecation schedule for updates.

Note: The AdWords API is scheduled to sunset in April 2022. Migrate all requests to the Google Ads API by then to continue managing your Google Ads accounts.

Updated release schedule:

Version	Planned Release Type*	Projected launch*	Projected sunset*
v7	Major	April 28, 2021 (launched)	April/May 2022
v8	Major	June 9, 2021 (launched)	April/May 2022
v8_1	Minor	August 11, 2021 (launched)	April/May 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.
- David Stevens, Google Ads API Product Manager

Announcing DSA Page Feeds and Dynamic Remarketing Feeds are migrating to Assets

2021-11-08T09:31:00.000-08:00

Today we’re announcing the upcoming migration of dynamic search ads (DSA) page feeds and dynamic remarketing feeds to assets in the Google Ads API. These assets are only available in the Google Ads API.

Asset-based configuration will replace the current feed services in the Google Ads API. All existing DSA and dynamic remarketing feeds are migrating to assets. We recommend that API users manually migrate their existing feeds before the auto-migration date. After the auto-migration date, any existing feeds will be removed and replaced with asset-based equivalents. Since there will be no link between legacy feeds and the auto-migrated assets, it is advised that API users migrate their own feeds if maintaining this link is important to your use case.

Legacy Type	Asset Available	Auto Migration Date
DSA Page Feed Dynamic Remarketing: Education	Google Ads API v9	27 April 2022
Dynamic Remarketing: Custom Flight Hotel Real estate Travel Location Job	Google Ads API v10_1	5 October 2022

What do you need to do?
You need to migrate your DSA page feeds and dynamic remarketing feeds to use the new asset types as soon as possible. You should remove feed-based entities after migrating. During the migration period, legacy feeds and asset-based feeds may coexist and both serve in a campaign. See our DSA and dynamic remarketing migration guides for details. Consider developing and testing your Asset-based implementation using a test account.

After the automatic migration dates, you will no longer be able to get, create, or mutate legacy feeds in the AdWords API or the Google Ads API.

Note that if you only upload and manage feeds via the Google Ads UI, they will be automatically migrated to assets and there is no further action required on your part.

If you have any questions or need additional help, contact us via the forum.
Nick Birine, on behalf of the Google Ads API Team

Google Ads (AdWords) API Annual Developer Survey 2021

2021-11-04T10:38:00.000-07:00

As 2021 comes to a close, we’re looking forward to next year and how we can improve the Google Ads API developer experience. As we've done in past years, we're again asking for your feedback on the Google Ads API (and AdWords API, sunsetting in April 2022).

Last survey, you helped us understand your biggest pain points when using the Google Ads API. You also pointed us toward the features and functionality you like or want most. We've spent time in those areas over the last year, keeping your feedback in mind.

Please take 10-15 minutes to share your feedback about the Google Ads API and the AdWords API on our Annual Google Ads API Developer Survey for 2021.
- Cory Liseno, Google Ads API Team

Reducing RMF to help migration to the Google Ads API

2021-11-04T08:21:00.002-07:00

Effective with the Google Ads API v9, we’re significantly reducing the Required Minimum Functionality (RMF) to use the Google Ads API. This is to help accelerate your migration to the new API prior to the sunset of the AdWords API on April 27, 2022 while decreasing the burden on your engineering team. Requirements for the AdWords API remain unchanged.

This will affect the following tools:

Full-service
Shopping-only, Smart Shopping-only, Hotel-only and App Promotion-only API tools
Special purpose tools that offer campaign creation or management functionality
Reporting-only tools

This will not affect Internal-only tools because they are not subject to RMF.

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

The following features are not changing and are still required:

Item Number	Functionality
C.10	Create campaign
C.96	Set bidding option: Target CPA (Portfolio and Standard)
C.97	Set bidding option: Target ROAS (Portfolio and Standard)
C.98	Set bidding option: Maximize Conversions (Standard)
C.120	Set budget
C.260	Add keyword
C.300	Set keyword match type
M.96	Edit bidding option: Target CPA (Portfolio and Standard)
M.97	Edit bidding option: Target ROAS (Portfolio and Standard)
M.98	Edit bidding option: Maximize Conversions (Standard)
M.110	Pause / enable / remove campaign
M.130	Pause / enable / remove ad
M.140	Pause / enable / remove keyword
R.40	Ad Group Ad
R.50	Keyword View
R.70	Search Term View
R.130	Bidding Strategy

The following features are still required but simplified or reduced in scope:

Item Number	Functionality	Change
C.20	Enable geo targeting	Required. Optional to expose to the user if only one country is relevant for the user base.
C.30	Enable language targeting	Required. Optional to expose to the user if only one language is relevant for the user base.
C.65	Create website / call conversion and generate code snippet	Requires at least one type of conversion tracking.
C.75	Callout extensions	Required account level only.
C.80	Callout extensions	Required account level only.
C.190	Create ad group	Optional: ability to create multiple ad groups.
C.270	Add ad group negative keywords	Change from Ad Group level to Campaign level.
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.
R.20	Campaign	Remove requirements for `segments.ad_network_type` and `segments.device`.
R.100	Dynamic Search Ads Search Term View	Required only if implementing Dynamic Search Ads.

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.

Shopping-only features (indicated by *) are still required for shopping-only tools, but are no longer required for Full-service tools.

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.41	Set Expanded Dynamic Search Ads
C.42	Set campaign DSA settings
C.50	Opt in/out of networks
C.70	Location extensions
C.72	App extensions
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.200	Add expanded text ad
C.290	Set keyword max CPC
C.311	Set keyword final URL
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.500	Create shopping campaign*
C.505	Set merchant identifier*
C.506	Set sales country*
C.510	Set inventory filter*
C.520	Create product ad*
C.525	Add first (root) product partition*
C.530	Local inventory ads*
C.610	Call ads
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.35	Enable ad rotation
M.40	Edit keyword max CPC
M.100	Edit expanded text ad
M.101	Edit bidding option: Maximize clicks (Standard)
M.120	Pause / enable / remove ad group
M.150	Edit inventory filter*
M.160	Subdivide (add product partition)*
M.170	Remove product partition*
M.180	Edit product partition max CPC*
M.190	Exclude product partition (delegate)*
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.110	Shopping Performance View*
R.120	Product Group View*
R.150	Campaign Audience View Ad Group Audience View

* These features are not required for Full-service tools. Shopping-only RMF tools still need to implement these features.

If you have questions specific to RMF, please contact the Google Ads API Compliance team.
If you have any questions or need additional help about the API, contact us via the forum.
David Wihl, Google Ads API Team

Announcing v9 of the Google Ads API

2021-11-03T13:00:00.000-07:00

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

Added support for Performance Max campaigns, a new campaign type that provides a unified buying service to virtually all Google Ads inventory. Performance Max also provides a superset of Smart Shopping Campaign functionality.
Added support for conversion goals to help you organize your conversion actions so that you can more easily optimize toward your advertising objectives.
Smart campaigns is in open beta and is now available for all users. We also added a new, more robust suggestion method, which leverages your company’s business details to suggest keyword themes for your Smart campaign.
Added support for an App campaign for pre-registration and the pre-registration ads which helps to gauge interest before an app or a game is available to install.
Migrated Video ads from using MediaFile to represent videos and images to using assets: AdVideoAsset and AdImageAsset. This includes the companion_banner and video fields of Video ads-related objects.
To comply with ATT, ConversionUploadService now supports conversion uploads with BRAID identifiers (ClickConversion.gbraid and ClickConversion.wbraid) in place of GCLID. BRAID identifiers are used for clicks associated with conversions from iOS14 devices. This feature is currently only available to allowlisted customers.
The Google Ads API now distinguishes between conversions with SKAdNetwork conversion value 0 and conversions with no conversion value present in the postback from Apple. Note that this feature is only available for SKAdNetwork conversions received after September 20th, 2021.
Added support for asset sets, which are a collection of assets. They will eventually replace the FeedService.
Added support for ad customizers for Responsive Search Ads.
Added support for warnings for OfflineUserDataJobService as AddOfflineUserDataJobOperationsRequest.enable_warnings. When set to true, any non-blocking errors pertaining to operation failures will be returned as AddOfflineUserDataJobResponse.warning.
ad_group_ad_asset_view reporting is now available for App engagement ads and responsive search ads.
Added support for retrieving hotel_reconciliation resources, which contain booking information to reconcile bookings from commission campaigns.
Added support for customer match rate range with CreateOfflineUserDataJobRequest.enable_match_rate_range_preview. The customer match rate range is the efficacy of your Customer Match uploads, which is the number of matched user data rows divided by the total number of Customer Match uploaded rows.
Added UserAttribute.shopping_loyalty to allow for sending loyalty-related data with UserAttribute.
Added the following types of assets, which will be available in all accounts by the end of 2021
- Price assets
- Hotel Callout assets
- Mobile App assets
- Call assets
- Call to action assets

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

Ads API apps must complete OAuth verification

2021-10-28T08:05:00.001-07:00

Last year, the OAuth scopes used by the following Ads APIs were classified as sensitive, requiring developers to complete the OAuth verification process for their Google Cloud projects:

Google Ads API & AdWords API
- https://www.googleapis.com/auth/adwords
Content API for Shopping
- https://www.googleapis.com/auth/content
DoubleClick Bid Manager API
- https://www.googleapis.com/auth/doubleclickbidmanager

Any remaining OAuth clients using the above scopes that remain unverified may have their existing credentials revoked and lose access to the above APIs if they do not complete the OAuth verification process as soon as possible.

Certain apps may qualify for one of the exceptions for app verification. If your application meets any one of those exceptions, follow the steps listed for the appropriate use case. If not, you must complete OAuth verification to continue using these Ads APIs.

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

Google Ads API & AdWords API: googleadsapi-support@google.com
Content API for Shopping: support forum
DoubleClick Bid Manager API: support contact form

Adam Ohren, Google Ads API Team

Google Ads API, Google Ads scripts, and AdWords API issues on Oct 1

2021-10-01T09:47:00.004-07:00

Between 2:50 am EDT and 6:40 am EDT on October 1, there was an outage that may have prevented some users from accessing the Google Ads API, Google Ads scripts, & the AdWords API. If you were using the Google Ads API or the AdWords API or running Google Ads scripts, then you may have experienced slowness or timeouts. Please check for any failed requests from these tools during the outage.

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

Josh Radcliff, Google Ads API Team

Feed-based Extensions Migration Reminder and Opt Out Instructions

2021-08-24T08:14:00.000-07:00

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 googleadsapi-support@google.com.
- Andrew Burke, Google Ads API Team

Announcing v8_1 of the Google Ads API

2021-08-11T14:20:00.000-07:00

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:

Support for two Smart Bidding features:
- Seasonality adjustments to let Smart Bidding apply conversion rate adjustments for future events such as promotions or sales.
- Data exclusions to let Smart Bidding exclude conversion data from specified dates. You can use this when there are issues with your account's conversion tracking during specific dates.
SmartCampaignSuggestService.SuggestSmartCampaignAd() to get suggestions for up to three headlines and two descriptions for Smart campaign ads based on information such as the landing page and keyword themes provided.
ConversionValueRule and ConversionValueRuleSet resources to adjust conversion values based on conditions like geographic location, device and audience, and to better express the value of conversions as they relate to your business.

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.
Thanet Knack Praneenararat, on behalf of the Google Ads API Team

Updates to how Google Ads API Smart Bidding strategies are organized

2021-07-22T10:01:00.000-07:00

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:

MaximizeConversions, with an optional target_cpa field (mutable starting in v8)
MaximizeConversionValue, with an optional target_roas field

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 googleadsapi-support@google.com.
Adam Ohren, Google Ads API Team

Google Ads API 2022 release and sunset schedule

2021-07-21T09:58:00.000-07:00

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.
- David Stevens, Google Ads API Product Manager