Today, we’re announcing the v9 release of the Google Ads API. To use some of the v9 features, you 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 support for Performance Max campaigns, a new campaign type that provides a unified buying service to virtually all Google Ads inventory. Performance Max also provides a superset of Smart Shopping Campaign functionality.
• Added support for conversion goals to help you organize your conversion actions so that you can more easily optimize toward your advertising objectives.
• Smart campaigns is in open beta and is now available for all users. We also added a new, more robust suggestion method, which leverages your company’s business details to suggest keyword themes for your Smart campaign.
• Added support for an App campaign for pre-registration and the pre-registration ads which helps to gauge interest before an app or a game is available to install.
• Migrated Video ads from using MediaFile to represent videos and images to using assets: AdVideoAsset and AdImageAsset. This includes the companion_banner and video fields of Video ads-related objects.
• To comply with ATT, ConversionUploadService now supports conversion uploads with BRAID identifiers (ClickConversion.gbraid and ClickConversion.wbraid) in place of GCLID. BRAID identifiers are used for clicks associated with conversions from iOS14 devices. This feature is currently only available to allowlisted customers.
• The Google Ads API now distinguishes between conversions with SKAdNetwork conversion value 0 and conversions with no conversion value present in the postback from Apple. Note that this feature is only available for SKAdNetwork conversions received after September 20th, 2021.
• Added support for asset sets, which are a collection of assets. They will eventually replace the FeedService.
• Added support for ad customizers for Responsive Search Ads.
• Added support for warnings for OfflineUserDataJobService as AddOfflineUserDataJobOperationsRequest.enable_warnings. When set to true, any non-blocking errors pertaining to operation failures will be returned as AddOfflineUserDataJobResponse.warning.
• ad_group_ad_asset_view reporting is now available for App engagement ads and responsive search ads.
• Added support for retrieving hotel_reconciliation resources, which contain booking information to reconcile bookings from commission campaigns.
• Added support for customer match rate range with CreateOfflineUserDataJobRequest.enable_match_rate_range_preview. The customer match rate range is the efficacy of your Customer Match uploads, which is the number of matched user data rows divided by the total number of Customer Match uploaded rows.
• Added UserAttribute.shopping_loyalty to allow for sending loyalty-related data with UserAttribute.
• Added the following types of assets, which will be available in all accounts by the end of 2021
  • Price assets
  • Hotel Callout assets
  • Mobile App assets
  • Call assets
  • Call to action assets

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

• Release Notes
• Migration Guide
• Guides
• Reference

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

Today, we’re announcing the v8_1 release of the Google Ads API. To use some of the v8_1 features, you need to upgrade your client libraries and client code. The updated client libraries and code examples will be published next week. This version has no breaking changes.

Here’s what we added:

• Support for two Smart Bidding features:
  • Seasonality adjustments to let Smart Bidding apply conversion rate adjustments for future events such as promotions or sales.
  • Data exclusions to let Smart Bidding exclude conversion data from specified dates. You can use this when there are issues with your account's conversion tracking during specific dates.
• SmartCampaignSuggestService.SuggestSmartCampaignAd() to get suggestions for up to three headlines and two descriptions for Smart campaign ads based on information such as the landing page and keyword themes provided.
• ConversionValueRule and ConversionValueRuleSet resources to adjust conversion values based on conditions like geographic location, device and audience, and to better express the value of conversions as they relate to your business.

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

• Release Notes
• Guides
• Reference
  

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

In the Google Ads API v8, Call Only Ads are replaced by Call Ads. You can still create Call Only Ads in the AdWords API v201809 and the Google Ads API v6 and v7, but we encourage you to use v8 to create new Call Ads.

Call Only Ads will continue to serve until the AdWords API Sunset on 27 April 2022.

Prior to v8, Call Only Ads only offered users the ability to call. Users and advertisers have said they want the ability to go directly to the website from these ads. The addition of the final URL in Call Ads enables advertisers to use calls as the primary (i.e. headline) action, while still providing users with a means to visit an advertiser’s website prior to or instead of calling.

What you need to do

• Use the ad type CallAd instead of CallOnlyAd to create new Call Ads.
• Filter on ad.type = 'CALL_AD' to retrieve information for existing ads regardless of what ad.type was used to create the ad. For example, using the Google Ads API to query

  
      SELECT ad_group_ad.ad.call_ad.country_code,
             ad_group_ad.ad.call_ad.phone_number
      FROM ad_group_ad
      WHERE ad_group_ad.ad.type = 'CALL_AD'

  will return ads created as CALL_ONLY_AD and CALL_AD.

What has changed
Fields added

ad_group_ad.ad.final_urls	This is where you specify the URL of your website.
path1	First part of text that may appear appended to the url displayed in the ad.
path2	Second part of text that may appear appended to the url displayed in the ad. This field can only be set when path1 is set.

Field removed

ad.display_url

We removed the display_url for Call Only Ads. The URL that will be displayed alongside your ad will now be based on ad_group.ad.final_urls if provided, or phone_number_verification_url if ad_group.ad.final_urls is blank, as well any additional text you specify in path1 and path2.

Field verification

phone_number_verification_url

This field is now required if ad_group.ad.final_urls is empty.

AdWords API Reporting: There is no change in the AdWords API.

Google Ads API Reporting: In the Google Ads API you can include these new fields in your queries

• ad.final_urls
• ad.path1
• ad.path2

Where to get help
If you have questions about Call Ads, please reach out to us on the forum or at [email protected].

Bob Hancock, Google Ads API Team

Source: Google Ads Developer Blog

Today, we’re announcing the v8 release of the Google Ads API. To use v8 features, you will need to upgrade your client libraries and client code. The updated client libraries and code examples will be published next week. For more information on breaking changes, see the migration guide.
Here are the highlights:

• We’ve added cross-account bidding strategies, which allow for attaching manager-owned bidding strategies to client accounts. Also included is a new resource, AccessibleBiddingStrategy, which provides a read-only view of all bidding strategies accessible to the current customer (including portfolio strategies owned by the customer and cross-account bidding strategies shared with the customer).
• You can now retrieve labels managed by the manager account using CustomerClient.applied_labels.
• CallOnlyAdInfo is replaced with CallAdInfo to support more capabilities of this ad type. This includes the ability to append text after the URL displayed in the Ad using fields CallAdInfo.path1 and CallAdInfo.path2.
• ClickConversion now supports cart_data for uploading conversions with the additional information on the items sold.
• Several fields added to TransactionAttribute and UserAttribute allow you to associate more information about a sold item and a user’s purchase record, when uploading user data using UserDataService or OfflineUserDataJobService.
• We’ve added support for Smart campaigns, which allows for creating, monitoring and managing smart campaign types. Smart campaigns are highly automated, efficient campaigns designed to maximize returns with minimal ongoing management. For more details, visit our development guide.

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

• Release Notes
• Migration Guide
• Guides
• Reference

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