Fixed: V4 Reporting Bug

Thursday, May 25, 2006

We have identified and corrected the V4 Reporting Bug that we reported on May 18.

We apologize again for the inconvenience.

-- Jon Diorio, Sr. Product Marketing "Guy"

System Maintenance - May 27

Wednesday, May 24, 2006

We will be performing routine AdWords system maintenance from 10am to 3pm PST on Saturday, May 27, 2006. While all AdWords advertisements will continue to run as normal, you will not be able to perform any API operations during this maintenance period.

We apologize for any inconvenience.

--Rohit Dhawan, Product Manager

V4 Reporting Bug and Workaround

Thursday, May 18, 2006

We wanted to take a minute to update you on a bug that affects V4 reporting. This bug affect all dates passed in to the v4 api.

Date parameters specified like the one below will fail with an error:

<endDay xsi:type="xsd:date">2006-05-01</endDay>

If you remove the xsi:type="xsd:date" attribute as shown below, the call will work:

We are working to correct this issue as quickly as possible. In the meantime, removing xsi:type="xsd:date" from your V4 code will allow you to work around the bug.

We apologize for the inconvenience, and we will notify you as soon as this issue is corrected.

-- The AdWords API Team

Want Email Updates on the API?

Monday, May 15, 2006

Just a quick word from “The Marketing Guy” (as I’m called over here)…

If you weren't aware of it already, I wanted to call your attention to the API Announcements email list.

We created this opt-in email service earlier this year based on your requests for more proactive (or “push”) notification of major API events (e.g. new releases, bugs, version shutdowns, etc).

We will continue to make all major and minor announcements about the API on both the AdWords API Blog and the AdWords API Developer Forum. However, all critical announcements that could impact the operation of your API systems will be echoed on this email list as well.

You can opt into this list from the AdWords API home page.

Thank you again for your support of the AdWords API, and we hope you find this service beneficial.

-- Jon Diorio, Sr. Product Marketing Guy

API Version 4 Now Available

Friday, May 12, 2006

We are happy to announce the release of the AdWords API Version 4.

Version 4 (V4) introduces three major enhancements to the AdWords API: local time zone operations, reporting on a list of account logins, and an update of the traffic estimator fields.


V4 includes new local time zone operations necessary for setting and retrieving account time zone information. Specifically, we’ve expanded the AccountService to include new getLocalTimezone, setLocalTimezone, and getTimeZoneEffectiveDate operations.

However, for the next few weeks, only getLocalTimezone and getTimezoneEffectiveDate will be supported. During this time, any calls to setLocalTimezone will return error code 111 (invalid time zone change). After we finish rolling out time zone support to all AdWords users, we will enable setLocalTimezone (this change will be announced on the AdWords API Blog and Forum).

For more information on how our new time zone support settings will affect API developers, please review our April 27th blog post.


The KeywordReportJob, CustomReportJob, AdTextReportJob and UrlReportJob objects in the ReportService have been modified so that developers can more easily report on a subset of accounts by providing a comma-separated list of account email logins. Specifically, we are replacing the clientAccounts (int[]) field with a new clientEmails (string[]) field.


To maintain functional parity with the AdWords web interface, we are replacing three fields in the KeywordEstimate data object with six (6) new fields. These new fields represent interval boundaries instead of single values. These changes, originally implemented in the AdWords web interface, are designed to give advertisers greater insight into their keyword performance.

  • avgPosition will be replaced with… lowerAvgPosition & upperAvgPosition
  • ClicksPerDay will be replaced with… lowerClicksPerDay & upperClicksPerDay
  • cpc will be replaced with… lowerCpc & upperCpc
  • Zero Impression Reporting – In order to support zero impression reporting in a future release, we have added an “includeZeroImpression” field to the KeywordReportJob and CustomReportJob. Please be aware that zero impression data will not be available in V4. We will notify all developers when this functionality becomes available.
  • Unique Request ID - A new response header element, requestId, uniquely identifies each request. This element allows tracking of requests by developers and the web service.
  • Geo Codes – We are no longer supporting non-standard country codes, including UK and YU. This will affect any method that uses GeoTarget as well as keyword tool methods.


Per our versioning policy, V3 will be supported for two months from today, at which time it will be turned off. Therefore, please make sure that you upgrade to V4 before July 12, 2006.

For technical details about V4, please review the latest Release Notes section of the Developer’s Guide.

-- Rohit Dhawan, Product Manager

System Maintenance - May 13

Tuesday, May 09, 2006

We will be performing routine AdWords system maintenance from 10am to 2pm PST on Saturday, May 13, 2006. While all AdWords advertisements will continue to run as normal, you will not be able to perform any API operations during this maintenance period.

We apologize for any inconvenience.

--Rohit Dhawan, Product Manager

Make Sure to Update Your MCC logins

Wednesday, May 03, 2006

This is a reminder that we're finalizing the integration of the AdWords MCC login system with Google Accounts. If you haven't already updated your MCC account logins to use Google Accounts, you'll be required to do so over the next one to two weeks.

Since some of you have not yet done so, we wanted to post this final reminder. It’s important to note that if someone updates an MCC login and specifies a new account login or password, API connectivity could be interrupted.

Therefore, if you have not yet updated your MCC login, please review the best practices laid out in our October 24, 2005 AdWords API Blog posting on this subject and be sure to coordinate logins with your colleagues and clients.

You can learn more about the Google Account login integration processes at the following FAQ: about this process.

-- Rohit Dhawan, Product Manager

Version 2 Shutdown Tomorrow

Monday, May 01, 2006

Please take note… per our announcement on March 9, we will shutdown Version 2 of the API tomorrow.

Please make sure you have migrated your applications to Version 3 in order to ensure uninterrupted service. You can find more information about Version 3 (including the release notes) at

-- Rohit Dhawan, Product Manager