Today we’re announcing the beta release of Google Ads API v0_4. With minor versions like this one, you’ll continue to point to v0 as your endpoint, but you will need to update your client libraries to use the new features. Here are the highlights:

• Whitelist Removed. The whitelist has been removed for the Beta. All API users with an existing developer token in the AdWords API are now able to use the Google Ads API.
• Billing. BillingSetupService and AccountBudgetProposalService introduce the ability to set up billing. Please note, this does not provide the ability to fully set up account budgets yet. See the release notes for details.
• Campaigns. 
• Retrieve the AdGroupAdPolicySummary to determine why an ad has been disapproved.
• Change History.
• We’ve introduced ChangeStatus, allowing you to find the current status of changed resources in your account.
• The six supported resources are:
• AD_GROUP
• AD_GROUP_AD
• AD_GROUP_CRITERION
• CAMPAIGN
• CAMPAIGN_CRITERION
• Search for changed resources using GoogleAdsService.Search.
• Conversion tracking. Conversion tracking lets you measure the performance of your advertising against your business goals. The API allows you to set up and edit your conversion tracking setup. With ConversionActions, you can set up and edit the settings associated with your conversion actions supporting:
• AD_CALL
• CLICK_TO_CALL
• GOOGLE_PLAY_DOWNLOAD
• GOOGLE_PLAY_IN_APP_PURCHASE
• UPLOAD_CALLS
• UPLOAD_CLICKS
• WEBPAGE
• WEBSITE_CALL
• Shopping. Shopping campaigns help you promote your online and local inventory, boost traffic to your website or local store, and find better qualified leads.
• This release supports the creation of standard Shopping campaigns with Shopping Product Ads. Portfolio and campaign-local bidding strategies are supported types MANUAL_CPC, ENHANCED_CPC, TARGET_SPEND, TARGET_ROAS. Product offers can be subdivided into groups using the ListingGroupInfo criterion (equivalent to Product Groups in the Google Ads user interface), which currently supports the following dimension types: Product Condition, Product Type, Listing Brand, Listing Custom Attribute (L0-4), Product Channel, Product Channel Exclusivity, Product Offer Id.
• Video. 
• Retrieve information about your video campaigns from GoogleAdsService.Search, which includes video-specific metrics including video views, video view rate, video quartiles, and view-through conversions.
• Ruby client library. When upgrading your client library, please look at the ChangeLog as the require path and namespace have changed in this version.

To get started with the API, our team has put together these resources:

• Google Ads API Release Notes
• Google Ads API Reference
• Google Ads API Guides
• Google Ads API Client Libraries

The updated client libraries and code examples will be published within the next 48 hours. If you have any questions or need help, please contact us via the forum.




 Nadine Sundquist, on behalf of the Google Ads API Team

Have you ever wanted to see the AdWords API and Google Ads API services or reference pages relevant to the new Google Ads experience web page you’re browsing? Now you can easily do so by using our new Chrome extension, the AdWords & Google Ads API Web Navi!

How does it work?
The tool shows the AdWords API and Google Ads API resources (e.g., guides, service reference pages, report references) related to the web page of the new Google Ads experience you are visiting. Just choose the tab for the API of interest to view the relevant resources.

For example, in the animation below, a user has clicked on the extension’s icon while browsing the Ad groups page of the new Google Ads experience. The extension then shows some relevant resources for the AdWords API, e.g., Objects, Methods, and Services, AdGroupService, and Adgroup Performance Report. When the user clicks on the Google Ads API (Beta) tab, its resources are shown instead.

Below are the screenshots of both tabs:

The AdWords API Resources	The Google Ads API Resources

Resources in each tab are divided into sections — Guides, Services, and Reports for the AdWords API, and Guides, Services, and Fields for the Google Ads API.

In each AdWords API and Google Ads API release, we will update the tool to reflect the addition, update, and deletion of resources. Note that for services, the tool always shows the latest version of the API.

If you have any questions or comments, please post on our forum or add your comments directly in the Reviews tab of the extension page.
 - Thanet Praneenararat, Google Ads API Team

Today we’re announcing the release of AdWords API v201809. Here are the highlights:

• More available text in ads. Several ad types now have additional fields, and an increased character count of 90 characters for descriptions. Check out the release notes for more details.
• Traffic split in trials. The new trafficSplitType gives you greater control over how traffic is split in your trials.
• Conversion reporting. The new ConversionAttributionEventType field in the CAMPAIGN_PERFORMANCE_REPORT allows you to segment AllConversions and related metrics by event type (impression or interaction). In addition, the new ConversionAdjustment and ConversionAdjustmentLagBucket fields allow you to determine if conversion adjustments were applied and segment metrics by the number of days between the impression and either conversions or adjustments.

If you’re using v201802 of the AdWords API, please note that it will be sunset on January 30, 2019. We encourage you to skip v201806 and migrate straight to v201809. If you're using v201806, be aware it's now marked deprecated and will be sunset on March 26, 2019.

As with every new version of the AdWords API, please carefully review all changes in the release notes and the v201809 migration guide. The updated client libraries and code examples will be published within the next 48 hours.

If you have any questions or need help with migration, please contact us via the forum. 

Today we're announcing the general availability of Structured Data Files (SDF) v4.1 in the DoubleClick Bid Manager API. Highlights of this release include:

• Enhanced support for inventory source targeting
• Renaming changes to better align SDF with the Display & Video 360 UI

All SDF users are encouraged to begin requesting v4.1 files to take advantage of these new features. To do so, simply pass 4.1 as the value of version when calling Sdf.download. For users with workflows that are dependent on older SDF formats, details of the file format changes between versions can be found in the release notes.