We’re pleased to announce that Display & Video 360 API v3 is available in public beta starting today.

v3 includes a number of new features and breaking changes. Here are some of the changes introduced in v3:

• You can now fully manage proximity location lists, enabling you to use the advertisers.locationLists.assignedLocations service to create and delete locations assigned to TARGETING_LOCATION_TYPE_PROXIMITY LocationList resources.
• You can now more easily enable optimized targeting for your line items using the new boolean enableOptimizedTargeting field, which replaces the targetingExpansionLevel field in the TargetingExpansionConfig object.
• The billingConfig field is now required in the Advertiser resource and must be included when making advertisers.create requests. To help with this, a new billingConfig field has been added to the Partner resource to surface the billing information for the parent partner.
• YoutubeAdGroup and YoutubeAdGroupAd resources have been renamed to AdGroup and AdGroupAd.

More detailed information about this release can be found in our release notes. Follow the steps in our migration guide to migrate from v2 to v3. Be aware that breaking changes may be made to v3 while in beta and will be listed in the Display & Video 360 API release notes.

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 October 2022 update to Display & Video 360 API v2, which is still in beta. This update includes the following features:

• Partial insertion order targeting write support for a subset of targeting types with the addition of create and delete methods to the insertion order AssignedTargetingOptions service.
• The ability to duplicate an existing line item to create a new line item with identical settings and assigned targeting under the same insertion order.

More detailed information about this update can be found in the Display & Video 360 API release notes and updated instructions on migrating from v1 to v2 can be found in our migration guide. Before using these new features, make sure to update your client library to the latest version.

If you have questions regarding the breaking changes or run into issues or need help with these new features, please contact us using our support contact form.
- Trevor Mulchay, Display & Video 360 API Team

We’re pleased to announce that Display & Video 360 API v2 is available in public beta starting today. We're also extending our DV360 API Developer Survey through the end of September so that we can gather more customer feedback on v2 and the API in general.

v2 includes a number of new features and breaking changes. Here are some of the changes introduced in v2:

• You can now retrieve YouTube & Partners line items and their targeting settings using get and list methods in the advertisers.lineItems and advertisers.lineItems.targetingTypes.assignedTargetingOptions services.
• You can now retrieve and update assigned targeting options for multiple line items in a single request using the new advertisers.lineItems.bulkListAssignedTargetingOptions and advertisers.lineItems.bulkEditAssignedTargetingOptions methods.
• You can now update the lineItem.entityStatus field across multiple line items in a single request using the new advertisers.lineItems.bulkUpdate method.
• Some targeting types now use enum values as assignedTargetingOptionId values, enabling the retrieval, creation, and deletion of targeting settings with enums.

More detailed information about this release can be found in our release notes. Follow the steps in our migration guide to migrate from v1 to v2. As it is in beta, be aware that we might make unversioned breaking changes to DV360 API v2 before it exits the beta phase.

If you want to provide feedback and recommend features that should be included in future versions of the API, please fill out our DV360 API Developer Survey. The survey has been extended through the end of September and will help shape the product roadmap for v2 and beyond.

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

Since our last announcement in July, we've made several updates to improve the performance of the Google Ads API. Your feedback was essential to us in making these improvements and will continue to be throughout the remainder of the Beta.

What has been fixed?
Over the past several months, we've rolled out performance improvements to Google Ads API read and mutate functionality. Some of these updates are visible in recent versions of the API, such as the launch of GoogleAdsService.SearchStream() in v3_0, while other improvements have sped up the response times of existing services and methods.

What's next for the Google Ads API Beta?
It is our top priority to get the Google Ads API ready for general availability. This involves rolling out features for key user journeys, for example: a service for asynchronous batch updates. If you have any feedback on the API's readiness to address your tool's requirements, we'd like to hear from you!

Which API should I use?
Throughout the remainder of the Beta, the AdWords API will continue to be the primary API for programmatically accessing and managing Google Ads campaigns. When deciding whether to use the Google Ads API Beta to run production systems, please keep in mind that we may release updates in preparation for general availability. As a reminder, changes will be released in new versions of the Google Ads API Beta. They will not affect your existing code unless announced otherwise on this blog.

If you have any feedback or questions regarding the performance, feature availability and overall usability of the Google Ads API Beta, please contact us at googleadsapi-support@google.com.
-- The Google Ads API team

We are excited to announce that AdWords scripts for MCC is now available as a limited beta for developers. This beta allows you to create AdWords scripts at the MCC level to efficiently manage changes across your client accounts at scale.

You can sign up for the limited beta at https://services.google.com/fb/forms/mccscripts. Once we’ve added you, we’ll send you an email with instructions on how to get started with MCC Scripts. You can learn more about this feature on our getting started guide.

We encourage you to try out this new feature and let us know what you think on our forum or our Google+ page.

- Anash P. Oommen, AdWords Scripts Team