In the upcoming months, Display & Video 360 instant reports will be made available using the Bid Manager API. We previously announced the migration of certain report types from Offline Reporting to Instant Reporting.

In the upcoming months, Display & Video 360 instant reports will be made available using the Bid Manager API. We previously announced the migration of certain report types from Offline Reporting to Instant Reporting.

Once a partner is migrated, they will see the following changes:

  • Instant reports will be included in queries.list responses.
  • Existing Standard, Reach, YouTube, and URA reports will only be available under the Instant Reporting tab in the Display & Video 360 interface under the same query and report IDs.
  • If you use the Display & Video 360 interface to build new reports, you will need to build Standard, Reach, YouTube, and URA reports under the Instant Reporting tab.

This migration will happen by partner throughout the following months, with all reports under a partner migrated at once.

If you have questions about this migration in general, you can contact Display & Video 360 product support using this contact form. If you have questions about how this migration will impact the API, please contact us using our new Bid Manager API Technical support contact form.

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

  • The ability to retrieve and manage keyword targeting assigned at the advertiser level.
  • The optimizationObjective field in the InsertionOrder resource. This field is only writable for allowlisted customers, and will otherwise be set as null.

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

  • The ability to retrieve and manage keyword targeting assigned at the advertiser level.
  • The optimizationObjective field in the InsertionOrder resource. This field is only writable for allowlisted customers, and will otherwise be set as null.

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.

What’s New

Starting with Google Ads API v17, BatchJobService supports AssetGroupOperation. With this change you can use batch processing to create and manage entire Performance Max campaigns.

Batch processing is a powerful feature in the Google Ads API that lets you dispatch a set of operations, which might be interdependent, to multiple services without waiting for each operation to complete. Batch processing also provides automatic retries for transient errors, and automatic grouping of operations We have made batch processing available for AssetGroupOperation in response to your feedback to provide another option for working with asset groups asynchronously.

What’s New

Starting with Google Ads API v17, BatchJobService supports AssetGroupOperation. With this change you can use batch processing to create and manage entire Performance Max campaigns.

Batch processing is a powerful feature in the Google Ads API that lets you dispatch a set of operations, which might be interdependent, to multiple services without waiting for each operation to complete. Batch processing also provides automatic retries for transient errors, and automatic grouping of operations We have made batch processing available for AssetGroupOperation in response to your feedback to provide another option for working with asset groups asynchronously.

Implementation Details

Using AssetGroupOperation with batch processing for Performance Max campaigns is similar to how you use other operations, with the following special considerations:

When creating asset groups using batch processing, AssetGroupOperation and AssetGroupAssetOperation must be sequential without other operations in between. This is due to how operations are grouped together when processed. You can learn more about the considerations and best practices for using batch processing to create Performance Max campaigns in the Batch processing for Performance Max guide.

Here’s how to create an asset group in a batch job:

  1. Create a MutateOperation containing an AssetGroupOperation. This is no different than creating a MutateOperation using the GoogleAdsService.Mutate service. See the mutating resources guide.
  2. Associate assets with the asset group by creating a MutateOperation containing operations of type AssetGroupAssetOperation for each asset required; the sequential AssetGroupOperation and operations of type AssetGroupAssetOperation must combine to meet applicable minimum asset requirements.
  3. Add the operations of type MutateOperation to the batch job as you would with any other type of operation.
  4. Run the batch job by calling RunBatchJob after adding all operations.

The following resources contain additional information to help you with your integration:

Improving Performance Max integrations Blog Series

This article is part of a series that discusses new and upcoming features that you have been asking for. We’ll cover what’s new and how it differs from the current implementation approach.

Keep an eye out for further updates and improvements on our developer blog, continue providing feedback on Performance Max integrations with the Google Ads API, and as always, contact our team if you need support.

Workshop Reminder

Register today for the Performance Max and the Google Ads API workshop happening on July 17!

Today, we’re announcing an upcoming developer workshop, Performance Max and the Google Ads API. These virtual sessions will provide you with knowledge, resources, and support to create, manage, and report on Performance Max campaigns in the Google Ads API. The workshop will be presented live in three regions on July 17, 2024.

Today, we’re announcing an upcoming developer workshop, Performance Max and the Google Ads API. These virtual sessions will provide you with knowledge, resources, and support to create, manage, and report on Performance Max campaigns in the Google Ads API. The workshop will be presented live in three regions on July 17, 2024.

Regional Workshop Times & Agendas

Hear from Google Ads API experts as we:

  • Tour the core features and business goals available in Performance Max campaigns.
  • Detail key technical pieces of your Performance Max implementation, from setup to reporting.
  • Build a Performance Max interface in an interactive demo.
  • Review best practices for configuring and optimizing your Performance Max campaigns.
  • Discuss Performance Max and AI in an experts panel.

Whether you’re new to Performance Max or looking to expand upon an existing integration, we'll have a variety of sessions to help you achieve your goals and boost your Google Ads account performance with the power of Google AI. We’ll be delivering several talks to discuss what's unique about Performance Max and explain key concepts across experience levels.

Throughout the workshop, you’ll have the opportunity to interact with our team via live Q&A.

Head over to the event site to register and view the full agenda. We look forward to seeing you!

What's Happening?

As we continue to improve our support experience, we are making changes to how you contact the Content API for Shopping support team.

What's Changing?

How you contact “Content API for Shopping” Support:

What's Happening?

As we continue to improve our support experience, we are making changes to how you contact the Content API for Shopping support team.

What's Changing?

How you contact “Content API for Shopping” Support:

  • Shutting down current support path: Effective June 10, 2024, the support email address (shopping-api-support) and the Developer Forum will no longer accept support questions.
  • New support paths:
    • To reach our “Content API for Shopping” support team, please use our new Contact Us Form: link here
    • To reach our "Comparison Shopping Services API" support team, please use this Contact Us Form: link here
    • Going forward, these will be the only support paths available.

This change will help us better understand user needs and provide quicker solutions. We appreciate your partnership.

In the meantime, please reference the following sites for integration/API information:

Your Content API for Shopping Team

Today, we’re announcing the v17 release of the Google Ads API. To use some of the v17 features, you will need to upgrade your client libraries and client code. The updated client libraries and code examples will be published next week.
Today, we’re announcing the v17 release of the Google Ads API. To use some of the v17 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: Where can I learn more?
The following resources can help you get started: If you have any questions or need additional help, contact us via the forum.

Today we’re deprecating the publisherReviewStatuses field in the Display & Video 360 API Creative resource. The field will sunset on June 26, 2024. After the sunset, publisherReviewStatuses will always contain an empty array in retrieved Creative resources.

Today we’re deprecating the publisherReviewStatuses field in the Display & Video 360 API Creative resource. The field will sunset on June 26, 2024. After the sunset, publisherReviewStatuses will always contain an empty array in retrieved Creative resources.

We’ve added the upcoming sunset to our list of feature deprecations. To avoid any issues, we recommend that you stop reading the publisherReviewStatuses field from retrieved Creative resources.

If you have questions regarding these changes, please follow the instructions on our support guide or contact us using our contact form.