We’re pleased to announce that version 1.2 of the Ad Exchange Buyer REST API is now available. This release provides one of the most requested features— detailed creative disapproval reasons. Additionally, it also provides a new field for creatives that can be used to identify the agency providing the creative and a new field for direct deals that can be used to determine whether a deal originated from a private auction. You may view a more specific listing of the changes implemented in v1.2 in our release notes.

Detailed Creative Disapproval Reasons

The Creatives resource now has an improved disapprovalReasons field. Previously, this field provided a list of strings that described the reason for disapproval in a broad context that may have been somewhat ambiguous. Each element of disapprovalReasons now provides two additional fields— reason and details. One can use disapprovalReasons.reason in order to access a categorized reason for disapproval, or use disapprovalReasons.details to retrieve a list of strings describing the disapproval reason in detail.

Identify Where Your Ads Came From

Publishers now have greater control over their inventory— e.g. with the new inventory management system, they may set rules that could offer special pricing or limit access to a specific set of creative agencies. With the new agencyId field, you can identify the creative agency that produced the ad with one of the IDs listed in agencies.txt, and consequently gain access to publisher inventory that utilizes these features.

Determine Your Eligibility for Private Auction Deals

We’ve given publishers the ability to create private auction deals, which you can read more about in our help center. You can now determine whether you have a fixed price deal or private auction deal by checking the private_exchange_min_cpm field— if it is set instead of the fixed_cpm field, you have a private auction deal. When you bid on ad slots from the publisher offering this deal, you are expected to offer at least the amount provided by this field.

You can read more about the new features in the Buyer REST v1.2 documentation. As always, we welcome you to join us on our forum to discuss and ask questions about these changes. To keep informed on all of our ads-related technologies, follow our Google Ads Developers Google+ page.

 - 

release notes.

Detailed Creative Disapproval Reasons

The Creatives resource now has an improved disapprovalReasons field. Previously, this field provided a list of strings that described the reason for disapproval in a broad context that may have been somewhat ambiguous. Each element of disapprovalReasons now provides two additional fields— reason and details. One can use disapprovalReasons.reason in order to access a categorized reason for disapproval, or use disapprovalReasons.details to retrieve a list of strings describing the disapproval reason in detail.

Identify Where Your Ads Came From

Publishers now have greater control over their inventory— e.g. with the new inventory management system, they may set rules that could offer special pricing or limit access to a specific set of creative agencies. With the new agencyId field, you can identify the creative agency that produced the ad with one of the IDs listed in agencies.txt, and consequently gain access to publisher inventory that utilizes these features.

Determine Your Eligibility for Private Auction Deals

We’ve given publishers the ability to create private auction deals, which you can read more about in our help center. You can now determine whether you have a fixed price deal or private auction deal by checking the private_exchange_min_cpm field— if it is set instead of the fixed_cpm field, you have a private auction deal. When you bid on ad slots from the publisher offering this deal, you are expected to offer at least the amount provided by this field.

You can read more about the new features in the Buyer REST v1.2 documentation. As always, we welcome you to join us on our forum to discuss and ask questions about these changes. To keep informed on all of our ads-related technologies, follow our Google Ads Developers Google+ page.

 - , Ad Exchange Buyer Team

Labels: ,


Find setup instructions in the AdMob Help Center here under the article titled ‘Allocate traffic by eCPM’.

Posted by: Vishay Nihalani, Product Manager, Google
Labels:


Reports
With these changes, comes a new report, the PLACEMENT_PERFORMANCE_REPORT which will contain all the information about manual placements. We strongly recommend using this report for queries regarding placement performance, moving forward.

There will also be changes to the AUTOMATIC_PLACEMENTS_PERFORMANCE_REPORT and URL_PERFORMANCE_REPORT to better match the AdWords website.


 - , AdWords API Team
Labels: , ,


Calls made using this version will not longer work after March 25th. It is therefore critical that you migrate to a newer version for your applications to run without interruption.

We encourage you to use the following resources for a successful migration:

 - , AdWords API Team

Labels: , ,

Labels: ,

Labels: , ,

Labels: , , ,

Labels: , ,

Labels: ,


 - , AdWords Scripts Team
Labels:

Labels: ,

Labels: , ,

Labels: , ,

Labels: ,

Housekeeping and deprecation

 Starting in v201302, we are shifting many of the disjointed creative asset properties to a single manageable object - CreativeAsset. The first type of creatives to get this treatment is image creative. The 4 fields that previously represented the image asset have been replaced by a single primaryImageAsset field. With the new field, you’ll always know where to find the URL to preview the asset, instead of having to programmatically determine the name of the property.

Last but not least, to make room for all the new features, versions v201203, v201204, and v201206 are now deprecated. On June 1st, we’ll be removing them from our online documentation and client libraries. If you are using one of these deprecated versions, now would be great time to update to take advantage of all the new features.

Be sure to also follow us on our Ads Developer Google+ page. We'll be publishing some great tips on using the API there soon. If you have any suggestions or questions about the new version, but sure to visit our forum.

 - , DFP API Team
Labels: ,