Starting in January 2025, we will enable consent unbundling in Google Ads scripts. This is a new feature of OAuth that allows you to customize which specific scopes you want to authorize, rather than the current all-or-nothing approach. Consent unbundling is being rolled out in all Google OAuth applications.

Google Ads scripts already runs a static analysis on your code before presenting the OAuth consent screen, and only requests the specific features that are required to run the script. Therefore, when you authorize Google Ads scripts, ensure that you select all the boxes on that screen, or else you will experience execution errors.

Any existing scripts you already have will continue to work without any user action needed when this feature rolls out, unless you make changes that require reauthorization. Existing unmodified scripts will continue to run as usual.

If you have any questions about consent unbundling or other Google Ads scripts features, please post them in the Google Ads scripts forum.
- Mike Cloonan, Google Ads Scripts Team

With v18 of the Google Ads API, you can now use the Recommendations.GenerateRecommendations method during campaign construction to retrieve optimized budget suggestions for Performance Max and Search campaigns.

When using the GenerateRecommendations method with a recommendation type of CAMPAIGN_BUDGET, you can supply inputs, such as final URL and bidding strategy, which Google machine learning models will use to generate budget recommendations. Google Ads API users that provide a campaign creation interface can provide budget prefills that fit into the campaign creation workflow. As with many recommendation types, campaign budget recommendations provide projected impact metrics to help understand the effect that implementing the recommendation will have on account performance.

Explore additional Recommendations API features

Recommendations in the Google Ads API offer several ways to increase your campaigns' performance through customized suggestions like adding new keywords or updating your bidding strategy. With RecommendationSubscriptionService, you can subscribe to automatically apply specific recommendation types of your choosing for your account. To retrieve and process recommendations directly, you can leverage the recommendation reporting resource.

To explore the full recommendations offering, check out our implementation guide.

 - Laura Chevalier, Google Ads API Team

Today, we’re announcing the October 2024 update to the Display & Video 360 API. This update adds the following:

• Support for cost-per-view performance goals and the targeting of connected devices.
• The ability to generate and download Structured Data Files (SDFs) using SDF v8. This version is currently in beta and only available to limited partners.
• Additional Adloox brand safety settings under third-party verifier targeting.

In addition, we’ve also officially deprecated the SDF v5.5 enum value given the sunset of v5.5 earlier this month.

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

If you need help with these new features, please contact us using our new Display & Video 360 API Technical support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Today, we’re announcing the v18 release of the Google Ads API. To use the v18 features, you will 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:

• You can now use GenerateRecommendations during campaign construction to retrieve optimized budget suggestions for Performance Max and Search campaigns.
• A new performance_max_placement_view report allows developers to query performance data for a given placement where Performance Max ads served.
• Replaced the summary_row_setting and return_total_results_count fields of SearchGoogleAdsRequest with the search_settings field, which allow developers to freely specify if summary_row, total_results_count and results will be returned with SearchGoogleAdsResponse.
• Added new segments for campaign and ad_group reports to allow for segmenting performance data based on a specific destination, such as a city or a country, for Hotel and Search campaigns.
• Added support for Travel Feeds in Search Ads with a new click type (ClickType.TRAVEL_ASSETS) and a new asset type (AssetSetType.TRAVEL_FEED).
• Added DataLinkService.CreateDataLink, which allows customers to link their Google Ads account to creator videos and enables running partnership ads.
• Added content_criterion_view which returns performance metrics of targeted contents, such as keywords, placements and topics, for Display, Demand Gen and Video campaigns.
• Renamed AssetType.DISCOVERY_CAROUSEL_CARD to AssetType.DEMAND_GEN_CAROUSEL_CARD.
• Added AdGroup.exclude_demographic_expansion which allows excluding demographics from being expanded when optimized_targeting_enabled is true, a feature that was previously only supported for Demand Gen.
• PhoneCallDetails.call_recording_url will be empty instead of providing an invalid URL if the call recording doesn’t exist for the given Local Services lead conversation.
• Added new metrics related to invalid clicks which can be queried with the campaign report.

Where can I learn more?
The following resources can help you get started:

• Release Notes
• Guides
• Reference
• Diff between v17 and v18

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

Starting November 13th, Google Ads will be implementing a new data retention policy. All account data, including performance metrics, billing information, and historical reports, will now be retained for a period of 11 years.

This means that when querying the Google Ads API using either GoogleAds.Search or GoogleAds.SearchStream you will only be able to retrieve data up to 11 years before the date of your API request and data before that will not be returned.

Required actions

If you need historical data for more than 11 years ago, we recommend you retrieve it and store it before November 13th, 2024.

Otherwise, no action is required on your end. This update will be applied automatically to your account and GoogleAds.Search and GoogleAds.SearchStream continue to work as usual.

However, be aware that you may notice differences in your reporting due to different values being returned.

If you have any questions or concerns, please don't hesitate to contact us via the forum.

 - Mattia Tommasone, Google Ads API Team

The detail_placement_view can be used to query metrics aggregated by ad group and URL or YouTube video in the Google Ads API. The detail_placement_view is not intended to be used for campaigns with an advertising_channel_type of PERFORMANCE_MAX, as this view is only intended to be used with campaigns containing ad groups, and Performance Max campaigns are constructed with asset groups rather than ad groups. However, this view is currently returning impression data for Performance Max campaigns. The impression metrics returned from the ​​detail_placement_view may not be accurate and should not be relied upon for campaigns with advertising_channel_type of PERFORMANCE_MAX.

In the next release of the Google Ads API, v18, we will be adding a new resource called performance_max_placement_view, which can be used to query placement impression data for Performance Max campaigns, and in a subsequent release, we will stop returning impression data from the ​​detail_placement_view for campaigns with advertising_channel_type of PERFORMANCE_MAX. Once performance_max_placement_view is released, use the data returned from that view for Performance Max campaigns rather than the data returned from the detail_placement_view.

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

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