Announcing the next AdWords API Workshops in October / November

Thursday, September 29, 2011

The Google Developer Relations team will be holding their next series of semi-annual AdWords API Workshops in October and November. These workshops will focus on new and upcoming features in the AdWords API, as well as best practices for special topics.

We invite you to join us for our next AdWords API Workshops which will be hosted in the following cities:

  • London, October 17th
  • San Francisco, October 18th
  • Hamburg, October 19th
  • Amsterdam, October 21st
  • New York City, October 25th
  • Tokyo, November 8th - New Location added this year
  • Singapore, November 11th - New Location added this year

In addition to presenting technical deep-dives on the topics listed below, we will also have the team on-hand to answer all your API-related questions, and also plan to give attendees a sneak peak and an opportunity to beta test a new programming feature being rolled out in the AdWords Frontend.

Workshop topics include:

  • Report Service Updates
  • AdWords API Authentication & Authorization Updates
  • Efficient API Usage with the Simplified Mutate Job Service
  • Campaign Targeting Changes
  • Mobile Best Practices

All events will have the same agenda, and will run from approximately 10:00AM - 3:00PM (local time). These workshops are geared towards software engineers who are already familiar with the AdWords API. Each session will focus on writing code and there will be no non-technical track.

For more information and to register, visit:

-- Sumit Chandel, AdWords API Team

Client Library Updates

Monday, September 19, 2011

We have recently made the following changes to the AdWords client libraries.


  • Made performance improvements.
  • Added unit spend information to responses.
  • Added support for Proxy servers.


  • Updated common module to version 2.1.0, which may impact your code. See the ChangeLog for more details.
  • Fixed issues 161, 162, 163 in version 14.2.3.
  • Added a tarball in the download section that collects all the required modules for this client library into a single download with an installer script.

You can download updated versions of the AdWords API client libraries from their respective sites, or see a list of all the client libraries.

If you have any questions or would like to discuss these changes, please post on the forum.

, AdWords API Team

Resolving Conflicts after Google Apps Account Migration

Thursday, September 01, 2011

Recently, we have migrated the Google Apps accounts to a new infrastructure that includes all Personal Google accounts. This has introduced a conflict for API users who have the same email address for both types of accounts. As a result, you will not be able to generate a ClientLogin token and will be presented with an error message such as “Either this object does not exist, or this user does not have permission to access it”, “Invalid client email specified” or an AuthenticationError.CLIENT_EMAIL_INVALID in the SOAP response. You can also verify whether your account is in conflict by making a request directly to the Client Login API.



Before the migration, it was possible to have a Google Apps account with your domain ( and a Personal Google account for AdWords, Picasa, Reader, etc. with the same email address. With the new infrastructure, both types of accounts are in one unified system so when you try to generate a ClientLogin token with, we do not know which account you are trying to use. More details about conflicting accounts can be found at the Google Accounts Help Article.

To differentiate between your conflicting accounts, we have created a temporary account ( for you to temporarily hold your data. You can log into with your gtempaccount and use the wizard to resolve your conflicts. A full walkthrough on the data migration wizard can be found at the Data Migration Getting Started Guide.

Please note that this issue will only affect tools built using clientEmail as a header to identify accounts. If you use clientCustomerId, the tool will not be affected. We recommend using clientCustomerId instead of clientEmail as a best practice.

As always, please post any questions to the forum.

, AdWords API Team