Tag Archives: release

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

Today we're releasing v3.3 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.2, which will sunset on August 31, 2019. After this date, any requests made against v3.2 will begin returning errors.

As a final reminder, API version 3.1 will be sunset on February 28, 2019. 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!

Announcing v0_7 of the Google Ads API

Today we’re announcing the beta release of the Google Ads API v0_7. With this version, you’ll continue pointing to v0 as your endpoint; however, you'll need to update your client libraries. Here are the highlights:
  • Request Parameters. These parameters give you the ability to change how a request is processed.
    • Set validate_only to true as a request parameter to only validate the request, but not perform it. This was added to all services including GoogleAdsService.Mutate().
    • Set partial_failure to true as a mutate parameter to continue on failure and commit valid operations even if other operations in the same request failed.
  • Reporting. All segment fields are now in a segments, which means all queries must be updated to include segments. before the segment field name.
  • Manager accounts. We've added support for mutating your customer hierarchy with CustomerManagerLink and CustomerClientLink.
  • Client accounts. We’ve introduced fields to identify if a customer is a test account or a manager account. The conversion tracking settings of a customer are now available.
  • Ad formats. We’ve added support for managing ad parameters with the AdParameterService.
  • Audiences. The targeting setting in campaigns and ad groups is now available. We’ve added support for rule-based, logical, and basic user lists. You can now manage remarketing actions for a basic user list.
  • Criteria types. Creating criteria with CriterionType MOBILE_APP_CATEGORY, WEBPAGE, OPERATING_SYSTEM_VERSION, and APP_PAYMENT_MODEL is now possible.
To get started with the API, review these helpful resources: The updated client libraries and code examples will be published within the next 2 business days. If you have any questions or need help, please contact us via the forum.

Announcing v0_6 of the Google Ads API

Today we’re announcing the beta release of Google Ads API v0_6. This release brings you the features listed in Required Minimum Functionality (RMF). Now that the core functionality of this new API is available, you should get started planning, designing, and coding against it. With this version, you’ll continue pointing to v0 as your endpoint, however, you'll need to update your client libraries. Here are the highlights:
  • Manager account authentication: If you’re authenticating as a manager account, the manager account you want for authorization must be in the header as login-customer-id. You then set the customer you want to interact with in the request as usual. This tells the API the level of manager account hierarchy you want to authenticate with.
  • Mix mutate operations: Pass in multiple kinds of operations with GoogleAdsService.Mutate.
  • Hotel Ads: We extended the GoogleAdsService to enable users to query hotel performance metrics that were previously available in the Travel Partner API with the HotelPerformanceView. Supported performance metrics are cost, clicks, impressions, and average lead values. Some derived metrics are also precomputed: average position, average cost per click, average cost per thousand impressions, and click-through rate. These metrics can be segmented by:
    • Itinerary segments: check-in date, check-in day of week, booking window days, and date selection type
    • Hotel segments: hotel center ID, hotel ID, class, city, state, and country
    • Date segments: hour, date, day of week, week, month, quarter, and year
    • Others: campaign, ad group, ad network, and device
  • Feeds: Manage and retrieve feeds with AdGroupFeedService, CustomerFeedService, FeedService, CampaignFeedService, and FeedMappingService.
  • Account management:
    • We introduced CustomerClient, which provides the ability to get an expanded hierarchy of customer clients (both direct and indirect) for a given manager customer.
    • This release also supports the creation of new customer clients under a manager using the CustomerService.CreateCustomerClient method.
    • CustomerService now supports mutates.
  • Recommendations: Added the DismissRecommendation method to the RecommendationService, making it possible to dismiss the recommendations listed in our guide.
  • Ad formats: Gmail ads and image ads are now supported.
  • Search query reporting: The SearchTermView resource is now available, providing metrics aggregated at the search term level. SearchTermView provides functionality similar to the Search Query Performance Report of the AdWords API.
  • Audiences: Create audiences using UserListService.
  • Criteria types: You can now create criteria with CriterionType LANGUAGE, CARRIER, USER_LIST, USER_INTEREST and IP_BLOCK.
To get started with the API, review these helpful resources: The updated client libraries and code examples will be published within the next 2 business days. If you have any questions or need help, please contact us via the forum.

Announcing v0_5 of the Google Ads API

Today we’re announcing the beta release of Google Ads API v0_5. With this version, you’ll continue pointing to v0 as your endpoint, however, you'll need to update your client libraries. Here are the highlights:
  • Billing. Multiple services are available for managing billing.
    • BillingSetupService
      • Create a new billing setup
      • Cancel an approved billing setup that is scheduled to start in the future
      • Cancel a pending billing setup that is not yet approved
    • AccountBudgetService
      • View all approved account-level budgets, including budget adjustments
      • View currently pending account-level budget proposals (if any)
    • AccountBudgetProposalService
      • Create account-level budget proposal to update a budget or create a new budget
      • View all account-level budget proposals. All approved values and proposed budget values are visible. Approved values will be exposed as fields prefixed with approved_.
  • Conversion tracking. Conversion tracking lets you measure the performance of your advertising against your business goals.
    • Conversion actions - Set up and edit the settings associated with your conversion actions, including website tracking and call-conversion tracking
  • Shopping. The ProductGroupView resource provides Shopping campaign statistics aggregated at the product group level (also called listing group in the Google Ads API). Results always reflect the current set of product groups. An impression for a product will be attributed to all product groups that contain the product. ProductGroupView provides features equivalent to the Product Partition Report of AdWords API.
  • Location and Demographics. You can now create criteria with CriterionType AGE_RANGE, GENDER, INCOME_RANGE, PARENTAL_STATUS, PLACEMENT, PROXIMITY, TOPIC, YOUTUBE_CHANNEL, and YOUTUBE_VIDEO. The GeoTargetConstantService lets you input locations and receive suggested geos.
  • Account Management. CustomerService.ListAccessibleCustomers provides the capability to manage Google Ads accounts.
To get started with the API, review these helpful 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.

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.





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

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.

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.