Tag Archives: ad_exchange_seller

Ad Exchange Seller REST API Deprecation Reminder

The Ad Exchange Seller REST API is deprecated. Existing API clients should migrate to the DoubleClick for Publishers API before July 26, 2018. After this date, all requests to the Ad Exchange Seller REST API will return errors.

This migration guide provides instructions for getting started, as well as a mapping of each Ad Exchange reporting metric to its equivalent in the DFP API.

For more details about reporting in the DFP API, see the reporting guide.

For general assistance with the DFP API or your migration, reach out on our developer forum.

 - , DFP API Team

Ad Exchange Seller REST API Deprecation

The Ad Exchange Seller REST API is being deprecated as of October 26, 2017. No new API clients will be supported after this date. Existing API clients will need to migrate to the DoubleClick for Publishers API before July 26, 2018. After this date, all requests to the Ad Exchange Seller REST API will return errors.

What action is required


Current Ad Exchange Seller REST API users will need to migrate to the DoubleClick for Publishers API before July 26, 2018. This migration guide provides a mapping of each Ad Exchange reporting metric to its equivalent in the DFP API.

For more details about reporting in the DFP API, see the reporting guide.
For general assistance with the DFP API or your migration, reach out on our developer forum.

Why this is happening


As a part of our effort to provide a unified tool to manage your ad business and monetize your inventory, the DoubleClick for Publishers API now supports all of the features of the Ad Exchange Seller REST API. The DFP API is more robust and has more frequent updates.

What isn't changing


Users will not need to create new accounts. All Ad Exchange Seller users already have a DoubleClick for Publishers account.

No data is changing. The only change is how you programmatically access that data.

 - , DFP API Team

DoubleClick Ad Exchange Seller API new metrics and dimensions

We are delighted to announce the introduction of additional Metrics and Dimensions which are now available through the reports resource; the API now returns most of the fields that the UI Query tool makes available.

The Metrics and Dimensions reference page now includes the UI field names to help make conversions simpler.

New Dimensions New Metrics
AD_LOCATION ACTIVE_VIEW_ELIGIBLE_COUNT
ADVERTISER_DOMAIN ACTIVE_VIEW_MEASURABLE_COUNT
AGENCY_NAME ACTIVE_VIEW_MEASURABLE_RATIO
BRAND_NAME ACTIVE_VIEW_VIEWABLE_COUNT
CREATIVE_SIZE ACTIVE_VIEW_VIEWABLE_RATIO
DEAL_ID ACTIVE_VIEW_VIEWABLE_TIME
DEAL_NAME AD_IMPRESSIONS
DFP_AD_UNIT_ID AD_IMPRESSIONS_RPM
DFP_AD_UNITS DEALS_AD_REQUESTS
DFP_REQUEST_SOURCE DEALS_BID_RESPONSES
INVENTORY_OWNERSHIP DEALS_MATCH_RATE
INVENTORY_PARTNER_NAME DEALS_MATCHED_REQUESTS
MOBILE_APP_NAME LIFT_RATE
MOBILE_CARRIER_NAME VIDEO_AD_ABANDONMENT_RATIO
MOBILE_DEVICE_NAME VIDEO_AD_DROPOFF_RATIO
MOBILE_INVENTORY_TYPE VIDEO_AD_QUARTILE_ONE
MOBILE_OS_VERSION VIDEO_AD_QUARTILE_THREE
MOBILE_USER_BANDWIDTH VIDEO_AD_SKIPPABLE_SKIP_RATIO
VIDEO_AD_DURATION VIDEO_AD_SKIPPABLE_VIEWS
VIDEO_AD_DURATION_RAW VIDEO_AD_SKIPPABLE_VTR
VIDEO_AD_FORMAT

-- Dean Lukies, Ad Exchange Seller API Team

DoubleClick Ad Exchange Seller API sunsets

Versions 1 and 1.1 of the DoubleClick Ad Exchange Seller API are marked as deprecated and will be sunset on the 14th of October 2016, after which any calls to these versions will return an error.

All users must migrate to Version 2.0 of the API by this date to avoid an interruption in service.

The deprecated resources preferredDeals and reports.saved will be sunset for all API versions on the 12th of July, after which any calls to these resources will return an error.

This will NOT impact reports.generate which most of you use to generate reports.

-- Dean Lukies, Ad Exchange Seller API Team

DoubleClick Ad Exchange Seller REST API Report changes

On November 17th, 2015, we'll be updating the Ad Exchange Seller REST API to make it consistent with the user interface. Specifically, we'll remove the ability to download saved reports or retrieve the dimensions we retired in April.

Requests made after this date for these dimensions will result in that dimension being ignored and requests for saved reports will result in an error.

As a reminder, the dimensions we retired in April are:

  • AD_FORMAT_CODE
  • AD_UNIT_ID
  • AD_UNIT_CODE
  • DSP_ID
  • EXPANSION_TYPE_CODE
  • PLATFORM_TYPE_CODE

For a full list of available dimensions, please see the AdX Seller REST API documentation.

Follow our Google+ page for other announcements and updates.

-- Dean Lukies, Ads Developer Relations

DoubleClick Ad Exchange Seller REST API Report changes

The ability to generate saved reports using the API will be retired on April 6th, 2015, along with six dimensions due to low usage. After the sunset, any API calls to Reports.Saved or requests for these dimensions will result an error.

After the introduction of the Query Tool to the UI last year, the ability to create and edit saved reports in the UI was removed--leading to the sunsetting of Reports.Saved in the API.

The dimensions that will be removed are
  • AD_FORMAT_CODE
  • AD_UNIT_EXTERNAL_ID*
  • AD_UNIT_CODE*
  • DSP_BUYER_NETWORK_ENCRYPTED_ID
  • EXPANSION_TYPE_CODE
  • PLATFORM_TYPE_CODE
[*] these dimensions haven't been relevant for 6 months due to the move to Enhanced Inventory Controls and only are retained in the UI for historic purposes.

To find out if you will be affected, search your code for any of the strings above and remove them; they will be associated with a call to Reports.Generate.

For a full list of available dimensions please see the AdX Seller REST API documentation.

-- Dean Lukies, Ads Developer Relations

DoubleClick Ad Exchange Seller REST API v2.0

Today we launch the v2.0 release of the DoubleClick Ad Exchange Seller REST API. This release adds support for associating a single user to more than one account.

If your user ID is associated with only one account, you can continue to use v1.1 of the API as you have previously, although we recommend you always use v2.0 of the API. If your user ID is associated with more than one account, you must use the v2.0 API and supply the accountId of the appropriate customer account with each request.

For example, resource requests in v1.1 like this:
https://www.googleapis.com/adexchangeseller/v1.1/{resourceType}/{resourceId}

Will become this in v2.0:
https://www.googleapis.com/adexchangeseller/v2.0/accounts/{accountId}/{resourceType}/{resourceId}

Follow our Google+ page for other announcements and updates.

Dean Lukies, Ads Developer Relations