Author Archives: Google Ads Developer Advisor

AdWords click measurement improvements and migration

Earlier this month, the following improvements were made available to all users:
  • Setting finalUrlSuffix at the customer, campaign, ad group, ad, and extension level in all AdWords accounts. Previously, this feature was only available in test accounts.
  • Specifying up to eight custom parameters. Previously, the maximum number of custom parameters was three.
As announced earlier this year, starting October 30, 2018, parallel tracking will be required for all AdWords accounts. With the above features in place, the AdWords API now supports all the features needed to migrate your accounts to parallel tracking, so we encourage you to get started on the migration as soon as possible. The detailed AdWords API guide and accompanying implementation checklist will walk you through the required changes.

If you have questions or need help with the migration, please email us at ads-clicktracking-support@google.com.

DFP API is becoming Google Ad Manager API



With DoubleClick for Publishers becoming Google Ad Manager, the API will be undergoing changes to follow suit. Over the next month, there will be changes to our documentation and client libraries, but no API entities are changing yet.

Documentation

In late July, references to “DFP” will become “Google Ad Manager” or just “Ad Manager”. Also, the documentation URL will change from https://developers.google.com/doubleclick-publishers/ to https://developers.google.com/ad-manager/.

We will support redirects to all documentation pages. For example, if you have a bookmark for the ReportService, you don’t need to do anything for this bookmark to continue working.

Client Libraries

Each of our client libraries will be updated to remove references to DFP in the v201808 release, which is currently scheduled for August 14, 2018. For example, in the Java client library, the DfpServices class will be renamed to AdManagerServices.

Each client library will have its own guidelines for what needs to be updated. In the announcement blog post for v201808 we will link to these guides. Keep in mind that you’ll only need to refactor your code once upgrading to v201808 and beyond, so using the DFP names will still be supported by some versions of the client library until August, 2019.


As always, if you have any questions or suggestions, feel free to reach out to us on our forum.

Sunset of DFP API v201708

On Friday, August 31, 2018, in accordance with the deprecation schedule, v201708 of the DFP API will be sunset. At that time, any requests made to this version will return errors.

If you’re still using this version, now’s the time to upgrade to the latest release and take advantage of fluid AdUnit sizes, Dynamic Ad Insertion options for video ads, and new reporting functionality.

In order to upgrade, check the release notes to identify any breaking changes, grab the latest version of your client library, and update your code.

Significant changes include:

This is not an exhaustive list, so be sure to check the release notes for a list of all changes. As always, don't hesitate to reach out to us with any questions. To be notified of future deprecations and sunsets, join the DFP API Sunset Announcements group and adjust your notification settings.

AdWords API v201710 sunset reminder

AdWords API v201710 will be sunset on July 25, 2018. After this date, all v201710 API requests will begin to fail. We recommend that you skip v201802 and migrate directly to v201806. Please migrate prior to July 25, 2018 to ensure your API access is unaffected.

We've prepared various resources to help you with the migration: As always, if you have any questions about this migration, please contact us via the forum.

Consent SDK removes limit of 12 ad technology providers

To support publishers in meeting their duties under the Google EU User Consent Policy, Google offers a Consent SDK. The Consent SDK is an open-source library that provides utility functions for collecting consent from your users. The full source code is available on GitHub.

With the latest release of the Consent SDK (v1.0.5 for Android or v1.0.2 for iOS), the Google-rendered consent form is now compatible with any number of ad technology partners, including the full list of commonly used partners. Apps that update to the latest version of the Consent SDK can start taking advantage of this additional flexibility immediately.

You can find additional documentation for the Consent SDK on the Google Mobile Ads Android and iOS developer docs. If you have any questions about implementing the Consent SDKs, you can reach us on our forum.

A new guide for integrating Google Shopping ads using Google APIs

Good news for developers planning to integrate Google Shopping ads! We have just released a brand new guide explaining how to automate the delivery of Google Shopping on behalf of merchants using Google APIs.

The Shopping Automation Guide covers the steps required to set up new merchants using a combination of the Content API for Shopping and AdWords API. It describes how you can fully automate certain tasks that would otherwise be performed manually using the Merchant Center and AdWords websites.

The guide is for developers interested in feed management, campaign management, or full automation workflow that includes both. The workflows provide detailed explanations of how the different APIs can be used for each stage of the user journey. You can follow the workflow step by step or navigate straight to the article you require using the side panel.

Head over to the developer pages to get started! If you have any questions or need help, please contact us on the relevant forums: If you have any feedback on the guide, please use the “Send Feedback” link at the top right of each page.

We also appreciate any feedback on your experience using the guide. If you would like to share it, please complete this survey.

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.

Learn with us: Google Ads API webinars

Thank you to the 100+ viewers from 30 different countries who joined our Google Ads API webinars on Tuesday, May 22! We had some great questions during the Q&A and hope it was helpful for everyone who attended.

For those who couldn’t attend the live events, and for anyone who would like a copy of the presentation, both the slides and a video recording of the event are available below. You can find out more about the Google Ads API in our documentation. Please contact us via the forum if you have any questions.

Limit line item serving with userConsentEligibility in the DFP API

Using v201805 of the DFP API, publishers can now limit which line items are shown to users in the European Economic Area (EEA) by setting the LineItem.userConsentEligibility field. (Note: this field only takes effect if you have elected to “Limit line items” on the “EU user consent” page.) The userConsentEligibility field can be set to one of three values:

  • NONE (default) - Don’t serve for any EEA ad requests
  • CONSENTED_ONLY - Don’t serve for non-personalized ad requests
  • CONSENTED_OR_NPA - Don’t limit serving

As always, if you have any questions or suggestions, feel free to reach out to us on our forum.