Starting on October 16, 2024, we will start rolling out changes to search and display reporting. As a result of this change, Google Ads Query Language (GAQL) queries for campaigns with an advertising_channel_type of SEARCH or DISPLAY will return a value of 0 for any metrics in that GAQL query when you include the fields segments.asset_interaction_target.asset or segments.asset_interaction_target.interaction_on_this_asset in the query.

Read More

Starting on October 16, 2024, we will start rolling out changes to search and display reporting. As a result of this change, Google Ads Query Language (GAQL) queries for campaigns with an advertising_channel_type of SEARCH or DISPLAY will return a value of 0 for any metrics in that GAQL query when you include the fields segments.asset_interaction_target.asset or segments.asset_interaction_target.interaction_on_this_asset in the query.

We are making this change now to ensure the accuracy of reporting data in preparation for future launches. If you have any questions or need help, check out the Google Ads API support page for options.

- Devin Chasanoff, on behalf of the Google Ads API Team

We are removing the ability to create new Smart Display Campaigns in all versions of the Google Ads API. Version v12 already has these changes implemented.

On January 17, 2023 we will make a breaking change to all active versions of the Google Ads API older than v12, disallowing the creation of new Smart Display Campaigns in the API.Read More

We are removing the ability to create new Smart Display Campaigns in all versions of the Google Ads API. Version v12 already has these changes implemented.

On January 17, 2023 we will make a breaking change to all active versions of the Google Ads API older than v12, disallowing the creation of new Smart Display Campaigns in the API.

You will still be able to update your existing Smart Display Campaigns until they are auto-migrated in Q1 2023. For more information, please see this Help Center article.

Change Description
In all versions, after January 17, 2023, mutate operations to create a Smart Display Campaign (setting the AdvertisingChannelSubType to DISPLAY_SMART_CAMPAIGN) will throw an OperationAccessDeniedError.CREATE_OPERATION_NOT_PERMITTED error.

Next Steps
If you receive this error during Smart Display Campaign creation, you should create a Standard Display Campaign instead by leaving the optional AdvertisingChannelSubType field blank.

If you have any questions about this change or any other API feature, please contact us via the forum.
- Cory Liseno, Google Ads API Team

 - Anash P. Oommen, Google Ads API Team Read More

What’s changing?

We are changing how stats for Search campaigns with Display Expansion (previously known as Search campaigns with Display Select) are reported by the AdWords API, the Google Ads API, and Google Ads scripts.

Starting the week of Feb 17, 2020, we will no longer return display keyword stats for Search campaigns with Display Expansion in

• Display Keyword Performance Report in the AdWords API and Google Ads scripts
• Display_keyword_view in the Google Ads API.

Why is this changing?

Search campaigns with Display Expansion historically used keywords to perform Display Expansion. As we strive to improve targeting for Display Expansion, it is no longer possible to meaningfully and consistently attribute stats to keywords. As a result, this view has been removed from the Google Ads UI. The changes in this announcement aim to create parity between APIs and UI.


What should I do?

Before the sunset date, we recommend switching to alternate reports for fetching stats for Search campaigns with Display Expansion.

• Automatic Placement Performance reports and Display Topics Performance report can be used in the AdWords API and Google Ads scripts to get granular performance data about these campaigns in the Display Network. If you use the Google Ads API, you can use group_placement_view and topic_view instead.
• Reports such as Campaign Performance report or Ad Group Performance report can be used in the AdWords API and Google Ads scripts to fetch aggregate performance stats for these campaigns. You need to filter by AdNetworkType2 = CONTENT for Display Network stats. If you use the Google Ads API, you can use the campaign or ad_group view instead.

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

 - Anash P. Oommen, Google Ads API Team

Read More

Update (Aug 6, 2019): Links and wording updated to reflect changes in v1 of Google Ads API. Renamed the existing ResponsiveDisplayAdInfo type to LegacyResponsiveDisplayAdInfo. Added a new ResponsiveDisplayAdInfo type for asset-based responsive display ads.

What's changing?
Starting May 15, 2019, AdWords API and Google Ads API requests that attempt to create or modify a responsive ad will fail. Make sure you migrate to the new asset-based responsive display ad before the deprecation date.

Due to changes and improvements to ad types in Display campaigns, keeping track of the names in the UI and APIs can be tricky, so here's a quick overview:

Ad type in the UI	AdWords API type	Google Ads API type
Responsive ad	ResponsiveDisplayAd	LegacyResponsiveDisplayAdInfo
Responsive display ad	MultiAssetResponsiveDisplayAd	ResponsiveDisplayAdInfo

After the deprecation date, behavior of the APIs will change as follows:

• AdWords API
  • AdGroupAdService requests that attempt to create a ResponsiveDisplayAd will fail with the error AdGroupAdError.CANNOT_CREATE_DEPRECATED_ADS. The API will continue to allow you to remove ResponsiveDisplayAds and modify the status of existing ads.
  • AdService requests that attempt to modify a ResponsiveDisplayAd will fail with the error AdError.CANNOT_MODIFY_AD.
• Google Ads API
  • AdGroupAdService requests that attempt to create a LegacyResponsiveDisplayAdInfo will fail with the error AdGroupAdError.CANNOT_CREATE_DEPRECATED_ADS. The API will continue to allow you to remove LegacyResponsiveDisplayAdInfos and modify the status of existing ads.

Both APIs will continue to return performance statistics for the deprecated ad types.

Why is this happening?
In October, 2018, responsive display ads replaced responsive ads as the default asset-based ad type for the Display network. To simplify the product suite, we'll be deprecating creation and modification of responsive ads.

What should you do?
Before the deprecation date:

• If you use the AdWords API, modify your code to use ResponsiveDisplayAdInfo wherever you currently use ResponsiveDisplayAd. Check out the guide and accompanying code example in the .NET, Java, Python, or Ruby client library to help you with the migration.
• If you use the Google Ads API, modify your code to use ResponsiveDisplayAdInfo whenever you currently use LegacyResponsiveDisplayAdInfo.

If you have any questions or need help, please contact us via the forum.
- Josh Radcliff, Google Ads API Team