Google Ads Developer Blog

AdWords API - Upcoming changes to AdGroupCriterionService.mutate behaviour

2012-05-28T00:34:00.000-07:00

We are making some changes to the way qualityInfo and firstPageCpc fields are returned by AdGroupCriterionService in AdWords API. Currently, the qualityInfo and firstPageCpc fields are populated for BiddableAdGroupCriterion objects returned in response to AdGroupCriterionService.mutate API calls. Starting the week of June 15th, these fields will no longer be populated in mutate call responses. If you wish to retrieve QualityInfo or firstPageCpc for criteria, you need to retrieve them by making a get() call instead, using the appropriate selector fields. This change will affect all the active versions of the AdWords API.

If your code depends on the current behaviour of AdGroupCriterionService.mutate, please make sure you migrate your code by the week of June 15th. If you have any questions about these changes please reach out to us in the forum or during one of our office hours hangouts.

- Anash P. Oommen, AdWords API Team

AdWords API - Updates in Search Query Performance Report

2012-05-25T14:06:00.000-07:00

As previously mentioned, AdWords now supports new matching behavior for exact and phrase match keywords. Support was added in v201109_1 that allows toggling of this setting. In order to better support reporting on the performance of this new feature, the Search Query Performance Report will gain a new field, MatchTypeWithVariant, which will now return two additional enum values in addition to the existing values of the MatchType field (enum values / display values):

NEAR_EXACT / exact (close variant)
NEAR_PHRASE / phrase (close variant)

The existing MatchType field will continue to return only the values it does today. This means that a value that would return “exact (close variant)” from MatchTypeWithVariant will return as “exact” for field MatchType.

This new field will be available starting the week of Monday June 4th.

If you have any questions about this change or other issues, please post on the forum or attend one of the AdWords API Office Hours Hangouts.

- Kevin Winter, AdWords API Team

Announcing a from-scratch rewrite of the Java Client Library

2012-05-21T14:01:00.000-07:00

The Java Client libraries for Ads APIs are some of the most popular, used by thousands of developers each day to manage their AdWords, DFA and DFP accounts. Since they were initially written years ago, we’ve gotten a lot of feedback from developers using the libraries. We’ve tried to incorporate as many suggestions as possible, but due to the legacy architecture, certain changes were not feasible.

Today we’re pleased to announce that we are officially supporting a new from-scratch rewrite of the Java Library! It is now production-ready and is no longer experimental. Read on for some reasons why you’ll want to take the new library for a spin right away.

New Features

New features in the rewritten library include:

Product level support for AdWords, DFA and DFP with shared common layer code.
Library is now hosted on Maven.
OAuth1.0a and OAuth2.0 support.
Uses the SLF4J logging facade.
More control over building your session, providing authentication and more.
Experimental AppEngine support via JAX-WS.

Migrating

The two biggest changes involve how to configure your session and how to obtain Service objects.

Here’s how you configure an AdWordsSession:

AdWordsSession session = new AdWordsSession.Builder()
    .fromFile()
    .withClientLoginToken(clientLoginToken)
    .build();

Here’s how you obtain a reference to a service:

AdWordsServices adWordsServices = new AdWordsServices();
CampaignServiceInterface campaignService =
    adWordsServices.get(session, CampaignServiceInterface.class);

Check out the migration guide we have recently published on the new project page wiki. You’ll find these procedures described in depth, along with best practices for using these classes.

The new library will be the primary focus of development moving forward. The existing AdWords and DFP java libraries are now in maintenance mode and we will continue to add support for new AdWords and DFP API releases for the near future.

If you find any bugs, have a patch to contribute or just a feature request, please feel free to file an issue on our issue tracker.

- Kevin Winter, AdWords API Team

AdWords API v201109_1 - new AdWords features available more quickly in dot release and beta program

2012-05-08T12:57:00.000-07:00

In an effort to make more features available faster to AdWords API users, we’re launching AdWords API v201109_1, a dot release which includes services to help API users incorporate some recent AdWords web interface launches into their applications. New features include:

Keyword match properties NEAR_EXACT and NEAR_PHRASE, which allow API users to opt in/out of these match types.
LocationSyncExtension and the reports download service now have OAuth 1.0 support, bringing these services in line with others in the API.

As part of this dot release, we are also launching a few other features that will be available through an invitation-only beta. Similar to beta programs for the AdWords interface, the goal of this beta is to give developers earlier access to specific features, allowing us to incorporate feedback more quickly and innovate more effectively.

Moving forward, we will use dot releases to launch AdWords features more quickly. AdWords API v201109_1 does not start the sunset on prior versions, so you do not need to upgrade immediately.

Complete release notes are available here. If you have any questions about these changes please reach out to us in the forum or during one of our office hours via Google+ Hangouts.

Posted by AdWords API Team

The Docs are Dead. Long Live the Docs!

2012-04-19T04:36:00.003-07:00

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.

Follow the links below to take a look at the full range of Ads API docs on Google Developers:

We’ll continue to try to improve the Ads API docs on Google Developers while, over time, Google Code returns to its original purpose as an open source project hosting service. Visits to the old Google Code docs will be redirected to the corresponding Google Developers docs throughout 2012, so be sure to update your bookmarks soon.

If you have any questions about these changes please reach out to us through any of the Ads API forums or office hours.

Lesley Burr, Ads Developer Relations Team

Changes to advanced location targeting

2012-04-09T11:15:00.000-07:00

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.
The default value of the exclusion setting will be more restrictive for new campaigns, taking into account both the physical location and the area of interest. In API terms, GeoTargetTypeSetting.negativeGeoTargetType will default to DONT_CARE for new campaigns. The value will not be updated for existing campaigns.
The AdWords web interface has reworded the language used to describe these settings. If you provide a user interface you may want to update your language as well.

If you have any questions about these changes please reach out to us in the forum or during one of our office hours hangouts.

- Eric Koleda, AdWords API Team

Processing updates in bulk with MutateJobService

2012-04-04T04:57:00.000-07:00

The AdWords API is designed to handle a high volume of changes, and many services allow developers to submit a large number of operations in one request. Most of the AdWords API services are synchronous though, so the client sends the request to the server, waits for processing and receives the result back.

Unlike other services, the MutateJobService (MJS) is designed for an asynchronous workflow. This has the following benefits:

No need to manage connections for each job - the job is executed autonomously and the results can be retrieved when ready.
Multiple jobs can be submitted and executed in parallel. In fact, the service has no limit on the maximum jobs count.
Transient errors like 'CONCURRENT_MODIFICATION' are automatically retried with no extra requests necessary.
Workload is automatically balanced so you will never receive a 'RateExceededError' error.

Also, MutateJobService operations cost only 50% of usual operations units cost.

Using MutateJobService in existing applications

Replacing existing calls to synchronous services with calls to MJS is easy. In most cases you can just use the same operations array to submit a job. Once submitted, the application needs to check the job status periodically to see when it is complete. Once ready, the results can be retrieved with the getResult method.

Please see examples in Java, PHP, Perl, DotNet, Ruby and Python for more details.

Recommendations:

Don't poll for job status too often as this can result in RATE_EXCEEDED_ERROR error. We recommend pausing for 5-30 seconds between get requests.
Although there is no minimum number of operations for a MJS job, it is more effective to send at least 100 operations per job. You can send up to 10,000 operations in one job.
When submitting a job that operates on multiple AdGroups and Campaigns, try grouping operations in such a way as to minimize the number of different AdGroups in one job.

Note: while the old BulkMutateJobService is still available we recommend to use the MutateJobService for all future developments.

MutateJobService is covered in more details in our video presentation: Efficient API Usage with the MutateJobService. As always, please feel free to ask any questions regarding the AdWords API on our forum or during scheduled office hours.

- Danial Klimkin, AdWords API Team.

Increased AdWords Account Limits

2012-03-20T06:26:00.000-07:00

As you may have recently read on the Inside AdWords blog we’ve increased various limits for Google AdWords accounts. Most notably it’s now possible to have up to 10,000 campaigns and three million keywords in an account. These and other product limits are listed in the AdWords Help Center, with additional API technical limits available on the System Limits page.

As a reminder, when dealing with large numbers of API objects it’s best to utilize paging in your requests, which allows you to fetch the data in smaller batches. The example code in our client libraries demonstrates how to use paging effectively. However, paging alone is insufficient to retrieve data sets with over 10,000 items and in those situations we recommend you either use predicates to limit the size of the results or use report downloads to get the full set of data.

If you have questions about these new limits or how they affect your API development you can reach us on the forum or during our regular office hours.

- Eric Koleda, AdWords API Team

Specifying version when requesting reports starting April 11

2012-03-13T12:34:00.000-07:00

Starting on April 11, 2012 we will require the API version string to be included as part of the HTTP request when downloading the AdWords API AdHoc reports. If version is not provided, the RequestError.INVALID_INPUT error will be returned. The requests for downloading reports should be sent to the following URL,


https://adwords.google.com/api/adwords/reportdownload/v201109

If you are using the latest versions of our client libraries for downloading reports, this change will not affect you.

As always, please feel free to ask any questions regarding the AdWords API on our forum or during scheduled office hours.

- Stan Grinberg, AdWords API Team

Spring 2012 Office Hours

2012-03-13T09:00:00.000-07:00

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. You can also continue to follow our schedule by subscribing to the Google Ads Developer Office Hours calendar which is also linked on the sidebar to the right of this blog entry.

In case you haven’t joined us before, you will need 3 things to join the hangout:

A Google+ account (sign up here)
The Google voice and video plugin installed on your computer
A quiet place to hangout so we can hear you

These hangouts are informal and conversational, which make them a great place to ask questions or give us feedback. If you have questions about our office hours program, reach out to us on the forums.
- Paul Rashidi, DFP API Team

Updates to AdWords API Terms & Conditions

2012-03-08T06:01:00.001-08:00

Today, in an ongoing effort to improve clarity, we have released an update to the Terms & Conditions for AdWords API Clients. As a reminder, per our terms and conditions, Google retains the right to modify the terms and conditions at any time. Note that continued use of the API means that you accept these terms. You can refuse to accept the terms by ceasing to use the API.

Below is an overview of what has changed:

We’ve updated the definition of an AdWords API client. In addition, we’ve modified the definition of an “End-Advertiser-Only AdWords API Client” (section I).
We clarify when we may terminate a token for non-use (section II.1).
We’ve added a clause specifying that a token may only be used for the applications/tools that it was approved for in the application process, and that we need to be notified of any changes (section II.5).
We’ve clarified the “Copying Data” section of the co-mingling clause to ensure that users manually import or export all campaigns (section III.2.c.ii).
We will now require clients to contact Google within 15 days of a change of control via written notice and re-application for a token (section IV.16).
We’ve added an "experimental program" clause and are deprecating our current 4-month deprecation clause (section IV.2.a). We are giving people 4 months notice before these changes take effect (section IV.17).

Please review the complete Terms & Conditions here.

Posted by The Google AdWords API Team

Resources to help with the migration to AdWords API AdHoc reports

2012-03-06T12:32:00.001-08:00

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.
The mapping report to the UI guide maps the concepts and naming conventions used in the User Interface (UI) and the AdWords API reports.
Report basics covers how to structure and download reports.
This blogpost covers best practices for when to schedule reports, and this post covers how to download reports for multiple clients.

For additional resources visit the AdWords API documentation.

We also encourage you to submit questions to the forum or ask them during office hours.

Post by Katie Miller, AdWords API Team

Streamline your coding with AdWords API examples

2012-02-24T12:19:00.000-08:00

Are you getting started with the AdWords API but short on time to read the documentation? Do you need a reference implementation of a particular API operation? Check out our client libraries code examples which have undergone extensive renovations in the last libraries release!

The code examples are one of the best resources to learn the API and understand version changes. It is also helpful to have a working code to troubleshoot issues you may have with your own implementation. You can find the list of the client libraries and the resources for each library on the AdWords API site.

There were a number of changes introduced which we hope will make the examples code base more useful and easy to follow:

The code examples are now oriented around typical use cases rather than the API-specific operations. To get Criteria report look for the getCriteriaReport example, to create text ads - for the createTextAds example.
The number of input parameters was reduced which means you can run more examples as-is now, without adding specific object IDs.
For each example the code is wrapped into a function which can be called with parameters. This makes it easier to find out what parameters are required and improves examples testability.
Some of our Best Practices are now also demonstrated in the examples and described in the comments.

We’ve also changed the example files layout. We’ve noticed developers find it easier to navigate defined sections:

BasicOperations: start here if you are new to the AdWords API. This directory contains examples of basic operations such as creation, updating and deletion of most commonly used objects. The examples demonstrate the principles used in the rest of the API: selectors, predicates, paging, grouping of operations.
Targeting, CampaignManagement: these sections contain more advanced examples on the AdWords API such as geo targeting, location extensions, experiments and ad parameters.
ErrorHandling: examples in the ErrorHandling directory demonstrate how to handle different kind of errors occurring during the API calls. The errors covered here are API-specific (e.g. not network errors) and not transient so they could not be solved by retrying the exact same request.
Reporting: this section includes examples on how to retrieve a report with the client libraries. You can find the list of reports and their fields available on our codesite page.
AccountManagement: examples in the AccountManagement section will be helpful if you manage more than one account via the API. Here you can find code which retrieves accounts’ hierarchy or finds units spent on particular account.
Optimization: If you are looking for keyword or placement ideas or traffic estimations, you can find the examples in this section.
Remarketing: conversion tracker and audience operations are shown in examples in the Remarketing section.
Misc: this section contains examples that don’t fit into any other category and also some library-specific code samples. Check out our OAuth authorization code example here.

Browse updated examples code in: DotNet, Python, Ruby, Perl, PHP. We are working to update examples for Java and JavaScript as well.

As always, please feel free to ask any questions regarding the AdWords API on our forum or during scheduled office hours.

- Danial Klimkin, AdWords API Team

AdWords API v201109 migration deadline is next week. Make the move today to avoid errors

2012-02-22T11:49:00.000-08:00

We would like to once again remind you that after February 29, 2012, calls made using the following AdWords API versions will return errors:

AdWords API versions v13, v200909, v201003, v201008, v201101

We strongly encourage you to make the move to v201109 before the February 29th deadline. This will give you the opportunity to identify any issues before it is too late to roll back to previous versions.

In addition, check that you have no automated or scheduled scripts running that are using old code.

To ensure that your code uses only v201109, be sure you are using the latest version of our client libraries.

If you have specific migration questions, you can asking them in upcoming office hours or on the forum. Additional migration resources are available here.

Posted by Katie Miller, AdWords API Team

Demographic performance report deprecation

2012-02-17T15:01:00.000-08:00

Demographic reports allow you to see the performance of your ads by age groups and gender on the specific sites in the Display Network that provide this information. As part of a greater effort to simplify AdWords, the DEMOGRAPHIC_PERFORMANCE_REPORT is being deprecated and will no longer be available in the API starting on or around March 21, 2012. You can back up the historical demographic data for your campaigns by downloading these reports before they sunset.

Please be aware that this change doesn’t impact demographic exclusions for your campaigns, which are done via the AgeRange and Gender criteria in the CampaignCriterionService. If you have additional questions about this deprecation, please reach out to us on the AdWords API forum or one of our regular Google+ Hangout office hours.

- Eric Koleda, AdWords API Team

Migrate to AdWords API v201109 in the next 2 weeks to avoid application interruption

2012-02-16T10:00:00.000-08:00

This is a reminder that after February 29, 2012, calls made using the following AdWords API versions will return errors:

AdWords API versions v13, v200909, v201003, v201008, v201101

If you would like your applications to run without interruption, you must migrate to AdWords API v201109 by February 29th. Migration resources are available here. In addition, if you have specific questions, we encourage you to attend office hours or post questions to the forum.

Posted by Katie Miller, AdWords API Team

AdWords API: Retrieving large result sets

2012-02-01T06:31:00.000-08:00

When you need to retrieve a large set of objects, such as a list of criteria for an account, it’s tempting to use one simple query with a paging parameter to pull the data from the server page-by-page.

While this approach is acceptable for most queries, it has some limitations:

The AdWords API does not allow you to retrieve data whose start index is past 50000
Unit cost for the request will depend on the number of pages and will be relatively expensive
A parallel update request may interfere with the process
Error handling and retry logic could be complex

We recommend using one of the following approaches instead:

Use AdHoc reporting to obtain data. With reports, you can still retrieve most fields available through SOAP requests, with the added bonus of AdHoc reporting being faster and free of unit costs.
Try to narrow the query as much as possible with predicates. Group queries by Campaign and AdGroup to retrieve only required data and to fit all results into one response.

Also, you can save bandwidth and retrieve large results faster by enabling transparent gzip compression. Check out our best practices page for more details on this feature and other recommendations.

As always, please feel free to ask any questions regarding the AdWords API on our forum or during scheduled office hours.

- Danial Klimkin, AdWords API Team

30 days left to migrate to AdWords API v201109

2012-01-30T09:43:00.000-08:00

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.

We encourage you to use the following resources for a successful migration:
Review the resources in the AdWords API client libraries.
Review the “Discover v201109” blog series.
Subscribe to the AdWords API Twitter account, which will share daily migration tips for the next month
Make sure you’ve completed everything on this migration checklist.
Give yourself ample time to migrate from v13 to AdHoc reporting. Resources to help with this migration are available here.
Attend office hours.
Make sure your contact information is up to date in your My Client Center account.
Post questions on the forum.
Posted by Katie Miller, AdWords API Team

Prepare for the sunset with the AdWords API v201109 migration checklist

2012-01-27T09:49:00.000-08:00

As announced in October, we will sunsetting all versions of the AdWords API prior to v201109 on February 29, 2012. To help you prepare to migrate to v201109, we've created a checklist that covers all of the required changes:

Required Changes:

Migrate all API calls to use v201109 services
Migrate all API calls to use clientCustomerId (instead of clientEmail) to identify an account as the target of an operation (Blog post)
Migrate campaign geo target creation and identification to use the new location criterion object (available through the CampaignCriterionService and the LocationCriterionService)
Migrate all other campaign targets (except ad scheduling) from the CampaignTargetService to CampaignCriterionService using the appropriate criterion objects defined within that service*
Migrate cross client reporting to v201109 AdHoc (single account) reports (Blog post)
Provide developerToken as HTTP header in AdHoc report requests
The last few API releases have seen various services migrate to generic selectors, as you update to v201109 you’ll need to migrate from service specific selectors to generic selectors as required. See the Selector Migration Reference for details
Update to the very latest version of the AdWords API client library specific to the programming language(s) that you use for API tool/platform development**
If you generate your own client side stubs from the API Service WSDLs, make sure that your requests strictly adhere to the WSDL definition as we have implemented stricter validation for the SOAP header and envelope (Blog post)

Optional Changes:

You can now use the v201109 CreateAccountService to create AdWords optional-login accounts

Note: If you do not make the required changes, calls made using versions of the AdWords API prior to v201109 will return errors after February 29th 2012

Additional Notes:
*In v201109, most targets become criteria, with each having it’s own ‘type’ of criterion object (see this Blog post for more details)
**This is an important requirement, so do make sure to check the version of the library or libraries that you are using against those available here

- Mandy Waite, AdWords API Team

AdWords SOAP Header validation is being enabled

2012-01-25T11:30:00.000-08:00

Starting with v201109, we enabled stricter validation of the SOAP Body, meaning that XML that did not closely follow the XML Schema defined in the WSDL would be rejected with a SOAP fault. This stricter validation enables developers to detect flaws in their applications, such as sending an unsupported field, at development time rather than later discovering that field was ignored.

In the coming weeks, we will also be enabling stricter validation of the SOAP Headers. Currently, SOAP Headers that don’t validate against the XML Schema are ignored. This includes headers such as clientEmail/applicationToken (both of which do not apply to v201109) or partialFailure, which is case sensitive (will not accept “TRUE” or “True”, only “true”). When clientEmail is ignored, the request will target the authenticating account (often an MCC), which will, for example, return an error message if you attempt to add a Campaign or no results if you make a GET request.

The stricter validation will trigger a SOAP fault for any SOAP Headers that do not match the XML Schema defined in the WSDL. This may cause your application to see more errors such as those referenced in our previous blog post. This validation will enable developers to better detect bugs in their application that were previously silently ignored.

If you have any questions, please post on the forum or attend one of the AdWords API Office Hours Hangouts.

- Kevin Winter, AdWords API Team

Upcoming changes to AdWords Impression Share metrics

2012-01-24T02:19:00.000-08:00

We recently announced upcoming changes to AdWords Impression Share metrics. If you are using the AdWords API to download BudgetLostImpressionShare, ImpressionShare, QualityLostImpressionShare and ExactMatchImpressionShare metrics in account and campaign performance reports, then the upcoming change will affect you in the following ways:

We will revise campaign-level Impression Share metrics from May 1, 2011 to present. You may notice some adjustments in past campaign-level Impression Share data once this change goes live.
We will remove campaign-level Impression Share metrics prior to May 1, 2011. If you depend on historic impression share data prior to May 1, 2011, then you need to download them before January 30th.
All Impression Share metrics will only be updated once every day, by afternoon PST. In addition, the data will no longer be available for segmentation by hour. If you have a saved report definition that requests hourly aggregation of IS data, then those definitions will stop working once the new changes go live.

If you wish to backup old Impression Share data or make changes to the way you use Impression Share to control your AdWords campaigns, please do so before January 30th. If you have any questions about the AdWords API, check out our developer forum.

- Anash P. Oommen, AdWords API Team.

UPDATED: DeveloperToken in reports rollback

2012-01-20T13:27:00.000-08:00

Update: developer token will be required in report downloads starting February 7th, 2012.

Based on recent AdWords API forum posts, many of you are unaware that on January 17th we began requiring a developer token in all post v13 report downloads. As a result, we are temporarily rolling back this change to give you additional time to update your applications and upgrade to the latest version of the client libraries. If you have already made this change, no action is required on your part. We will enforce this requirement starting February 7th, 2012.

Minimum client library versions with support for providing the developerToken header in reports are as follows:

DotNet - 13.1.0
Java - 8.4.1
Perl - 2.5.1
PHP - 2.7.1
Python - 15.0.4
Ruby - 0.5.0

As always, we encourage you to subscribe to the AdWords API blog posts and Twitter account and to follow us on the forum to ensure that you are aware of all critical updates and requirements.

If you have any questions, please post on the forum or attend one of the AdWords API Office Hours Hangouts.

- Kevin Winter, AdWords API Team

ReportDefinition XML Schema Definition is now available

2012-01-19T11:33:00.000-08:00

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. Here’s an example URL used to obtain the XSD for v201109 ReportDefinitions:

https://adwords.google.com/api/adwords/reportdownload/v201109/reportDefinition.xsd

How to use this XSD

There are many tools to use to validate XML against an XSD. Here we will show how to use the common command-line tool xmllint to validate against the XSD. First, download the reportDefinition.xsd to a working directory. Next, save some ReportDefinition XML to a file, such as reportDefinition.xml:

<reportDefinition xmlns="https://adwords.google.com/api/adwords/cm/v201109">
 <selector>
   <fields>CampaignId</fields>
   <fields>Id</fields>
   <fields>Impressions</fields>
   <fields>Clicks</fields>
   <fields>Cost</fields>
   <predicates>
     <field>Status</field>
     <operator>IN</operator>
     <values>ENABLED</values>
     <values>PAUSED</values>
   </predicates>
 </selector>
 <reportName>Custom Adgroup Performance Report</reportName>
 <reportType>ADGROUP_PERFORMANCE_REPORT</reportType>
 <dateRangeType>LAST_7_DAYS</dateRangeType>
 <downloadFormat>CSV</downloadFormat>
</reportDefinition>

Now run the following command from the directory you placed these two files in:

$ xmllint --schema reportDefinition.xsd reportDefinition.xml
[xml omitted]
reportDefinition.xml validates

This step verifies that your ReportDefinition XML is well-formed for use with the AdWords API report downloads.

If you have any questions, please post on the forum or attend one of the AdWords API Office Hours Hangouts.

- Kevin Winter, AdWords API Team

Latest AdWords API developer docs available in 9 languages

2012-01-12T12:28:00.000-08:00

We are happy to announce availability of the AdWords API documentation for v201109 release in 9 languages in addition to English. In time for your upcoming migration with deadline on February 29, 2012, we have released the latest documentation in Chinese, French, Japanese, German, Korean, Portuguese, Russian, and Spanish. The drop-down menu at the top right corner of the documentation can be used to change the language.

If you have any questions, suggestions or requests for improving docs please post on the forum.

- Stan Grinberg, AdWords API Team

AdWords, DFA and DFP Client Library Updates

2012-01-12T10:41:00.000-08:00

We’re constantly making improvements to our AdWords, DoubleClick for Advertisers (DFA) and DoubleClick for Publishers (DFP) client libraries across all supported languages. Recently, we added the following features. Read the ChangeLogs and READMEs for details on these changes:

GZIP compression used when sending and receiving API calls and reports. (Perl and Java do not have this for AdWords API Report Downloads).
SSL certificate verification.
AdWords only - Examples and support for the new CreateAccountService.

Please see below for a summary of other changes for each library.

DotNet

No other updates.

Java

A preview version of the rewritten Java client library is now available for AdWords, DFA and DFP APIs. Please consider this alpha-quality code; please file any bugs or feature requests on the issue tracker. The new library currently supports Maven2, SLF4J, OAuth and we have plans to support other environments and platforms.

Ruby

Improved parameters validation and error reporting on missing / mistyped fields.
HTTP headers are now logged on DEBUG level.

Perl

Fixes to OAuth logic to better handle misconfigurations.
Several bug fixes.

PHP

AdWords only - Added example to get the clientCustomerId for a clientEmail.
AdWords only - Fixed issue with GetAccountHeirarchy example when used in the sandbox.
Fixed issue with lingering "id" attribute after reference replacement. Added tests for SoapXmlFixer.

Python

Validation and error handling has been improved to make it easier to use OAuth and Google AppEngine.

You can download updated versions of our client libraries from their respective sites, or see a list of all client libraries: AdWords, DFA and DFP.

If you have any questions or would like to discuss these changes, please post on our forums: AdWords, DFA, DFP.

- Kevin Winter, AdWords API Team