We're pleased to announce that v202111 of the Google Ad Manager API is available starting today. This release brings new video features including more Video Opportunity metrics and GRP settings ...Read More

We're pleased to announce that v202111 of the Google Ad Manager API is available starting today. This release brings new video features including more Video Opportunity metrics and GRP settings for proposal line items.

Additionally, MCM users can now programmatically resend expired invitations using the new ResendInvitationAction. For altering revenue share or re-inviting an inactive child publisher, continue to use the ReInviteAction.

For the full list of changes for v202111 and all other active API versions, 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

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.Read More

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:

• Release Notes
• Deprecation Schedule
• Migration Guide
• AdWords API to Google Ads API Migration

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

Today we’re releasing an update to the Display & Video 360 API that primarily adds full support for managing custom bidding algorithms and their scripts. The update includes the following features ...Read More

Today we’re releasing an update to the Display & Video 360 API that primarily adds full support for managing custom bidding algorithms and their scripts. The update includes the following features:

• Functions to create new and update existing CustomBiddingAlgorithms.
• The ability to upload scripts through the process of retrieving an available resource location and then uploading the file to that location.
• A new customBiddingAlgorithms.scripts service to retrieve and create CustomBiddingScripts.
• Added support for the newest SDF version, v5.4, through the addition of an SdfVersion enum value.

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 updated our Managing Line Items guide to include a page describing the full process of implementing a custom bidding strategy 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

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 ...Read More

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

We removed the HOTEL_ADS_COMMISSION BudgetType enum from the Google Ads API in the v9 release. In the next few weeks, we will deprecate the HOTEL_ADS_COMMISSION BudgetType in all prior versions of the API and migrate existing ...Read More

We removed the HOTEL_ADS_COMMISSION BudgetType enum from the Google Ads API in the v9 release. In the next few weeks, we will deprecate the HOTEL_ADS_COMMISSION BudgetType in all prior versions of the API and migrate existing HOTEL_ADS_COMMISSION budgets to STANDARD budgets. Although the HOTEL_ADS_COMMISSION BudgetType enum will still exist in prior versions of the API, attempting to create a budget of type HOTEL_ADS_COMMISSION will result in an error after the change is completed. In addition, reports against existing budgets of type HOTEL_ADS_COMMISSION will reflect the STANDARD BudgetType after the migration. Please update your codebase accordingly to avoid any potential business interruptions.


If you have any questions about this change or need additional help, contact us through the forum or at googleadsapi-support@google.com.
- Devin Chasanoff, on behalf of the Google Ads API Team

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 ...Read More

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

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 ...Read More

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

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.Read More

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:

• Release Notes
• Migration Guide
• Guides
• Reference

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

On Tuesday, November 30, 2021, in accordance with the deprecation schedule, v202011 of the Ad Manager API will sunset. At that time, any requests made to this version will return errors.Read More

On Tuesday, November 30, 2021, in accordance with the deprecation schedule, v202011 of the Ad Manager API will sunset. At that time, any requests made to this version will return errors.

If you’re still using v202011, now is the time to upgrade to a newer release and take advantage of additional functionality. For example, in v202102 we added support for AudioCreatives, and in v202105 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:

• v202102
• The AuthenticationError enum value NOT_WHITELISTED_FOR_API_ACCESS was changed to NETWORK_API_ACCESS_DISABLED.
• The LineItem fields isPrioritizedPreferredDealsEnabled and adExchangeAuctionOpeningPriority were removed.
• For video Line Items, the videoMaxDuration field is now required and must be greater than 0.
• v202105
• Support was removed for filtering on the field keyValueMemberContent in CmsMetadataService.getCmsMetadataValuesByStatement. Use Content.cmsMetadataValueIds instead.
• v202108
• On the MobileApplication object, the singular field appStore was changed to the list field appStores.

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

 - Donovan McMurray, Ad Manager API Team