Today we’re announcing the launch of Display & Video 360 API v3 out of public beta and into general availability. With this launch, v3 becomes our recommended version, and our guides have been updated to reflect v3 features and conventions.

Today’s launch also makes the following changes:

• Adds Structured Data Files v7 support to Display & Video 360 API v2 and v3 through a new SdfVersion enum value.
• Renames an AdGroupFormat enum value from AD_GROUP_FORMAT_ACTION to AD_GROUP_FORMAT_RESPONSIVE in v3.

Read the Display & Video 360 API release notes for more details on this and previous updates. Instructions on migrating from v2 to v3 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 breaking changes, 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 are expanding support for YouTube Select forecasting in ReachPlanService to additional markets on November 14, 2023. We introduced two new error codes in v15 of the Google Ads API to support these new markets.

Error code	Reason
ReachPlanError.NOT_FORECASTABLE_NOT_ENOUGH_INVENTORY	There isn’t enough inventory available for forecast.
ReachPlanError.NOT_FORECASTABLE_ACCOUNT_NOT_ENABLED	The account isn’t enabled.

Note: earlier versions of the Google Ads API that do not contain these error codes will throw a ReachPlanError.UNKNOWN error.

If you use this feature, make sure you update your code to handle these additional error codes before November 14, 2023.

For more information regarding Reach Forecasting, visit the Reach Forecasting guide. If you have any questions, please contact us through our support page or on the forum.

 - Anash P. Oommen, Google Ads API Team

Google announced in September that there would be upcoming changes to support the Digital Markets Act (DMA). Google is releasing changes to the Google Ads API and the Display & Video 360 API as quickly as possible so that our developers have time to make application changes before DMA starts being enforced, expected March 6, 2024. Review the EU user consent policy for a reminder on our consent requirements for users in the European Economic Area.

What should I change for the Google Ads API?

The Google Ads API v15 release introduced the Consent object for uploading consent with your data. This Consent is used across all uploads for call conversions, click conversions , Customer Match, and Store Sales. Here is where to set the Consent for each feature.

Feature	Code change
Call Conversions	Set Consent for each call conversion event at CallConversion.consent. See the guide for details.
Click Conversions	Set Consent for each click conversion event at ClickConversion.consent. See the guide for details.
Customer Match	Set Consent for each Customer Match job at CustomerMatchUserListMetadata.consent. See the guide for details.
Store Sales	Set Consent for each Store Sales event at UserData.consent. See the guide for details.

What should I change for the Display & Video 360 API?

The Display & Video 360 API will be releasing similar changes in the following months announced via this blog. Check back in the release notes for updates to existing versions and the Customer Match feature guide for updated implementation instructions.

Where can I get support?

If you have questions, reach out to us googleadsapi-support@google.com for the Google Ads API or the support form for the Display & Video 360 API.

Nadine Wang, on behalf of the Google Ads API and Display & Video 360 API Teams

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

• Added RecommendationSubscriptionService which manages recommendation subscriptions and lets you automatically apply the recommendations.
• Added new recommendation types: FORECASTING_SET_TARGET_CPA, SET_TARGET_CPA, SET_TARGET_ROAS.
• Updates to Performance Max:
  • Added AssetGroupSignal.search_theme which lets you attach a search theme to asset groups for enhanced targeting.
  • Added a new asset_group_top_combination_view to report the top performing assets at the asset group level.
  • asset_group can now be queried with metric fields to support retrieving the performance of an asset group of a Performance Max campaign.
• Added UserList.lookalike_user_list to support creating a Lookalike segment, an audience created based on the provided existing seed audience. Lookalike segments can be used in a Demand Gen campaign only.
• Added support of reporting for Apple's SkAdNetwork 4 conversions, including web to app conversions on Google search. You can now segment by coarse conversion value, source domain, and postback sequence index.
• Improved offline conversion upload diagnostics in the offline_conversion_upload_client_summary report, with more useful details of the conversion upload status such as successful events, success rate, error percentage.
• Added support of sales and profit metrics such as revenue, gross profit, gross profit margin, and units sold. These metrics are available to all advertisers who implement conversions with cart data across Search, Shopping, and Performance Max campaigns.
• Added LocalServicesSettings and its fields to the customer report for returning a Local Services advertiser’s granular license and insurance statuses. We also added new reports for Local Services ads including local_services_lead, local_services_lead_conversation, and local_services_verification_artifact.
• Changes to linking accounts:
  • Added support for adding and removing a link between a Google Ads account and a Merchant Center account using ProductLink.merchant_center and removed MerchantCenterLinkService.
  • Added ProductLinkInvitationService to support updating a link invitation sent from other products, available for Hotel Center and Merchant Center accounts.
    • Removed AccountLink.hotel_center and support for updating link invitations from Hotel Center accounts via AccountLinkService.
• Changes to Shopping campaigns:
  • Removed ShoppingSetting.sales_country, whose values are now returned as ShoppingSetting.feed_label.
  • Removed support for adding Campaign.shopping_setting to Search campaigns.
  • Removed support for adding CampaignCriterion.listing_scope to Search campaigns.
• Added support for targeting Google TV and YouTube at the campaign level using NetworkSettings.
• Added CustomerLifecycleService.ConfigureCustomerLifecycleGoals and CampaignLifecycleService.ConfigureCampaignLifecycleGoals for configuring customer acquisition goals at the customer and campaign levels, respectively.
• Added consent to the below classes. No action is required at this time, but please follow our blog for updates in the coming months.
  • UserData
  • CustomerMatchUserListMetadata
  • CallConversion
  • ClickConversion
• Added BrandSuggestionService which can suggest brands based on the provided brand prefix and the excluded list of brands. These brands can be used to create a BRAND criterion, added to a BRANDS shared set, and then attached to a campaign by creating a CampaignCriterion with brand_list set to the shared set. These campaign criteria must have their negative field set to false in Search campaigns and true in Performance Max campaigns.

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

• Release Notes
• Guides
• Reference
• Diff between v14 and v15

If you have any questions or need additional help, contact us through the forum.
 - Thanet Knack Praneenararat, on behalf of the Google Ads API Team

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