Posted:

We’re pleased to announce the newest DFA Reporting API release, version 1.3. This version adds an often requested feature: the ability to retrieve the dimensions and metrics that are available for selection.

Compatible Fields

DoubleClick for Advertisers allows you to restrict the visibility of certain metrics and dimensions for individual users based on the permissions granted to the user role and filters applied to the user profile. Additionally, certain dimensions and/or metrics cannot be used in combination with one another. For these reasons it can be difficult to determine which metrics and dimensions are available. The new reports.compatibleFields resource allows you to programmatically tackle this problem, returning a listing of fields available to the current user based on the report being created.

Additional details are available in our developer documentation release notes. We’re always available to answer your questions on our forum, or you can reach out to us on our Google+ Page.

Posted:

We’re pleased to announce the newest DFA Reporting API release, version 1.2. This version’s main additions include paid search dimensions and a way to view all reports and files in your account, not just those that you own.

Paid Search

Paid search dimensions have been added to the API with this release. We also added support for these new dimensions to version 1.1, but only version 1.2 contains the new matchType field in the DimensionValue resource allowing you to filter paid search dimensions by one of the following:

  • EXACT
  • CONTAINS
  • BEGINS_WITH
  • WILDCARD_EXPRESSION

Report Sharing

We have added the ability to list all reports and files in your DFA account (in addition to those owned by you). You may also optionally list just those files that have been shared with you using the Files resource. You can find this option in the scope parameter in the input to the respective list methods.

Refer to the release notes in our developer documentation for more details. We’re always available to answer your questions on our forum, or you can reach out to us on our Google+ Page.

Posted:

One of the more exciting features in the DFA Reporting API is synchronous reporting - the ability to run smaller reports right when you request them. Synchronous reporting is great for fetching metrics when you need them quickly, such as in a GUI environment. To help you understand how to take advantage of this feature, we’ve added a synchronous reporting guide.

If you have any questions on this topic, please bring them to our forum. We’d be happy to answer them for you and add them to our guide.

Posted:

A new release of the DFA Reporting API, version 1.1, extends the ability of your applications to tap into the power and flexibility offered by our new reporting platform.

Feature Parity with ReportBuilder

Using the DFA Reporting API, you can now take advantage of all of the report types in ReportBuilder:

  • STANDARD
  • REACH
  • PATH_TO_CONVERSION
  • FLOODLIGHT

The API contains support for CROSS_DIMENSION_REACH reports, but the backend currently does not. Support for these reports will be turned on at a later date and will be accessible through version 1.1.

Additionally, you may now set a list of recipients to be emailed when a scheduled report runs. We have paved the way for downloading reports in different formats, though currently CSV is the only available option.

A Few Backwards Incompatible Changes

We have taken the opportunity to make a few backwards incompatible changes to the API. It will not be standard procedure to make changes like this in minor version releases, but since the API is still relatively new, locking down the final structure of our API now will reduce changes later and ease development. These changes include:

  • Report files and report criteria now share the same dateRange kind.
  • The urls object in the File resource has changed to support report formats other than CSV.
  • A customRichMediaEvents and an activities kind have been added, both of which are reused between different report types.

Our updated release notes page has a full list of changes for your reference. As always, we highly value your feedback and questions. Please join us on our forum whenever you’d like to reach us.

Posted:
We have some exciting changes and important announcements for the DoubleClick for Advertisers community as we begin to improve our overall approach to APIs for the product. This is just the first of many improvements that will come over the next several quarters.

DFA API v1.19 - Security at the Forefront

The newest release of the DFA API, v1.19, is now available. This release brings two major security enhancements. SSL encryption, a feature we originally slated for v1.18, is now mandatory on all API requests. This is in line with a Google-wide effort to leverage HTTPS connections for greater security.

Secondly, this release of the DFA API supports OAuth2 authentication in addition to the API passwords tied to your DFA user profiles. We recommend using this new approach. In time, we plan to phase out the profile-specific passwords in favor of making OAuth2 the single, standard way to authenticate against our API. Please see our documentation for more information on how OAuth2 is integrated with the DFA API and reference our client libraries, all of which will soon be updated with examples of using OAuth2 instead of an API password.

Our release notes page has been updated with complete notes on v1.19.

DFA Reporting Gets an API

Less than a year ago, we announced the availability of the new DFA Reporting system. This new system offers the power, flexibility and data access required to keep up with today’s always-connected, multi-device consumer. Compared to Report Central, data in the new DFA Reporting system is fresher, can be segmented by the hour, and includes a host of new features including geographic reporting for all ads. Today, we are pleased to launch an API for the new DFA Reporting system.

The DFA Reporting API is a language-neutral REST API that offers programmatic access to the same reports as can be generated through the DFA Reporting user interface. Along with improved speed and performance, the new API will allow you to create, edit, and schedule Standard reports. We will continue to launch additional features to the new DFA Reporting API over the next few months. Support for this API has been added to the Google APIs Client Libraries. The Java library currently has the most complete example set.

Version Enforcement on the Java DART API

The Java DART API, long the bread and butter of integrating with our ReportCentral service, has a large range of versions currently in use. We are going to begin enforcing a minimum version requirement on this API on November 3rd, 2012. At this time, clients will be must be using one of the newest versions of the Java DART API -- version 13.4, version 13.6, or version 13.8. We recommend you take the opportunity to consider the new DFA Reporting API. Come enjoy the benefits of its newer technology.

Changes to Our Deprecation Policy

This past April, Google announced changes to the deprecation policies surrounding our APIs to help keep our products moving and innovating quickly. DFA is joining this overall Google effort. As such, as of November 3rd, 2012, DFA will remove the depreciation policy for all of our APIs.

The removal of the deprecation policy doesn't mean we have changed the way we think about our APIs. As signaled by the launch of the new DFA Reporting API, we are more committed than ever to offering stable and relevant APIs to our developer community. We will continue to work very hard to communicate any changes to our APIs well in advance, regardless of the APIs' deprecation policy. Our commitment to our clients and to the API remains unchanged.

Until November 3,2012 we will continue the deprecation policy we currently have in place. With the the release of v1.19, version v1.17 is now deprecated. Version v1.17 will continue to be supported until September 8th, 2012, when it will be entirely removed from service, as previously announced. Meanwhile, version v1.18 will be deprecated in November and sunset in early December, 2012.

As always, we highly value your feedback and questions. Please join us on our forumwhenever you’d like to reach us.