Last year , we provided you with a bonus of 20% more AdWords API units at no additional cost. We're pleased to announce that we're bringing back our holiday bonus this year. Starting now and extending through January 15, 2012, you'll receive 20% more API units at no additional cost. Here are the details: Developers can purchase AdWords API units at the rate of 1250 for 0.25 USD, up from 1000 for 0.25 USD.

We would like to announce an important change to the process of downloading reports from the AdWords API that will affect all report downloads for tools built on API versions post v13. Currently, downloading reports costs no API units and has previously not required a developer token. To allow us to better monitor usage of reports, we will start requiring a developer token when downloading reports. Downloading reports will still cost zero API units.

We've just released a new My Client Center )MCC( feature called multiple links , which makes it easier for agencies, SEMs, AdWords API developers, other 3rd party providers and clients to work together while taking advantage of the benefits of the MCC structure . It enables up to five MCCs to link to and manage a single AdWords account as necessary. Multiple links also removes the distinction that Google currently has between UI and API and API-only links.

With the release of v201109 we are happy to announce that we now fully support OAuth 1.0 a in the AdWords API. OAuth is an open standard for authorization. Google uses this standard to allow applications to access a user's data )in this case AdWords( without requiring the user to give the application their Google username and password. In OAuth, an application starts by contacting Google with an OAuth request. Next,

A common question for the AdWords API Team is "when is the best time to run reports" )and for that matter, when to retrieve statistical data via the API(. The quick answer is: it depends on the type of data and report. Read on for details. The reporting system is very complex and statistical data is not available in realtime. For most reports and API services,

AdWords allows you to target your users based on their Location of Presence )LOP( or Area of Interest )AOI(. This feature is now available to developers through AdWords API v201101 and this blog post discusses how to use this new AdWords API feature. This blog post assumes that are familiar with how to set geographic targets on your campaign. If not, you can learn more here . For a refresher on where regionally targeted ads appear,

When introduced last year , AdWords Campaign Experiments )ACE( allowed for experimental changes to be applied to ad groups and criteria. To allow for even greater flexibility, in v201101 we've added the ability to apply experimental changes to individual ads as well. Just like other entities, experiment data can be added to an AdGroupAd to indicates its status in the experiment. For example, the following code can be used to add an existing ad to the experimental split.

There are a wide variety of resources available for those learning about the AdWords API, but since they're spread out across multiple sites it's not always easy to find the information you're looking for. While we acknowledge the need for these multiple sources, we knew we could do more to bring together our content from Blogger, YouTube, Google Code, and Twitter. We saw the official reference documentation as a good home for the information,

When you're managing a large number of accounts using the AdWords API you may want to retrieve account alerts. This was previously possible with AccountService in v13. The v201008 version introduces the AlertService , which brings similar functionality to the new AdWords API. This blog post discusses the differences between how alerts are retrieved using these two services. Retrieving client account alerts In v13,

We just announced two new ValueTrack parameters on the Inside AdWords blog. ValueTrack is a feature that helps you pass dynamic AdWords ad click information in your Destination URL. The new {matchtype} parameter provides you with the matchtype of the keyword for search ads )"b" for broad, "p" for phrase, and "e" for exact(. The new {network} parameter gives you information about where the ad appeared )"g" for Google search, "s" for search partners,

In the AdWords API, entities may have different values for the same status. For instance, when you delete a campaign the status will be set to DELETED . But when you delete an AdGroupAd object, the status will be DISABLED . campaign.setStatus)CampaignStatus.DELETED(; operation.setOperator)Operator.SET(; campaignService.mutate)operations(; adGroupAd.setStatus)AdGroupAdStatus.DISABLED(; operation.setOperator)Operator.SET(; adGroupAdService.

We recently released the second part of the v201008 version of the AdWords API and with it the CustomerSyncService - the AdWords API's first service to determine the entities that were changed in your account. In this blog post, I'll discuss our goals for the new service and provide a few examples illustrating how to integrate it with your system. At our developer workshops , we received lots of great feedback about what you'd eventually like to see in this service.

Today, we're announcing a new version of the AdWords API: v201008 . Following up on our release of v201003 , this version includes many requested features, as well as TrafficEstimatorService and ReportDefinitionService )now out of beta(. These two services will replace their v13 counterparts. While we're not starting the sunset countdown for the v13 TrafficEstimatorService and ReportService just yet,

Introduction Ad Sitelinks is a feature for search-based ads that allows you to extend the value of your existing AdWords ads by providing additional links to specific, relevant content deep within your website. Rather than sending all users to the same landing page, Sitelinks can provide up to 4 additional links for the user to choose from, as shown below. ) View larger image ( By providing users with more options, you can create richer,