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

Update (December 21, 2020 16:50 EST): The issue below also occurred between 8:15 am EST and 9:30 am EST on December 20, and has since been resolved.

Between 8:30 am EST and 12:50 pm EST on December 17 and 8:15 am and 9:30 am EST on December 20, there were outages that may have prevented some users from accessing the Google Ads API & Google Ads scripts. If you were using the Google Ads API or running Google Ads scripts using the beta AdsApp.search feature or the Google Ads scripts beta, then you may have experienced slowness, errors, or timeouts. This issue has been resolved, but please check for any failed requests from these tools during the outage and consider re-running the impacted operations.

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

Josh Radcliff, Google Ads API Team

Starting February 15, 2022, all existing and future Smart Shopping Campaigns (SSC) will use a shared budget type. Although shared, the assigned budget will only be used by the SSC and will behave like a standard, non-shared campaign budget. New campaigns cannot be added to the shared budget. This change will not have any impact on campaign performance. In reports and queries, existing and future SSC budgets will be returned as explicitly_shared = true (isExplicitlyShared in AdWords API).

Note: the AdWords API will sunset on April 27, 2022. Developers must migrate to the Google Ads API before then.

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

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

CAF DAI SDK ReleasedThe Interactive Media Ads team is excited to announce that we’ve teamed up with the Cast Application Framework team to bring you the CAF DAI SDK, a fully supported solution for casting DAI video streams to Chromecast devices. This project is a complete rewrite of our original IMA SDK for Cast, significantly reducing the amount of code publishers need to write and streamlining the integration between the two SDKs.

The CAF DAI SDK provides a deep integration with Chromecast Application Framework's native Ad Breaks, meaning that adding around 30 lines of code to an existing CAF receiver can enable:

• DAI support for both Live and VOD streams
• Media queue management
• Sender and receiver UI, including ad break markers
• Bidirectional communications between sender and receiver
• Skippable ad support on VOD streams

With the previous SDK, all of these functions required manual implementation.


A fully-featured CAF DAI integration



IMA SDK for Cast deprecatedAs of December 13, 2021, both the client-side and DAI versions of the IMA SDK for cast are now deprecated. Publishers who are currently using the IMA SDK for cast to implement client-side advertisements are encouraged to migrate to using CAF native ad breaks. Publishers who are currently using the IMA SDK for cast to implement DAI advertisements are encouraged to migrate to the new CAF DAI SDK. These new implementation options offer publishers significantly simpler integrations with better stability and tighter integration with the entire cast ecosystem.

Advertisement Type	Deprecated Solution	Recommended Solution
Client Side	IMA SDK for Cast	CAF native ad breaks
DAI	IMA SDK for Cast	CAF DAI SDK

The Client side and DAI versions of the IMA SDK for Cast will continue to function for the foreseeable future but support and new development will be focused on the CAF DAI SDK moving forward. The IMA SDK team will continue to offer best attempt support for the deprecated SDKs through December of 2022, however, some limitations of the older platform may only be resolved by migrating to the new workflows described above.


We highly recommend that publishers who are currently using the older IMA SDK for Cast begin migrating to these new workflows for improved stability, simplified integration, and a much more polished developer experience.


—


For more information about these changes, check out the developer documentation. If you have any issues migrating your integration from the IMA SDK for Cast to the CAF DAI SDK, feel free to reach out via our developer forums.

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:

• Extensions
• Dynamic Search Ads
• Dynamic Remarketing

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

If you are using an Ads API Client Library and Apache Log4j, please see below.

NIST has announced a recent vulnerability in the Apache Log4j library.

The Apache Log4j utility is a commonly used component for logging requests. On December 9, 2021, a vulnerability was reported that could allow a system running older Apache Log4j versions to be compromised.

What do you need to do?
If you are using an Ads API Client Library and affected Apache Log4j versions, please upgrade to the latest version as indicated in the Apache Log4j Security Vulnerabilities website.

If you have any questions or need additional help, contact us through this forum.
--Stan Grinberg, Ads Developer Relations

Campaign Manager 360 API v3.4 will sunset on Jan 10th, 2022. After this date, all requests made to v3.4 of this API will fail. If you're still using this version, you must migrate to the most current release to avoid an interruption in service.

See the migration guide for details. Most likely, you just need to adopt the latest version of your preferred client library. However, all users are advised to review the release notes to learn about important version differences you may need to be aware of.

If you have questions about this or anything else Campaign Manager 360 API related, feel free to reach out to us on our support forum.
- Ruizhi Liao, CM360 API Team

Today we’re releasing a small update to the Display & Video 360 API to add support for audio content type targeting under TARGETING_TYPE_AUDIO_CONTENT_TYPE.

You can find more detailed information about this update in the Display & Video 360 API release notes. Before using these new features, make sure to update your client library to the latest version.

If you run into issues or need help with these new features, please contact us through our support contact form.
- Trevor Mulchay, Display & Video 360 API Team

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

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.

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:

• 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 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 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, 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 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