Google Ads Developer Blog: adwords

v201209 Sunset - 2 weeks remaining

Thursday, July 11, 2013

AdWords API v201209 will sunset on July 22nd, 2013

Tuesday, May 28, 2013

The sunset date for v201209 of the AdWords API has been extended to July 22, 2013. This will provide you with additional migration time while you are exploring the newly launched Enhanced Campaigns functionality.

Calls made to this version after July 22, 2013 will fail. It is therefore important that you migrate to AdWords API v201302 if you want your applications to continue to run without interruption.

If you have any questions about the sunset or need help with migration, please contact us on the forum. You can also reach out to us on Google+ page.

- Stan Grinberg, Ads Developer Relations Team

New AdWords API features supporting enhanced campaigns

Wednesday, February 6, 2013

We recently announced improvements to AdWords called enhanced campaigns. Today’s consumers are constantly connected and using many different devices, so we’ve developed enhanced campaigns to help advertisers reach them more effectively and more easily.

As part of the announcement of enhanced campaigns, we’ve enabled several new capabilities in the API including the ability to:

Upgrade campaigns to enhanced campaigns
Submit new ads marked as mobile preferred
Set a mobile bid adjustment
Retrieve Google suggested mobile bid adjustment for upgrading legacy campaigns to enhanced campaigns

These features are available for AdWords API developers through the forwardCompatibilityMap field, already available in Adwords API versions v201206 and v201209. For more information on how to use the Forward Compatibility Maps please consult this guide.

With the launch of enhanced campaigns, we have also updated the Required Minimum Functionality. Please review these materials carefully as you begin to develop your applications to create and upgrade to enhanced campaigns.

As always, we encourage you to review the resources in the AdWords API client libraries, as we have updated code examples. And if you have any questions, please post them on the AdWords API forum.

Posted by S Srikanth Belwadi - Product Manager, Adwords

40 days left to migrate to AdWords API v201209

Wednesday, January 16, 2013

Calls made using this version will return errors after February 26th. It is therefore critical that you migrate to AdWords API v201209 for your applications to run without interruption.

We encourage you to use the following resources for a successful migration:

Review the v201209 release notes.
Review the “Discover v201209” blog series.
Make sure you’ve made the essential changes laid out in the v201209 migration guide.
Review the resources in the AdWords API client libraries.
Attend the office hours sessions, to get face-to-face Q & A sessions.
Make sure your contact information is up to date in your My Client Center account.
Post questions on the forum.
Subscribe to our Google Plus page for news and announcements.

- Paul Matthews, AdWords API Team

We recently announced several changes and improvements to the way we report AdWords impression share (IS). We are now making these changes available through the v201209 version of AdWords API reports as well.

Around the second week of December, the following new columns will be available for account, campaign and adgroup performance reports:

ContentImpressionShare

ContentBudgetLostImpressionShare

ContentRankLostImpressionShare

SearchBudgetLostImpressionShare

SearchExactMatchImpressionShare

SearchImpressionShare

SearchRankLostImpressionShare
We now provide distinct search and display columns, so you can clearly separate search and display impression share. We also support “Hour of day” segmentation to evaluate how your ad coverage varies by the hour. You can get hourly segmentation of impression share data by requesting the HourOfDay column in your reports.
Finally, we’re improving the accuracy of how we calculate impression share data. As previously mentioned on our product blog and via social media, historical IS reporting data is now only available going back to October 1, 2012.
Phasing out old IS columns in February 2013
With the new IS columns now available, we’re planning to phase out the old IS columns (BudgetLostImpressionShare, ExactMatchImpressionShare, ImpressionShare and QualityLostImpressionShare) in February 2013.
If you face any issues with the above changes or have any questions about the AdWords API, you can ask us on our developer forum, or at the upcoming live office hours with the Developer Relations team.
- Anash P. Oommen, AdWords API Team

AdWords API v201209 launch - including shared budgets and more

Thursday, October 4, 2012

Update: The sunset of v201206 is now moved to March 25th, 2013.

We’re pleased to announce the launch of AdWords API v201209, which includes the ability to share budgets across multiple campaigns, set up demographic targeting at the ad group level, opt into a rotate indefinitely option for ad text, as well as some reporting changes that make errors clearer. Below we’ve highlighted some of the new features available to all users. A complete list of changes is available in the release notes.

v201209 highlights:

Shared budgets - The AdWords API now supports sharing budgets across campaigns through the new BudgetService and top-level Budget entity. All budgets are now potentially shareable so you need to first create a budget that is not associated with any particular campaign, and then assign campaigns to this budget via CampaignService.
Rotate indefinitely - CampaignService now has a fourth option for the ad rotation setting called ROTATE_INDEFINITELY. Read more about it in this announcement.
Ad group-level demographic targeting - Demographic targeting criteria (Age Range and Gender) are now available at the Ad group level (positive and negative). Note that you can continue to set negative targets at the Campaign level.
Reports - A new XML format is being introduced to report download error responses that makes it easier to parse the error messages. Also, report downloads using reportDefinitionId are no longer supported, and a valid AdWords API version must now be supplied in the URL for all report download requests.

With the release of v201209, we are deprecating v201206 and sunsetting it at the end of February 2013.

As with every new version of the AdWords API, we encourage you to review the resources in the release notes. If you have any questions please post on the forum or attend one of the AdWords API Office Hours Hangouts.

- The AdWords API Team

Ads Developer Blog

v201209 sunsets on July 22 - a reminder

v201209 Sunset - 2 weeks remaining

AdWords API v201209 will sunset on July 22nd, 2013

New AdWords API features supporting enhanced campaigns

40 days left to migrate to AdWords API v201209

Impression share reporting changes

AdWords API v201209 launch - including shared budgets and more

Labels

Archive