The newest version of the DFA API is now available: v1.18. This release adds support for In-Stream Video creatives and makes some assorted improvements, including better error messages and trimming out some unused fields. This post reflects just some of the changes in the release. Our updated release notes page gives you a more in-depth breakdown of what has changed since the previous version. In-Stream Video Creatives New to v1.18,

Last year we exposed advanced location targeting settings in the AdWords API, using the GeoTargetTypeSetting object. Based on customer feedback we are now rolling out a series of changes to improve the power and clarity of this feature. The full details of these changes can be found on the Inside AdWords blog , but some highlights are: The advanced location targeting settings now apply to Display Network traffic in addition to Google Search and the Search Network traffic.

Recent visitors to any of the Ads API documentation pages will have noticed their shiny new appearance and a message to let you know the docs have moved to a new platform: This move is much more than a skin-deep makeover. As we've blogged before, the new Google Developers platform is so named to reflect our focus on you, and not just on the tools we provide.

If you are an advanced AdSense Management API user, your application may have run into one of the several different limits we have in place. We've created a new documentation page to keep track of system limits, but here's a small description of what they are and what you can do to avoid them. API Courtesy Limit This limit refers to the number of requests your project can make via the API in a single day, across all of your users or AdSense accounts. This is set to 10,

Google+ Office Hour Hangouts continue to be a hit across all of the Ads products so we're announcing that we've scheduled new events for the spring season. You can view the newly scheduled hangouts on the Google Developers events page . Please RSVP by clicking the "I'll be there" button if you plan on attending.

During Chart Tools Week , we showed you how to create a basic dashboard for AdSense reporting using the AdSense Management API and Google Chart Tools . In this new two-part series, we'll examine more advanced charting techniques that will improve the look and feel of our chart as well as enable user interactivity. We'll also show you how to use the Google Closure Library to ease some of the data manipulation tasks when writing a JavaScript application.

Last week we sunset all versions of the AdWords API prior to v201109. If you have not yet migrated to v201109, you will now receive errors when making calls using previous versions. For users still working on the transition from v13 to AdHoc reports, we want to remind you of resources available to help you out: The report migration guide provides a side-by-side mapping between the fields available in the v13 ReportService and those available in v201109.

In the newest version of the API, v201201 , we've added a feature to streamline the syncing of information in your DFP network to another system. Previously, this was possible but required repeatedly downloading the same objects to see if they had been modified. Now, a new PQL field exists, lastModifiedDateTime , which can be used to return objects based on their modification dates.

Unlike reports in previous AdWords API versions, v201109 AdHoc reports are downloaded by POSTing XML to a URL rather than defining them using a SOAP service; therefore they have no WSDL document to describe the XML payload. To ensure that your ReportDefinition XML is valid when sending it to the API, we are now publishing an XML Schema Definition )XSD(. This XSD is tied to the versioned Report Download endpoint, allowing us to make incremental changes to reporting as needed.

Editor's note: We'd like to share with you this post from John Park about the growing DFP API ecosystem and a few success stories from our partner directory . - Adam Rogal, Ads Developer Relations Team With thousands of publishers using the DFP and DFP Small Business ad serving platforms, we know first-hand that no two publishers are identical. Publishers may use in-house billing systems, have unique approval workflows,

On February 29, 2012, we will be sunsetting the following versions and services: AdWords API versions v13, v200909, v201003, v201008, v201101 AdWords API version v13 AccountService will only be available on a whitelist basis. Calls made using these versions will return errors after February 29th. It is therefore critical that you migrate to AdWords API v201109 if you would like your applications to run without interruption.

Editor's note: As many of you are planning your 2012 advertisement strategy, we'd like to share with you this post from Karim Temsamani. It's a look back on 2011 and provides a great perspective on how mobile really took a step forward in the advertising ecosystem. - Stan Grinberg, Ads Developer Relations Team Mobile turned a corner this year. As smartphones and tablets became a part of our everyday lives,

Last month, we announced the ability to create both custom and template creatives using the DFP API. Today we'll show you can use these premium-only features to create richer creatives with custom HTML. Custom or template The difference between custom and template creatives is that custom creatives have their HTML snippet set within them, while template creatives are instantiated from system or user defined HTML snippets.

It's Chart Tools week here on the blog, and so we'll be showing you in a 4-part series how to easily generate charts for your AdSense reporting using Google Chart Tools . In today's second post we'll examine how to generate another type of chart: a column chart. Column chart The second item required by our CEO is a column chart . The column chart will show the number of page views, ad requests,

It's Monday morning, and you're sitting in front of your computer, ready for a relaxed start of the week. But wait! You've received an email from your CEO. He wants you to add AdSense reporting to his dashboard, and he wants to see the following: a line chart showing the number of ad requests for the current year, broken down by month a column chart showing the number of page views, ad requests, matched ad requests and individual ad impressions for the current year,

In addition to retrieving performance statistics, AdWords API developers often use the reporting system to get structural information about an account. These reports can be used to quickly synchronize a local database without having to make a series of expensive get)( calls to the API. Unlike v13 which had a dedicated Structure Report for this purpose,

The v201111 version of the DoubleClick for Publishers )DFP( API introduces SuggestedAdUnitService which lets you get and approve those ad units that have tags on your web pages, but no corresponding ad units in DFP. By default, only ad tags that have 10 or more requests will be returned as suggested ad units . They can be approved using performSuggestedAdUnitAction , after which they become ad units and you can manipulate them using InventoryService . To use this service,

Last month we provided a new channel for developers to reach us: AdWords API office hours on Google+ Hangouts. Based on positive feedback from participants, we've decided to schedule additional Hangouts. In this next round we are including one more time slot for the European region. Please join us via Google+ Hangouts during the following hours: U.S. session: Friday, 16th Dec, 1PM EST / 10AM PST; Europe session: Friday, 16th Dec, 11AM London / 12 PM Frankfurt / 3PM Moscow.

We're very pleased to announce the release of AdWhirl v3.1.1 for both Android and iOS platforms. This update heralds support for the Nexage ad network and includes refreshed adapters for Millennial Media , InMobi , and AdMob ensuring support for their latest SDK versions. Additionally, we've taken the opportunity to fix several bugs,

As part of routine upgrades to our infrastructure to improve performance and reliability and along with the announced sunsets scheduled for February 29th, we are planning to change our SSL certificates to use wildcards in the common name )CN(. Our certificates will therefore be configured as CN *.google.com instead of adwords.google.com. In most cases we foresee no changes required on your side,