Google Ads has rolled out a new feature that allows Google Ads account administrators to grant access to a service account. Once the access has been granted, you can use the service account credentials to make API calls to that Google Ads account and other accounts in that hierarchy, if applicable. Refer to the service account guide to learn more about this option.

Google Ads has rolled out a new feature that allows Google Ads account administrators to grant access to a service account. Once the access has been granted, you can use the service account credentials to make API calls to that Google Ads account and other accounts in that hierarchy, if applicable. Refer to the service account guide to learn more about this option.

This new approach simplifies the Google Ads API authentication process in two important ways:

  1. If your application works entirely offline without any user interaction, then you no longer need to generate a refresh token. This means you can also avoid other steps such as configuring an OAuth consent screen and performing OAuth App verification.
  2. The new service account flow doesn’t require you to be a Google Workspace user or configure the service account for domain-wide impersonation.

We hope this simplifies your experience when working with the Google Ads API.

How to get help

If you have any questions or need help, check out the Google Ads API support page for options.

 - , Google Ads API Team

标签： , ,

We're pleased to announce that v202411 of the Google Ad Manager API is available starting today, November 21, 2024. This release brings support for INVENTORY_FORMAT reporting dimensions and removes GOOGLE as a GrpProvider.

We're pleased to announce that v202411 of the Google Ad Manager API is available starting today, November 21, 2024. This release brings support for INVENTORY_FORMAT reporting dimensions and removes GOOGLE as a GrpProvider.

In the PublisherQueryLanguageService Line_Item table, the field EndDateTime has been renamed to ServingEndTime. In both v202411 and earlier versions, the value is inclusive of any grace period. The new name differentiates the PQL field from the LineItem.endDateTime field which is exclusive of any grace period.

Version Service End time including grace period End time excluding grace period
v202411 PublisherQueryLanguageService ServingEndTime Not available
LineItemService endDateTime + autoExtensionDays endDateTime
v202408 PublisherQueryLanguageService EndDateTime Not available
LineItemService endDateTime + autoExtensionDays endDateTime

For the full list of changes, check the release notes. Contact us on the Ad Manager API forum with any API-related questions.

- Chris Seeley, Ad Manager API Team
标签： , ,

Starting today, you can populate reports in the Bid Manager API with data that had been previously omitted due to lower statistical significance by using a new filter, FILTER_UNIQUE_REACH_SAMPLE_SIZE_ID, and setting the value to “0”.

Starting today, you can populate reports in the Bid Manager API with data that had been previously omitted due to lower statistical significance by using a new filter, FILTER_UNIQUE_REACH_SAMPLE_SIZE_ID, and setting the value to “0”.

This filter setting only impacts reach metrics with the following Metric prefixes as defined in the Bid Manager API:

  • METRIC_UNIQUE_REACH_
  • METRIC_VIRTUAL_PEOPLE_DUPLICATE_
  • METRIC_VIRTUAL_PEOPLE_EXCLUSIVE_
  • METRIC_VIRTUAL_PEOPLE_OVERLAP_

queries.create requests with queries that filter by FILTER_UNIQUE_REACH_SAMPLE_SIZE_ID but don’t include impacted metrics will return a 400 error.

On February 4, 2025, Display & Video 360 will include unique reach data with lower statistical confidence by default. If you want to ensure that your reports continue to only return high-confidence data, we recommend that you update your integration to use the new filter value to filter to "1" when creating reports with any of the impacted metrics.

Read more about these changes in our release notes.

If you run into issues or have questions about these changes, please contact us using our new Bid Manager API Technical support contact form.

- Trevor Mulchay, Bid Manager API Team
标签： ,

We’re announcing our tentative 2025 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 versions.
We’re announcing our tentative 2025 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 versions.
Version Planned Release
Type* 		Projected launch* Projected sunset*
V19 Major February/March 2025 February 2026
V19_1 Minor April/May 2025 February 2026
V20 Major June/July 2025 June 2026
V20_1 Minor August/September 2025 June 2026
V21 Major October/November 2025 October 2026

*Estimated and subject to change

Where can I learn more?
Check back for any updates as the blog is the best place to stay informed about developments in this space.

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

Today we’re announcing the general availability of Structured Data Files (SDF) v8. All users can now use SDF v8 to upload and download SDFs in the Display & Video 360 UI, and to download SDFs through the Display & Video 360 API.

Today we’re announcing the general availability of Structured Data Files (SDF) v8. All users can now use SDF v8 to upload and download SDFs in the Display & Video 360 UI, and to download SDFs through the Display & Video 360 API.

SDF v8 adds support for Demand Gen Line Item, Ad Group, and Ad resources, as well as the companion banner field for YouTube and Demand Gen Ads.

Full details on the changes made in v8 can be found in our Structured Data Files release notes and instructions for migrating from v7.1 to v8 can be found in our migration guide. If you are currently using SDF v6, follow the instructions in our v7 migration guide first before migrating to v8.

If you run into issues or need help with this new version, please follow the instructions on our support guide or contact us using our contact form.

- Trevor Mulchay, Display & Video 360 API Team
标签： , ,

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.
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
标签：