Tag Archives: release

Announcing v0_4 of the Google Ads API

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. 
  • 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:

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

Announcing v201809 of the AdWords API

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. 

- Josh Radcliff on behalf of the AdWords API Team.

Announcing v0_3 of the Google Ads API

Today we’re announcing the beta release of Google Ads API v0_3. 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:

  • Campaigns. We’re expanding beyond Search campaigns with keyword targeting to include:
    • Display campaigns
    • Campaign groups
    • Ad schedules
    • Campaign shared sets
    • Shared sets for keyword criteria
    • Campaign bid modifiers for interaction types.
    • Ad group bid modifiers.
  • Queries. GoogleAdsService.search provides the ability to filter by resource name.
  • Creatives. For ad disapproval error handling, PolicyFindingDetails replaces PolicyViolationDetails for expanded text ads.
  • Hotel Ads. Hotel ads, first introduced in v0_1, is a whitelisted feature with an ad type that is created automatically by the system based on your provided hotel listings and prices. To learn more about the hotel ads migration and what’s next, check out our recent webinar:
  • Recommendations. Recommendations provide customized suggestions to help increase your campaigns' performance. In the v0_3 release, we’ve added new recommendation types to the API and a new “dismissed” field.
    • Five new recommendation types are available in the API:
      • Bidding with Maximize conversions
      • Bidding with Enhanced CPC
      • Bidding with Maximize clicks
      • Expand your reach with Google Search partners
      • Use optimized ad rotation
    • Added “Dismissed” field to search, retrieve, or apply dismissed recommendations.
  • Shopping. Smart Shopping Campaigns combine standard Shopping and Display remarketing campaigns, and use automated bidding and ad placement to promote your products and business across networks.
  • This release of Google Ads API supports the creation of Smart Shopping Campaigns, which can be used with Maximize Conversion Value bidding strategies. Product offers can be subdivided into groups using the ListingGroupInfo criterion, which currently supports the following dimension types: Product Condition, Product Type, Listing Brand, Custom Attribute (L0-4).
  • Access to Smart Shopping campaigns is currently only available to whitelisted developers.
  • Python client library. We’ve now also released a Python client library. In the v0 and v0_2 releases, we released Java, C#, Ruby, and PHP client libraries. 
To get started with the API, our team has put together these resources:

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

Nadine Sundquist, on behalf of the Google Ads API Team

Announcing v3.2 of the DCM/DFA Reporting and Trafficking API


Today we're releasing v3.2 of the DCM/DFA Reporting and Trafficking API. Highlights of this release include:
Details of these and all other changes are covered in our release notes.

Deprecation and sunset reminder
In accordance with our deprecation schedule, this release marks the beginning of the deprecation period for v3.1, which will sunset on February 28, 2019. After this date, any requests made against v3.1 will begin returning errors.

As a final reminder, API version 2.8 will be sunset on August 31, 2018. To avoid an interruption in service, all users are required to migrate to a newer version before the sunset date.


Learn More
As with every new version of the DCM/DFA Reporting and Trafficking API, we encourage you to carefully review all changes in the release notes. For those of you looking to get going right away, updated client libraries are now available. If you're just starting out, the Get Started guide is a great reference to help you get up and running quickly.


Give it a try and let us know if you have any questions!


- Jonathon Imperiosi, DCM API Team

Announcing v201806 of the AdWords API

Today we’re announcing the release of AdWords API v201806. Here are the highlights:
  • Mutable ads. The new AdService allows you to edit ads in place and retain performance stats for ETA, DRA, Showcase ads, and responsive search ads. Check out the updated ads overview for details.
  • Responsive search ads (beta). This new ad format allows you to provide multiple headlines and descriptions in one creative. These assets are then combined into ads that can accommodate more content -- up to 3 headlines and 2 description lines -- and can improve performance. Responsive search ads are available to whitelisted users and in test accounts.
  • Responsive display ads (beta). This new type of display ad is available to whitelisted users and will be fully supported when it launches later this summer. Responsive display ads allow you to provide multiple text and image assets in one creative, and then AdWords combines and tests these assets to show the most relevant ads to your customers across the Google Display Network.
  • Smart display campaigns (beta). The AdWords API now supports creation and management of Smart display campaigns by whitelisted users, and will also be fully supported when it launches later this summer. The new accompanying guide covers all the details.
  • Offline conversion adjustments. The new OfflineConversionAdjustmentFeedService allows you to apply conversion adjustments using the AdWords API. The updated conversions guide has more details to help you get started with this new service.
  • Dynamic Search Ads criteria. WebpageConditions for Webpage criteria now support parameters based on an exact match of URLs.
  • New promotion extension occasions. Several new occasions were added for promotion extensions.
If you’re using v201710 of the AdWords API, please note that it will be sunset on July 25, 2018. We encourage you to skip v201802 and migrate straight to v201806. If you're using v201802, be aware it's now marked deprecated.

As with every new version of the AdWords API, please carefully review all changes in the release notes and the v201806 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.
- Josh Radcliff on behalf of the AdWords API Team

Announcing v0_1 of the Google Ads API

Today we’re announcing the beta release of Google Ads API v0_1. With minor updates like this one, you’ll continue to point to v0 as your endpoint, but you will want to update your client libraries. Here are the highlights:
  • Recommendations. Recommendations provide customized suggestions to help increase your campaigns' performance. This is the first time Recommendations is being brought to you through an API.
    • The four Recommendations we currently provide in the API are:
      • Bid more efficiently with target CPA
      • Add new keywords
      • Add ad suggestions
      • Fix campaigns that are limited by budget
    • Search for Recommendations using GoogleAdsService.Search, which supports filtering and selecting with ad group, campaign, and campaign budget for supported Recommendations.
    • Retrieve and apply Recommendations using RecommendationService.
  • PHP client library. In the v0 release, we released Java, C#, and Ruby client libraries. We’re releasing a PHP client library shortly after this version.
To get started with the API, our team has put together these resources: If you have any questions or need help, please contact us via the forum.
Nadine Sundquist, on behalf of the AdWords API Team

Announcing v3.1 of the DCM/DFA Reporting and Trafficking API

Today we're releasing v3.1 of the DCM/DFA Reporting and Trafficking API. Highlights of this release include:



Details of these and all other changes are covered in our release notes.

Deprecation and sunset reminder

In accordance with our deprecation schedule, this release marks the beginning of the deprecation period for v3.0, which will sunset on November 30, 2018. After this date, any requests made against v3.0 will begin returning errors.

As a reminder, API version 2.8 will be sunset on August 31, 2018. To avoid an interruption in service, all users are required to migrate to a newer version before the sunset date.

Learn More

As with every new version of the DCM/DFA Reporting and Trafficking API, we encourage you to carefully review all changes in the release notes. For those of you looking to get going right away, updated client libraries are now available. If you're just starting out, the Get Started guide is a great reference to help you get up and running quickly.

Give it a try and let us know if you have any questions!


- Jonathon Imperiosi, DCM API Team

Join the beta for the new AdWords API

Today we’re announcing the beta release of Google Ads API v0. The Google Ads API is the next generation of our current AdWords API, and it can be accessed via gRPC and JSON REST from a variety of client environments. As this API gradually rolls out, it will reach full parity with the current API.

What’s in the beta?
For the beta, you have the ability to manage search campaigns from creation all the way to reporting. By getting in early, you’ll get to:
  • Integrate newer technologies like gRPC or JSON REST into your product sooner.
  • Provide feedback when requested on the beta in order to influence the new Google Ads API.
  • Try out features such as the new Google Ads Query Language that gives more querying flexibility.
  • Start using the API to query metrics with the accompanying resources and then mutate those resources. For example, you can query all the keywords that have zero impressions and then immediately mutate those keywords to change their bids.
The functionality for Google Ads API v0 includes:
  • Creating, updating, and removing search campaigns.
  • Managing campaign budgets.
  • Managing ad groups in search campaigns.
  • Managing 5 different kinds of ads in search campaigns.
  • Setting shared and portfolio bidding strategies.
  • Setting up targeting using keywords in search campaigns.
  • Retrieving detailed advertiser information.
  • Reporting on various metrics for search campaigns.
Please see the release notes for more details.

How do I join the beta?
Anyone with an existing developer token can apply to join this beta by submitting an application. People who join the beta are expected to submit feedback in order to help us make improvements.

Once you are approved, start with the Get Started guide, and get familiar with our other guides. We’ve also created client libraries for Java, C#, and Ruby with examples to help get you started.

Where do I learn more?
To get started with the API, our team has put together resources: If you have any questions or need help, please contact us via the forum.
Nadine Sundquist, on behalf of the AdWords API Team

Structured Data Files v4 now available in the DoubleClick Bid Manager API


Today we're announcing the general availability of Structured Data Files (SDF) v4 in the DoubleClick Bid Manager API. Highlights of this release include support for:
  • Bid Multipliers
  • TrueView bumper ads
  • Enhanced YouTube tracking
  • Exchange Targeting settings inheritance

Details of these features and all other changes can be found in the release notes.

All SDF users are encouraged to begin requesting v4 files to take advantage of these new features. To do so, simply pass 4 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.

- Jonathon Imperiosi, DBM API Team

Announcing v201802 of the AdWords API

Today we’re announcing the release of AdWords API v201802. Here are the highlights: In addition to the above changes for v201802, the following improvements were made in all versions of the AdWords API:
  • Click types for Shopping Showcase ads. The list of click types in reports now includes values for Showcase Shopping ads interactions.
  • Member uploads by mobile ID/IDFA and address. All users of the AdWords API can now upload mobile ID/IDFA and address member data to CrmBasedUserList. Previously, these features were only available to whitelisted users.
If you’re using v201705 or v201708 of the AdWords API, please note that they will be sunset on March 28, 2018. We strongly encourage you to skip v201705, v201708, and v201710 and migrate directly to v201802. If you're using v201710, be aware it's now marked deprecated and will be sunset on July 11, 2018.

As with every new version of the AdWords API, please carefully review all changes in the release notes and the v201802 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.
- Josh Radcliff on behalf of the AdWords API Team