<?xml version="1.0" encoding="UTF-8"?>

<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearchrss/1.0/" xmlns:blogger="http://schemas.google.com/blogger/2008" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0"><id>tag:blogger.com,1999:blog-7815614485808579332</id><updated>2016-06-27T07:36:54.007-07:00</updated><category term="adwords_api" /><category term="dfp_api" /><category term="admob_sdk" /><category term="adwords_scripts" /><category term="mobile" /><category term="iOS" /><category term="mobile_ads_sdk" /><category term="dfa_api" /><category term="android" /><category term="ima_sdk" /><category term="ad_exchange" /><category term="sunset" /><category term="adsense_api" /><category term="reporting" /><category term="client_libraries" /><category term="reports" /><category term="adsense_management_api" /><category term="dfp_mobile" /><category term="ad_exchange_rtb" /><category term="ad_exchange_rest" /><category term="deprecation" /><category term="html5" /><category term="oauth2" /><category term="release" /><category term="admob" /><category term="adsense" /><category term="feeds" /><category term="dfp_reports" /><category term="hangout" /><category term="shopping" /><category term="admob_mediation" /><category term="adwords_v201109" /><category term="ad_exchange_soap" /><category term="bidding" /><category term="docs" /><category term="targeting" /><category term="upgraded_urls" /><category term="oauth" /><category term="adwords" /><category term="adwords_api_workshops" /><category term="adwords_v201209" /><category term="conversion" /><category term="unity" /><category term="workshops" /><category term="ad_exchange_optimization-series" /><category term="adwhirl" /><category term="adwords_api_v201406" /><category term="chart_tools" /><category term="dfa_reporting_api" /><category term="dfa_v1.18" /><category term="display_network" /><category term="geotargeting" /><category term="limits" /><category term="new_features" /><category term="ad_exchange_seller" /><category term="ad_extensions" /><category term="adwords_api_v201402" /><category term="adwords_api_v201506" /><category term="content" /><category term="content_api" /><category term="dfp" /><category term="dfp_v201111" /><category term="enhanced_campaigns" /><category term="mcc" /><category term="optimization" /><category term="PQL" /><category term="ads" /><category term="adsense_management_api_v1" /><category term="adsense_management_api_v1.1" /><category term="adwords_api_v201302" /><category term="adwords_api_v201409" /><category term="adwords_api_v201509" /><category term="dfp_pql" /><category term="display_select" /><category term="flash" /><category term="remarketing" /><category term="test_network" /><category term="video" /><category term="adsense_management_api_v1.3" /><category term="adwords_CampaignService" /><category term="adwords_MutateJobService" /><category term="adwords_api_v201306" /><category term="adwords_v201309" /><category term="analytics" /><category term="app_engine" /><category term="awql" /><category term="dfa_v1.20" /><category term="dfp_creatives" /><category term="dfp_v201201" /><category term="dfp_v201203" /><category term="dfp_v201204" /><category term="examples" /><category term="google_apps_script" /><category term="io13" /><category term="location_extensions" /><category term="php" /><category term="sitelinks" /><category term="swift" /><category term="ConversionTrackerService" /><category term="GMF" /><category term="LocationExtensionOperand" /><category term="LocationGroups" /><category term="account_management" /><category term="ad_customizers" /><category term="admob_v4.3.1" /><category term="adsense_host_api" /><category term="adsense_host_api_v3" /><category term="adsense_management_api_v1.2" /><category term="adsense_management_api_v1.4" /><category term="adwords_BatchJobService" /><category term="adwords_ManagedCustomerService" /><category term="adwords_api_v201309" /><category term="adwords_api_v201502" /><category term="adwords_api_v201603" /><category term="adwords_v201206" /><category term="adwords_v201302" /><category term="adwords_v201306" /><category term="best_practices" /><category term="call_tracking" /><category term="case_study" /><category term="code_examples" /><category term="common_questions" /><category term="creatives" /><category term="dfa_v1.17" /><category term="dfp_appengine" /><category term="feedback" /><category term="flash_sdk" /><category term="geo_targets" /><category term="https" /><category term="i18n" /><category term="iOS9" /><category term="impression_share" /><category term="interview" /><category term="java_dart_api" /><category term="labels" /><category term="native" /><category term="offline_conversions" /><category term="ruby" /><category term="selector" /><category term="snds" /><category term="terms" /><category term="test_accounts" /><category term="AdGroup" /><category term="AdGroupAd" /><category term="AdWords Scripts" /><category term="CampaignCriterion" /><category term="DoubleClick_Rich_Media" /><category term="OfflineConversionFeedService" /><category term="PLA" /><category term="RateExceededError" /><category term="StepInsideAdWords" /><category term="ad_clicks" /><category term="ad_param" /><category term="admob_v5.0.5" /><category term="admob_v6.0.1" /><category term="advanced_apis" /><category term="adwhirl_v3.1.1" /><category term="adwords_AdGroupCriterionService" /><category term="adwords_CreateAccountService" /><category term="adwords_ReportDefinitionService" /><category term="adwords_api_v201601" /><category term="adwords_api_v201605" /><category term="adwords_v201601" /><category term="alerting" /><category term="analyticsapi" /><category term="android_layout" /><category term="animation" /><category term="aw_reporting" /><category term="beta" /><category term="budgets" /><category term="builders" /><category term="bulk_upload" /><category term="c#" /><category term="call-only" /><category term="call_metrics" /><category term="callout_extensions" /><category term="certificates" /><category term="click-to-download" /><category term="client_library" /><category term="conference" /><category term="creative_platforms" /><category term="custom_fields" /><category term="dart" /><category term="decorators" /><category term="developer" /><category term="dfa_ad_service" /><category term="dfa_api_v118" /><category term="dfa_creative_service" /><category term="dfa_site_service" /><category term="dfa_v1.16" /><category term="dfa_v1.19" /><category term="dfp_inventory" /><category term="dfp_sales" /><category term="dfp_teams" /><category term="dfp_v201206" /><category term="dfp_v201208" /><category term="dfp_v201211" /><category term="dfp_v201302" /><category term="dfp_v201308" /><category term="dotnet" /><category term="doubleclick" /><category term="doubleclick_studio" /><category term="dsa" /><category term="dynamic_creative" /><category term="excluded_placement_lists" /><category term="faq" /><category term="firebase" /><category term="forecast_service" /><category term="games" /><category term="gdc" /><category term="gdl" /><category term="google_apis" /><category term="google_drive" /><category term="google_play_services" /><category term="google_plus" /><category term="interstitial" /><category term="java_app_engine" /><category term="jdbc" /><category term="keywords" /><category term="line_item" /><category term="linq" /><category term="manager_accounts" /><category term="maps_api" /><category term="mobile_ads_garage" /><category term="mobile_targeting" /><category term="openrtb" /><category term="policy" /><category term="product_listing_ads" /><category term="proguard" /><category term="python" /><category term="rate_sheet" /><category term="referer" /><category term="rewarded_video" /><category term="rmf" /><category term="sandbox" /><category term="scripts" /><category term="sdkless" /><category term="search_network" /><category term="service_accounts" /><category term="shared_negative_keywords" /><category term="ssl" /><category term="suggested_ad_units" /><category term="template_ads" /><category term="ui" /><category term="v201509" /><category term="vast3" /><category term="vcpm" /><category term="viewable-cpm" /><category term="wp8" /><category term="xml" /><title type="text">Google Ads Developer Blog</title><subtitle type="html">The official blog for information about the AdWords, AdSense, DoubleClick and AdMob APIs and SDKs.</subtitle><link rel="alternate" type="text/html" href="http://googleadsdeveloper.blogspot.com/search/label/adwords_api" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/-/adwords_api/-/adwords_api?start-index=26&amp;max-results=25" /><author><name>Stan Grinberg</name><uri>http://www.blogger.com/profile/13815957415507388389</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img1.blogblog.com/img/b16-rounded.gif" /></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>230</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/blogspot/lQlzL" /><feedburner:info uri="blogspot/lqlzl" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><entry><id>tag:blogger.com,1999:blog-7815614485808579332.post-8394866751819460570</id><published>2016-06-03T07:38:00.000-07:00</published><updated>2016-06-03T07:38:22.568-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api" /><category scheme="http://www.blogger.com/atom/ns#" term="client_libraries" /><category scheme="http://www.blogger.com/atom/ns#" term="dfp_api" /><title type="text">AdWords and DFP Java client library will soon require Java 7+</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;After &lt;b&gt;November 2016&lt;/b&gt;, all releases of the &lt;a href="https://github.com/googleads/googleads-java-lib"&gt;Google Ads API Java Client Library&lt;/a&gt; will only be compatible with Java 7 (1.7) and higher.&lt;br /&gt;&lt;br /&gt; &lt;font size="4"&gt;Why this change is happening&lt;/font&gt;&lt;br /&gt;The primary reasons for this change are: &lt;ul&gt; &lt;li&gt;Java 6 is a bit outdated -- it was &lt;a href="http://www.oracle.com/technetwork/java/eol-135779.html#java-commercial-offerings"&gt;first introduced in Dec 2006&lt;/a&gt;, and &lt;a href="http://www.oracle.com/technetwork/java/eol-135779.html#java-commercial-offerings"&gt;Oracle's support for Java 6 is approaching some key end dates&lt;/a&gt;.&lt;/li&gt; &lt;li&gt;Maintaining support for Java 6 means code examples cannot leverage &lt;a href="http://www.oracle.com/technetwork/java/javase/jdk7-relnotes-418459.html"&gt;useful features of Java 7&lt;/a&gt;, such as catch clauses for multiple exception types and type inference for generic instance creation.&lt;/li&gt; &lt;li&gt;Usage of Java 6 among Google Ads API Java Client Library developers is rapidly declining.&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt; &lt;font size="4"&gt;Next steps&lt;/font&gt;&lt;br /&gt;If you are using Java 7 or higher, then no action is required.&lt;br /&gt;&lt;br /&gt; If you are still using Java 6 then you'll have to migrate your runtime to Java 7 or higher. Check out the &lt;a href="http://docs.oracle.com/javase/7/docs/webnotes/adoptionGuide/"&gt;Java 7 adoption guide from Oracle&lt;/a&gt; to get started.&lt;br /&gt;&lt;br /&gt; Still have questions? Feel free to file an issue on the library's &lt;a href="https://github.com/googleads/googleads-java-lib/issues"&gt;issues page&lt;/a&gt; or contact us via our &lt;a href="https://plus.google.com/115658573333388777174/posts"&gt;Google+ page&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt; &lt;span class='byline-author'&gt;&lt;img height="40" width="40" src="https://lh6.googleusercontent.com/OARJJ1a0J4Mw11dlC-Wl_OuLl2eKtEjhYQw8DiRxq19R_N38Vu5xICRd6D5WE66ibQklt5BWyquFuRLThvI6V067SGVhE-vW_5IiKq_G1tn8cDcZRAdHXE-8UegB_UryQ9dw5N7K" style="vertical-align: middle; border:none;"/&gt; - &lt;a href="https://plus.google.com/100205313733177937765/posts"&gt;Josh Radcliff&lt;/a&gt;, AdWords API Team&lt;/span&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/Zjf41PDVLAc" height="1" width="1" alt=""/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/8394866751819460570" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/8394866751819460570" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/lQlzL/~3/Zjf41PDVLAc/adwords-and-dfp-java-client-library.html" title="AdWords and DFP Java client library will soon require Java 7+" /><author><name>Google Ads Developer Advisor</name><uri>http://www.blogger.com/profile/16700526826531306391</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img1.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googleadsdeveloper.blogspot.com/2016/06/adwords-and-dfp-java-client-library.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-7815614485808579332.post-2252211805800199673</id><published>2016-06-01T08:35:00.001-07:00</published><updated>2016-06-01T08:35:29.005-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api" /><category scheme="http://www.blogger.com/atom/ns#" term="workshops" /><title type="text">Register now for the Fall 2016 AdWords API Workshops!</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;We’re excited to announce that the AdWords API Workshops are back this Fall, and global registration is now open. Visit the workshop website to register: &lt;a href="https://events.withgoogle.com/adwords-api-workshops-2016/"&gt;https://events.withgoogle.com/adwords-api-workshops-2016/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt; Choose a location and type of event that works best for you. Once you register, we'll send you an email confirmation.&lt;br /&gt;&lt;br /&gt; The types of workshops this Fall are: &lt;ul&gt; &lt;li&gt;The &lt;b&gt;Technical&lt;/b&gt; workshops are for experienced API users, and we are going to talk about advanced use cases on a very technical level.&lt;/li&gt; &lt;li&gt;The &lt;b&gt;Business&lt;/b&gt; workshop covers use cases, automation, scaling, and tools. There will not be any deep technical content in this workshop, so anyone can attend.&lt;/li&gt;&lt;/ul&gt; We’ll be covering everything from what’s new in each of the releases to how to better utilize the API.&lt;br /&gt;&lt;br /&gt; If you have any questions about the AdWords API Workshops, you can post them on our &lt;a href="https://groups.google.com/forum/#!forum/adwords-api"&gt;forum&lt;/a&gt;. Check out our &lt;a href="https://plus.google.com/+GoogleAdsDevelopers/posts"&gt;Google+&lt;/a&gt; page for Ads API updates.&lt;br /&gt;&lt;br /&gt; &lt;span class='byline-author'&gt;&lt;a href="https://plus.google.com/109542956637533475940/posts"&gt;&lt;img height="40" width="40" src="https://lh3.googleusercontent.com/0f-ZyaPvqJym-IQIlYdvfA7hSucdeLAQWyqkeAMtcFzvpmljMt1eK8_kG-mUcmI2m-dQ5IExQSooX9FvtX8FTYjJmIGUmlMYn3EPO-ZTOPZAxq_9fNu5ODo_CPRknQqn0KF1Bp6E" style="vertical-align: middle; border:none;"/&gt; Nadine Sundquist&lt;/a&gt;, AdWords API Team&lt;/span&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/DrA9NPZRSBY" height="1" width="1" alt=""/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/2252211805800199673" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/2252211805800199673" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/lQlzL/~3/DrA9NPZRSBY/register-now-for-fall-2016-adwords-api.html" title="Register now for the Fall 2016 AdWords API Workshops!" /><author><name>Google Ads Developer Advisor</name><uri>http://www.blogger.com/profile/16700526826531306391</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img1.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googleadsdeveloper.blogspot.com/2016/06/register-now-for-fall-2016-adwords-api.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-7815614485808579332.post-6235991145009901362</id><published>2016-05-27T10:03:00.000-07:00</published><updated>2016-05-27T13:25:53.983-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api" /><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api_v201605" /><category scheme="http://www.blogger.com/atom/ns#" term="release" /><title type="text">Announcing v201605 of the AdWords API</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;Today we’re announcing the release of &lt;a href="https://developers.google.com/adwords/api/docs/reference/#v201605"&gt;AdWords API v201605&lt;/a&gt;. This is the third release that follows the &lt;a href="http://googleadsdeveloper.blogspot.com/2016/01/new-release-schedule-for-adwords-api.html"&gt;new release schedule announced in January 2016&lt;/a&gt;. Here are the highlights: &lt;ul&gt; &lt;li&gt;&lt;b&gt;Expanded Text Ads and responsive ads for Display.&lt;/b&gt; Support was added for creating the new &lt;a href="https://developers.google.com/adwords/api/docs/reference/v201605/AdGroupAdService.ExpandedTextAd"&gt;ExpandedTextAd&lt;/a&gt; and &lt;a href="https://developers.google.com/adwords/api/docs/reference/v201605/AdGroupAdService.ResponsiveDisplayAd"&gt;ResponsiveDisplayAd&lt;/a&gt; ad types in &lt;a href="https://developers.google.com/adwords/api/docs/test-accounts"&gt;test accounts&lt;/a&gt;. Give these &lt;a href="http://adwords.blogspot.com/2016/05/ads-and-analytics-innovations-for-a-mobile-first-world.html"&gt;new formats&lt;/a&gt; a try with your test accounts. This functionality will be made available for production accounts over the next few months.&lt;/li&gt; &lt;li&gt;&lt;b&gt;Campaign bid estimates by platform.&lt;/b&gt; Inclusion of campaign estimates by platform was added to &lt;a href="https://developers.google.com/adwords/api/docs/reference/latest/TrafficEstimatorService"&gt;TrafficEstimatorService&lt;/a&gt;. Check out the updated &lt;a href="https://developers.google.com/adwords/api/docs/guides/traffic-estimator-service#prepare_the_request"&gt;Estimating Traffic&lt;/a&gt; guide for more details.&lt;/li&gt; &lt;li&gt;&lt;b&gt;Bid modifiers for all platforms (test accounts only).&lt;/b&gt; &lt;a href="https://developers.google.com/adwords/api/docs/reference/latest/CampaignCriterionService.CampaignCriterion#bidmodifier"&gt;Campaign&lt;/a&gt; and &lt;a href="https://developers.google.com/adwords/api/docs/reference/latest/AdGroupBidModifierService.AdGroupBidModifier"&gt;ad group&lt;/a&gt; bid modifiers for &lt;i&gt;all&lt;/i&gt; &lt;a href="https://developers.google.com/adwords/api/docs/reference/latest/AdGroupBidModifierService.Platform"&gt;platforms&lt;/a&gt; are now supported across all versions, but only in &lt;a href="https://developers.google.com/adwords/api/docs/test-accounts"&gt;test accounts&lt;/a&gt;. Previously, platform bid modifiers were only supported for the &lt;a href="https://developers.google.com/adwords/api/docs/appendix/platforms"&gt;HighEndMobile (30001) platform&lt;/a&gt;. This functionality will be made available for production accounts over the next few months, as mentioned in a recent &lt;a href="http://adwords.blogspot.com/2016/05/ads-and-analytics-innovations-for-a-mobile-first-world.html"&gt;Inside AdWords blog post&lt;/a&gt;.&lt;/li&gt; &lt;li&gt;&lt;b&gt;Improved reporting on quality score.&lt;/b&gt; The new &lt;a href="https://developers.google.com/adwords/api/docs/appendix/reports/all-reports#hasqualityscore"&gt;HasQualityScore&lt;/a&gt; field lets you filter reporting rows based on the presence or absence of quality score data for each criterion. In addition, the &lt;a href="https://developers.google.com/adwords/api/docs/appendix/reports/all-reports#qualityscore"&gt;QualityScore&lt;/a&gt; field will now have a value of '--' on rows where &lt;code&gt;HasQualityScore = false&lt;/code&gt;. Previously, these rows had a &lt;code&gt;QualityScore&lt;/code&gt; value of 6 for Search campaigns, and 0 (zero) for Display campaigns.&lt;/li&gt; &lt;li&gt;&lt;b&gt;Image dimensions in reports.&lt;/b&gt; The &lt;a href="https://developers.google.com/adwords/api/docs/appendix/reports/ad-performance-report#imagecreativeimageheight"&gt;ImageCreativeImageHeight&lt;/a&gt; and &lt;a href="https://developers.google.com/adwords/api/docs/appendix/reports/ad-performance-report#imagecreativeimagewidth"&gt;ImageCreativeImageWidth&lt;/a&gt; fields were added to the Ad Performance report so you can retrieve image dimensions for all &lt;a href="https://developers.google.com/adwords/api/docs/reference/latest/AdGroupAdService.ImageAd"&gt;image ads&lt;/a&gt; without making multiple &lt;a href="https://developers.google.com/adwords/api/docs/reference/latest/AdGroupAdService"&gt;AdGroupAdService&lt;/a&gt; requests.&lt;/li&gt;&lt;/ul&gt; If you’re using v201601 of the AdWords API, please note that it’s now deprecated and will &lt;a href="https://developers.google.com/adwords/api/docs/sunset-dates"&gt;be sunset&lt;/a&gt; on August 23, 2016. We encourage you to skip v201603 and migrate straight to v201605.&lt;br /&gt;&lt;br /&gt; As with every new version of the AdWords API, we encourage you to carefully review all changes in the &lt;a href="https://developers.google.com/adwords/api/docs/reference/#v201605"&gt;release notes&lt;/a&gt; and the &lt;a href="https://developers.google.com/adwords/api/docs/guides/migration/v201605"&gt;v201605 migration guide&lt;/a&gt;. The updated &lt;a href="https://developers.google.com/adwords/api/docs/clientlibraries"&gt;client libraries&lt;/a&gt; and code examples will be published shortly.&lt;br /&gt;&lt;br /&gt; If you have any questions or need help with migration, please post on the &lt;a href="https://developers.google.com/adwords/api/community/"&gt;forum&lt;/a&gt; or the &lt;a href="https://plus.google.com/+GoogleAdsDevelopers"&gt;Ads Developers Plus Page&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt; &lt;span class='byline-author'&gt;&lt;img height="40" width="40" src="https://lh6.googleusercontent.com/qDcZnztzS6s1O4oPOk33OiQ8T7VErqUL0r4wA6CoAcjwrwJ5niktK0mm8UENvdZ8j4dfAKg4pAMKq72OCTlPvc3BrRvQ4fAOq6e4-jvI5FbJXSZQBOfNyQbvBR4fIqKiAMMjHdcF" style="vertical-align: middle; border:none;"/&gt; - &lt;a href="https://plus.google.com/100205313733177937765/posts"&gt;Josh Radcliff&lt;/a&gt; &lt;a href="https://plus.google.com/100205313733177937765/posts"&gt;on behalf of&lt;/a&gt; the AdWords API Team&lt;/span&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/FnIR4Y1m5q4" height="1" width="1" alt=""/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/6235991145009901362" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/6235991145009901362" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/lQlzL/~3/FnIR4Y1m5q4/announcing-v201605-of-adwords-api.html" title="Announcing v201605 of the AdWords API" /><author><name>Google Ads Developer Advisor</name><uri>http://www.blogger.com/profile/16700526826531306391</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img1.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googleadsdeveloper.blogspot.com/2016/05/announcing-v201605-of-adwords-api.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-7815614485808579332.post-1685210010231649994</id><published>2016-05-19T11:10:00.000-07:00</published><updated>2016-05-19T11:10:13.205-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api" /><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api_v201509" /><category scheme="http://www.blogger.com/atom/ns#" term="sunset" /><title type="text">AdWords API v201509 sunset reminder</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;&lt;b&gt;AdWords API v201509 will be &lt;a href="https://developers.google.com/adwords/api/docs/sunset-dates"&gt;sunset&lt;/a&gt; on June 21, 2016, after which all v201509 API requests will begin to fail.&lt;/b&gt; This version was &lt;a href="http://googleadsdeveloper.blogspot.com/2015/10/announcing-v201509-of-adwords-api.html"&gt;deprecated&lt;/a&gt; on February 2, 2016. If you are still on v201509, we recommend that you skip v201601 and migrate directly to &lt;a href="http://googleadsdeveloper.blogspot.com/2016/03/announcing-v201603-of-adwords-api.html"&gt;v201603&lt;/a&gt;. Please be sure to migrate prior to sunset to ensure your API access is unaffected.&lt;br /&gt;&lt;br /&gt; We've prepared various resources to help you with the migration: &lt;ul&gt; &lt;li&gt;&lt;a href="https://developers.google.com/adwords/api/docs/guides/migration/v201603"&gt;v201603 migration guide&lt;/a&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="https://developers.google.com/adwords/api/docs/guides/migration/v201601"&gt;v201601 migration guide&lt;/a&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="https://developers.google.com/adwords/api/docs/reference/"&gt;Release notes&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt; As always, if you have any questions about this migration, please contact us via the &lt;a href="https://groups.google.com/forum/#!forum/adwords-api"&gt;forum&lt;/a&gt; or the &lt;a href="https://plus.google.com/+GoogleAdsDevelopers"&gt;Ads Developers Plus Page&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt; &lt;span class='byline-author'&gt;- Michael Cloonan, AdWords API Team&lt;/span&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/GXBzN3fLqvM" height="1" width="1" alt=""/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/1685210010231649994" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/1685210010231649994" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/lQlzL/~3/GXBzN3fLqvM/adwords-api-v201509-sunset-reminder.html" title="AdWords API v201509 sunset reminder" /><author><name>Google Ads Developer Advisor</name><uri>http://www.blogger.com/profile/16700526826531306391</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img1.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googleadsdeveloper.blogspot.com/2016/05/adwords-api-v201509-sunset-reminder.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-7815614485808579332.post-8791945641366304416</id><published>2016-05-17T08:08:00.000-07:00</published><updated>2016-05-17T08:08:23.147-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api" /><category scheme="http://www.blogger.com/atom/ns#" term="adwords_BatchJobService" /><category scheme="http://www.blogger.com/atom/ns#" term="adwords_MutateJobService" /><category scheme="http://www.blogger.com/atom/ns#" term="sunset" /><title type="text">Sunset of MutateJobService in the AdWords API</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;If you've been following the AdWords API &lt;a href="http://googleadsdeveloper.blogspot.com/search/label/sunset"&gt;sunset&lt;/a&gt; and &lt;a href="http://googleadsdeveloper.blogspot.com/search/label/release"&gt;release announcements&lt;/a&gt;, you know that there have been some changes to batch processing: &lt;ul&gt; &lt;li&gt;Version &lt;a href="http://googleadsdeveloper.blogspot.com/2015/10/announcing-v201509-of-adwords-api.html"&gt;v201509&lt;/a&gt; deprecated &lt;a href="https://developers.google.com/adwords/api/docs/reference/v201601/MutateJobService"&gt;MutateJobService&lt;/a&gt; and introduced &lt;a href="https://developers.google.com/adwords/api/docs/reference/latest/BatchJobService"&gt;BatchJobService&lt;/a&gt;.&lt;/li&gt; &lt;li&gt;Version &lt;a href="http://googleadsdeveloper.blogspot.com/2016/02/announcing-v201601-of-adwords-api.html"&gt;v201601&lt;/a&gt; supports both &lt;a href="https://developers.google.com/adwords/api/docs/reference/v201601/MutateJobService"&gt;MutateJobService&lt;/a&gt; and &lt;a href="https://developers.google.com/adwords/api/docs/reference/latest/BatchJobService"&gt;BatchJobService&lt;/a&gt; concurrently.&lt;/li&gt; &lt;li&gt;Version &lt;a href="http://googleadsdeveloper.blogspot.com/2016/03/announcing-v201603-of-adwords-api.html"&gt;v201603&lt;/a&gt; doesn't include &lt;a href="https://developers.google.com/adwords/api/docs/reference/v201601/MutateJobService"&gt;MutateJobService&lt;/a&gt;.&lt;/li&gt;&lt;/ul&gt; The planned &lt;a href="http://googleadsdeveloper.blogspot.com/2016/01/new-release-schedule-for-adwords-api.html"&gt;sunset date&lt;/a&gt; of version &lt;a href="http://googleadsdeveloper.blogspot.com/2016/02/announcing-v201601-of-adwords-api.html"&gt;v201601&lt;/a&gt; is &lt;b&gt;August, 2016&lt;/b&gt;, after which &lt;code&gt;MutateJobService&lt;/code&gt; will no longer be available.&lt;br /&gt;&lt;br /&gt; &lt;font size="4"&gt;What do I need to do?&lt;/font&gt;&lt;br /&gt;If you are still using &lt;code&gt;MutateJobService&lt;/code&gt;, please migrate to &lt;code&gt;BatchJobService&lt;/code&gt; ahead of &lt;b&gt;August, 2016&lt;/b&gt;.&lt;br /&gt;&lt;br /&gt; &lt;font size="4"&gt;How do I migrate?&lt;/font&gt;&lt;br /&gt;The migration from MutateJobService to BatchJobService is relatively straightforward and covered in the &lt;a href="https://developers.google.com/adwords/api/docs/guides/batch-jobs#migrating_from_mutatejobservice"&gt;migration section of the batch processing guide&lt;/a&gt;. The guide also contains &lt;a href="https://developers.google.com/adwords/api/docs/guides/batch-jobs#code_examples"&gt;code examples for each client library&lt;/a&gt; to help you get started.&lt;br /&gt;&lt;br /&gt; If you have any questions or need help with migration, please post on the &lt;a href="https://developers.google.com/adwords/api/community/"&gt;forum&lt;/a&gt; or the &lt;a href="https://plus.google.com/+GoogleAdsDevelopers"&gt;Ads Developers Plus Page&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt; &lt;span class='byline-author'&gt;&lt;img height="40" width="40" src="https://lh6.googleusercontent.com/Kltft4ltAn8Pu1ga0uFUkOSZPLLAXXnEK-4ozIdvNObV7mnlSjZRgY3pFDt323Dxw0UR7nsRVzAEvWbDiE_Io7v1jLbyhnrlDWe18PS4Wl7iYV2glKdkNTRcG50LShndUdVqLzCj" style="vertical-align: middle; border:none;" /&gt; - &lt;a href="https://plus.google.com/100205313733177937765/posts"&gt;Josh Radcliff&lt;/a&gt;, AdWords API Team&lt;/span&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/nTUTj2RrmUY" height="1" width="1" alt=""/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/8791945641366304416" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/8791945641366304416" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/lQlzL/~3/nTUTj2RrmUY/sunset-of-mutatejobservice-in-adwords.html" title="Sunset of MutateJobService in the AdWords API" /><author><name>Google Ads Developer Advisor</name><uri>http://www.blogger.com/profile/16700526826531306391</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img1.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googleadsdeveloper.blogspot.com/2016/05/sunset-of-mutatejobservice-in-adwords.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-7815614485808579332.post-4490476737491658732</id><published>2016-05-09T07:05:00.001-07:00</published><updated>2016-05-09T07:05:16.505-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api" /><category scheme="http://www.blogger.com/atom/ns#" term="flash" /><category scheme="http://www.blogger.com/atom/ns#" term="html5" /><title type="text">Begin migrating from Flash to HTML5 ads before June 30th</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;&lt;font size="4"&gt;What is changing?&lt;/font&gt;&lt;br /&gt;&lt;br /&gt; &lt;a href="https://plus.google.com/+GoogleAds/posts/dYSJRrrgNjk"&gt;Starting June 30, 2016&lt;/a&gt;, you will no longer be able to upload Flash display ads in AdWords. By January 2, 2017 existing Flash ads will no longer serve on the Google Display Network. In order for your ads to keep serving, you will need to migrate any existing Flash ads to HTML5. If you need help migrating, check out the &lt;a href="https://support.google.com/adwords/answer/6249073"&gt;Help Center Article&lt;/a&gt; on updating Flash ads to HTML5 ads.&lt;br /&gt;&lt;br /&gt; If you have video ads built in Flash, they will not be affected at this time. You do not need to migrate these ads.&lt;br /&gt;&lt;br /&gt; &lt;font size="4"&gt;Where can I learn more?&lt;/font&gt; &lt;ul&gt; &lt;li&gt;&lt;a href="https://developers.google.com/adwords/api/docs/guides/template-ads#html5_ads"&gt;HTML5 Ad Examples in the API&lt;/a&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="https://developers.google.com/adwords/api/docs/appendix/templateads#html5_upload_V1"&gt;HTML5 Template Ads&lt;/a&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="https://support.google.com/adwordspolicy/answer/176108?hl=en#HTML5"&gt;HTML5 Ad Specifications&lt;/a&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="https://developers.google.com/adwords/api/docs/clientlibraries#client-libraries"&gt;Ads API Client Libraries&lt;/a&gt;: Each of the client libraries has examples on how to add an HTML5 ad and how to upload a media bundle with the contents of the ad. Here are the examples for Java to get you started: &lt;ul&gt; &lt;li&gt;&lt;a href="https://developers.google.com/adwords/api/docs/samples/java/advanced-operations#add-an-html-5-ad-to-an-ad-group"&gt;Add an HTML5 ad to an ad group&lt;/a&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="https://developers.google.com/adwords/api/docs/samples/java/advanced-operations#upload-an-html5-zip-file-as-a-mediabundle"&gt;Upload an HTML5 zip file as a MediaBundle&lt;/a&gt;&lt;/li&gt; &lt;/ul&gt; &lt;/li&gt;&lt;/ul&gt; Questions? Visit us on the &lt;a href="https://groups.google.com/forum/#!forum/adwords-api"&gt;AdWords API Forum&lt;/a&gt; or our &lt;a href="https://plus.google.com/115658573333388777174/posts/bA8W5r3KwZb"&gt;Google+ page&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt; &lt;span class='byline-author'&gt;&lt;a href="https://plus.google.com/109542956637533475940/posts"&gt;&lt;img height="40" width="40" src="https://lh5.googleusercontent.com/NIB2rW268qTHsXN3Q83-7IhpnCVtKFEzNqqRtEPPoFrAhvyoHGSxZwYcohyVLi3EQyODrHtGzL223Bw4ZzrWfCfUMkCOpZAkl80taJj2wInfSnrIgoaxPcoNndc10eu5jCfZPq7c" style="vertical-align: middle; border:none;"/&gt; Nadine Sundquist&lt;/a&gt;, AdWords API Team&lt;/span&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/Ye2IfXYTw6U" height="1" width="1" alt=""/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/4490476737491658732" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/4490476737491658732" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/lQlzL/~3/Ye2IfXYTw6U/begin-migrating-from-flash-to-html5-ads.html" title="Begin migrating from Flash to HTML5 ads before June 30th" /><author><name>Google Ads Developer Advisor</name><uri>http://www.blogger.com/profile/16700526826531306391</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img1.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googleadsdeveloper.blogspot.com/2016/05/begin-migrating-from-flash-to-html5-ads.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-7815614485808579332.post-4720282933844257873</id><published>2016-05-03T11:01:00.001-07:00</published><updated>2016-05-03T11:12:23.447-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api" /><category scheme="http://www.blogger.com/atom/ns#" term="policy" /><title type="text">Upcoming changes to AdWords policy names</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;If you submit AdWords API &lt;a href="https://developers.google.com/adwords/api/docs/guides/exemption-requests"&gt;exemption requests&lt;/a&gt; for policy violations, then you may need to modify your application as a result of &lt;a href="https://support.google.com/adwordspolicy/answer/6397420"&gt;these recently announced policy changes&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt; &lt;font size="4"&gt;What is changing?&lt;/font&gt;&lt;br /&gt;For some policy violations, the values of the &lt;a href="https://developers.google.com/adwords/api/docs/reference/latest/AdGroupCriterionService.PolicyViolationError#externalpolicyname"&gt;externalPolicyName&lt;/a&gt;, &lt;a href="https://developers.google.com/adwords/api/docs/reference/v201603/AdGroupCriterionService.PolicyViolationError#externalpolicyurl"&gt;externalPolicyUrl&lt;/a&gt;, and &lt;a href="https://developers.google.com/adwords/api/docs/reference/v201603/AdGroupCriterionService.PolicyViolationError#externalpolicydescription"&gt;externalPolicyDescription&lt;/a&gt; fields on &lt;code&gt;PolicyViolationError&lt;/code&gt; will change.&lt;br /&gt;&lt;br /&gt; &lt;font size="4"&gt;What is not changing?&lt;/font&gt;&lt;br /&gt;The &lt;a href="https://developers.google.com/adwords/api/docs/reference/latest/AdGroupCriterionService.PolicyViolationKey#policyname"&gt;policyName&lt;/a&gt; field value on &lt;a href="https://developers.google.com/adwords/api/docs/reference/latest/AdGroupCriterionService.PolicyViolationError#key"&gt;PolicyViolationError.key&lt;/a&gt; will not change.&lt;br /&gt;&lt;br /&gt; &lt;font size="4"&gt;Could you remind me what a PolicyViolationError looks like?&lt;/font&gt;&lt;br /&gt;Absolutely - glad you asked! In the following sample, after the policy changes go live, the content in &lt;code&gt;externalPolicyName&lt;/code&gt;, &lt;code&gt;externalPolicyUrl&lt;/code&gt;, and &lt;code&gt;externalPolicyDescription&lt;/code&gt; may change, but the &lt;code&gt;policyName&lt;/code&gt; field will stay the same. &lt;pre class="prettyprint lang-xml"&gt;&lt;br /&gt;&amp;lt;errors xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="PolicyViolationError"&amp;gt;&lt;br /&gt; &amp;lt;fieldPath&amp;gt;operations[0].operand.ad.headline&amp;lt;/fieldPath&amp;gt;&lt;br /&gt; &amp;lt;trigger/&amp;gt;&lt;br /&gt; &amp;lt;errorString&amp;gt;AdPolicyError.POLICY_ERROR&amp;lt;/errorString&amp;gt;&lt;br /&gt; &amp;lt;ApiError.Type&amp;gt;PolicyViolationError&amp;lt;/ApiError.Type&amp;gt;&lt;br /&gt; &amp;lt;key&amp;gt;&lt;br /&gt; &amp;lt;&lt;b&gt;policyName&lt;/b&gt;&amp;gt;nonstandard_punctuation&amp;lt;/&lt;b&gt;policyName&lt;/b&gt;&amp;gt;&lt;br /&gt; &amp;lt;violatingText&amp;gt;!!!&amp;lt;/violatingText&amp;gt;&lt;br /&gt; &amp;lt;/key&amp;gt;&lt;br /&gt; &amp;lt;&lt;b&gt;externalPolicyName&lt;/b&gt;&amp;gt;Non-standard punctuation&amp;lt;/&lt;b&gt;externalPolicyName&lt;/b&gt;&amp;gt;&lt;br /&gt; &amp;lt;&lt;b&gt;externalPolicyUrl&lt;/b&gt;/&amp;gt;...&amp;lt;/&lt;b&gt;externalPolicyUrl&lt;/b&gt;&amp;gt;&lt;br /&gt; &amp;lt;&lt;b&gt;externalPolicyDescription&lt;/b&gt;&amp;gt;Google ads aren't allowed to have excessive or unnecessary punctuation or symbols such as the following:&lt;br /&gt; ...&lt;br /&gt; &amp;amp;lt;a href="https://support.google.com/adwordspolicy/answer/176095" target="_blank"&amp;amp;gt;See the full policy&amp;amp;lt;/a&amp;amp;gt;&lt;br /&gt; &amp;lt;/&lt;b&gt;externalPolicyDescription&lt;/b&gt;&amp;gt;&lt;br /&gt; &amp;lt;isExemptable&amp;gt;true&amp;lt;/isExemptable&amp;gt;&lt;br /&gt; &amp;lt;violatingParts&amp;gt;&lt;br /&gt; &amp;lt;index&amp;gt;18&amp;lt;/index&amp;gt;&lt;br /&gt; &amp;lt;length&amp;gt;3&amp;lt;/length&amp;gt;&lt;br /&gt; &amp;lt;/violatingParts&amp;gt;&lt;br /&gt;&amp;lt;/errors&amp;gt;&lt;br /&gt;&lt;/pre&gt; &lt;font size="4"&gt;What should you do?&lt;/font&gt;&lt;br /&gt;If your application looks for specific values of &lt;code&gt;externalPolicyName&lt;/code&gt;, &lt;code&gt;externalPolicyUrl&lt;/code&gt;, or &lt;code&gt;externalPolicyDescription&lt;/code&gt; to decide if a failed &lt;a href="https://developers.google.com/adwords/api/docs/reference/latest/AdGroupAdService.AdGroupAdOperation"&gt;AdGroupAdOperation&lt;/a&gt; should be resubmitted with one or more &lt;a href="https://developers.google.com/adwords/api/docs/reference/latest/AdGroupAdService.AdGroupAdOperation#exemptionrequests"&gt;ExemptionRequests&lt;/a&gt;, please make the following changes: &lt;ol&gt; &lt;li&gt;Modify your application to use the &lt;a href="https://developers.google.com/adwords/api/docs/reference/latest/AdGroupCriterionService.PolicyViolationKey#policyname"&gt;policyName&lt;/a&gt; instead of one of the &lt;code&gt;externalPolicy&lt;/code&gt; fields. The values for &lt;code&gt;policyName&lt;/code&gt; are non-localized constants, so this is a more reliable field for this use case.&lt;/li&gt; &lt;li&gt;In early &lt;b&gt;June, 2016&lt;/b&gt;, monitor your logs for occurrences of &lt;code&gt;PolicyViolationError&lt;/code&gt;. Look for any new &lt;code&gt;policyName&lt;/code&gt; values that you may want to incorporate into your application's logic for submitting exemption requests.&lt;/li&gt;&lt;/ol&gt; If you have any questions or need help, please post on the &lt;a href="https://developers.google.com/adwords/api/community/"&gt;forum&lt;/a&gt; or the &lt;a href="https://plus.google.com/+GoogleAdsDevelopers"&gt;Ads Developers Plus Page&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt; &lt;span class='byline-author'&gt;&lt;img height="40" width="40" src="https://lh5.googleusercontent.com/h0lsJ_xsvIvI245vS3Ai1vrBQwMJtbKzKSWecpZstsfg-51Ta3grDd2irb30xvHpwlZLf-tkxvd7ROBqXsDhU5zV5JFcofTWgnYWVx8yxsshtWvCvVPWFPhEX3oOjQXubizMpNGn" style="vertical-align: middle; border:none;"/&gt; - &lt;a href="https://plus.google.com/100205313733177937765/posts"&gt;Josh Radcliff&lt;/a&gt;, AdWords API Team&lt;/span&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/yOTDtjykum4" height="1" width="1" alt=""/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/4720282933844257873" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/4720282933844257873" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/lQlzL/~3/yOTDtjykum4/upcoming-changes-to-adwords-policy-names.html" title="Upcoming changes to AdWords policy names" /><author><name>Google Ads Developer Advisor</name><uri>http://www.blogger.com/profile/16700526826531306391</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img1.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googleadsdeveloper.blogspot.com/2016/05/upcoming-changes-to-adwords-policy-names.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-7815614485808579332.post-8167222675782360098</id><published>2016-04-25T07:15:00.000-07:00</published><updated>2016-04-25T07:15:25.849-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api" /><category scheme="http://www.blogger.com/atom/ns#" term="alerting" /><title type="text">A new Java framework for large-scale AdWords API alerting</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;When managing multiple AdWords accounts, it’s critical to identify underperforming ads and accounts in a timely manner. For account managers, these alerts are useful information to promptly solve issues and maintain ads quality.&lt;br /&gt;&lt;br /&gt; To reduce the technical barrier of the alerting workflow implementation, we are happy to announce &lt;a href="https://github.com/googleads/adwords-alerting"&gt;Alerting Framework on Adwords&lt;/a&gt;, an open source Java framework for large scale AdWords API alerting. This framework is capable of generating alerts for all accounts under the specified manager account, which includes downloading &lt;a href="https://developers.google.com/adwords/api/docs/appendix/reports"&gt;AdWords report&lt;/a&gt; data, combining it with other data feeds, processing them to trigger relevant alerts, and delivering the alert messages to the proper destination. You can use our &lt;a href="https://github.com/googleads/adwords-alerting/blob/master/src/main/resources/aw-alerting-alerts-sample.json"&gt;sample alerts&lt;/a&gt; to explore how it works, or set up your own alerting logic by implementing custom alert entities and plugging them into the system.&lt;br /&gt;&lt;br /&gt; Get started at the Alerting Framework on AdWords &lt;a href="https://github.com/googleads/adwords-alerting"&gt;GitHub repository&lt;/a&gt;. If you have any questions or would like to provide feedback, please visit the &lt;a href="https://github.com/googleads/adwords-alerting/issues"&gt;project issue tracker&lt;/a&gt;, &lt;a href="https://groups.google.com/forum/#!forum/adwords-api"&gt;AdWords API Forum&lt;/a&gt;, or our &lt;a href="https://plus.google.com/+GoogleAdsDevelopers"&gt;Google+ page&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt; &lt;span class='byline-author'&gt;Zhuo Chen, AdWords API Team&lt;/span&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/YXU1YBFBSVw" height="1" width="1" alt=""/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/8167222675782360098" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/8167222675782360098" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/lQlzL/~3/YXU1YBFBSVw/a-new-java-framework-for-large-scale.html" title="A new Java framework for large-scale AdWords API alerting" /><author><name>Google Ads Developer Advisor</name><uri>http://www.blogger.com/profile/16700526826531306391</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img1.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googleadsdeveloper.blogspot.com/2016/04/a-new-java-framework-for-large-scale.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-7815614485808579332.post-5091548813815873971</id><published>2016-04-12T07:53:00.000-07:00</published><updated>2016-04-12T07:53:36.866-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api" /><category scheme="http://www.blogger.com/atom/ns#" term="reporting" /><title type="text">AdWords: Updates to impression share in reporting</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;Starting in late April, 2016, AdWords will begin rolling out a new calculation for impression share, which will potentially affect your reports in the AdWords API if you rely on &lt;a href="https://developers.google.com/adwords/api/docs/appendix/reports/all-reports#contentbudgetlostimpressionshare"&gt;impression share columns&lt;/a&gt; and run Video Campaigns.&lt;br /&gt;&lt;br /&gt; Historically, a small percentage of impressions on YouTube videos were not being included in the calculation of the impression share columns. We've implemented an improved algorithm to more accurately count impression share volume that now accounts for these impressions.&lt;br /&gt;&lt;br /&gt; We plan to roll out the improved calculation over the next few months for all accounts and impressions, so if you run campaigns on YouTube, your impression share statistics will become more accurate when your account goes live.&lt;br /&gt;&lt;br /&gt; If you have any questions about this change, or other questions about the AdWords API, please contact us via the &lt;a href="https://groups.google.com/forum/#!forum/adwords-api"&gt;forum&lt;/a&gt; or the &lt;a href="https://plus.google.com/+GoogleAdsDevelopers"&gt;Ads Developers Plus Page&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt; &lt;span class='byline-author'&gt;- Michael Cloonan, AdWords API Team&lt;/span&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/ME5jsxi8_Yk" height="1" width="1" alt=""/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/5091548813815873971" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/5091548813815873971" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/lQlzL/~3/ME5jsxi8_Yk/adwords-updates-to-impression-share-in.html" title="AdWords: Updates to impression share in reporting" /><author><name>Google Ads Developer Advisor</name><uri>http://www.blogger.com/profile/16700526826531306391</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img1.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googleadsdeveloper.blogspot.com/2016/04/adwords-updates-to-impression-share-in.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-7815614485808579332.post-3674747235433591015</id><published>2016-03-23T15:06:00.001-07:00</published><updated>2016-03-23T15:06:35.327-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api" /><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api_v201603" /><category scheme="http://www.blogger.com/atom/ns#" term="release" /><title type="text">Announcing v201603 of the AdWords API</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;Today we’re announcing the release of &lt;a href="https://developers.google.com/adwords/api/docs/reference/#v201603"&gt;AdWords API v201603&lt;/a&gt;. This is the second release that follows the &lt;a href="http://googleadsdeveloper.blogspot.com/2016/01/new-release-schedule-for-adwords-api.html"&gt;new release schedule announced in January 2016&lt;/a&gt;. Here are the highlights: &lt;ul&gt; &lt;li&gt;&lt;b&gt;Campaign drafts and experiments.&lt;/b&gt; A new suite of services in v201603 gives you &lt;a href="http://adwords.blogspot.com/2016/02/test-with-confidence-using-campaign.html"&gt;more options and control&lt;/a&gt; over experimenting with your &lt;b&gt;Search Network&lt;/b&gt; and &lt;b&gt;Search Network with Display Select&lt;/b&gt; campaign experiments. Check out the new &lt;a href="https://developers.google.com/adwords/api/docs/guides/campaign-drafts-experiments"&gt;Campaign Drafts and Experiments guide&lt;/a&gt; for all the exciting details! If you're currently using &lt;a href="https://developers.google.com/adwords/api/docs/reference/latest/ExperimentService"&gt;ExperimentService&lt;/a&gt; to manage your experiments, we recommend migrating to the new suite of services so you can make the most of your experiments.&lt;/li&gt; &lt;li&gt;&lt;b&gt;More flexibility with Target CPA and Target Spend.&lt;/b&gt; Following the &lt;a href="https://plus.google.com/+GoogleAds/posts/FP5XUu5DayT"&gt;revamped workflow for automated bidding announcement&lt;/a&gt; last month, the &lt;a href="https://developers.google.com/adwords/api/docs/guides/bidding#strategy-types"&gt;TARGET_CPA and TARGET_SPEND (Maximize clicks)&lt;/a&gt; bidding strategies can be created either as portfolio strategies (to share across multiple campaigns) or as standard strategies (to use with only one campaign). In addition, portfolio &lt;code&gt;TARGET_CPA&lt;/code&gt; bidding strategies now support different CPA targets for individual ad groups.&lt;/li&gt; &lt;li&gt;&lt;b&gt;Top content bid modifiers.&lt;/b&gt; The new &lt;a href="https://developers.google.com/adwords/api/docs/reference/v201603/AdGroupBidModifierService.PreferredContent"&gt;PreferredContent&lt;/a&gt; criteria type allows you to set a bid modifier for &lt;a href="https://support.google.com/adwords/answer/2732132#types"&gt;top content on YouTube or the Google Display Network&lt;/a&gt;, and the new &lt;a href="https://developers.google.com/adwords/api/docs/appendix/reports/top-content-performance-report"&gt;TOP_CONTENT_PERFORMANCE_REPORT&lt;/a&gt; lets you monitor your ad group's performance relative to those bid modifiers.&lt;/li&gt; &lt;li&gt;&lt;b&gt;Campaign mobile bid modifier simulations.&lt;/b&gt; &lt;a href="https://developers.google.com/adwords/api/docs/reference/v201603/DataService"&gt;DataService&lt;/a&gt; has new &lt;a href="https://developers.google.com/adwords/api/docs/reference/v201603/DataService#getcampaigncriterionbidlandscape"&gt;getCampaignCriterionBidLandscape&lt;/a&gt; and &lt;a href="https://developers.google.com/adwords/api/docs/reference/v201603/DataService#querycampaigncriterionbidlandscape"&gt;queryCampaignCriterionBidLandscape&lt;/a&gt; methods that will return bid simulations for campaign-level &lt;a href="https://developers.google.com/adwords/api/docs/appendix/platforms"&gt;HighEndMobile Platform&lt;/a&gt; (ID 30001) bid modifiers.&lt;/li&gt; &lt;li&gt;&lt;b&gt;Universal app campaigns in reports.&lt;/b&gt; Reports now include data for &lt;a href="https://support.google.com/adwords/answer/6247380"&gt;Universal App Campaigns&lt;/a&gt;. You can identify these campaigns by looking for &lt;a href="https://developers.google.com/adwords/api/docs/appendix/reports/all-reports#advertisingchanneltype"&gt;AdvertisingChannelType&lt;/a&gt; &lt;code&gt;MULTI_CHANNEL&lt;/code&gt; or &lt;a href="https://developers.google.com/adwords/api/docs/appendix/reports/all-reports#advertisingchannelsubtype"&gt;AdvertisingChannelSubType&lt;/a&gt; &lt;code&gt;UNIVERSAL_APP_CAMPAIGN&lt;/code&gt;.&lt;/li&gt; &lt;li&gt;&lt;b&gt;Batch processing.&lt;/b&gt; &lt;a href="https://developers.google.com/adwords/api/docs/reference/latest/BatchJobService"&gt;BatchJobService&lt;/a&gt; now supports job cancellation in all versions of the API. &lt;a href="https://developers.google.com/adwords/api/docs/reference/v201601/MutateJobService"&gt;MutateJobService&lt;/a&gt; has been removed in v201603, so be sure to check out the &lt;a href="https://developers.google.com/adwords/api/docs/guides/batch-jobs#migrating_from_mutatejobservice"&gt;migration information&lt;/a&gt; if you have not yet transitioned to &lt;code&gt;BatchJobService&lt;/code&gt;.&lt;/li&gt; &lt;li&gt;&lt;b&gt;Targeting extensions.&lt;/b&gt; &lt;a href="https://developers.google.com/adwords/api/docs/guides/extension-settings"&gt;Extension setting services&lt;/a&gt; now support setting campaign, ad group, keyword, and location targeting for each &lt;a href="https://developers.google.com/adwords/api/docs/reference/latest/AdGroupExtensionSettingService.ExtensionFeedItem"&gt;ExtensionFeedItem&lt;/a&gt;, as shown in the &lt;a href="https://developers.google.com/adwords/api/docs/guides/extension-settings"&gt;updated code examples&lt;/a&gt;.&lt;/li&gt; &lt;li&gt;&lt;b&gt;Reporting improvements.&lt;/b&gt; Ad group bid modifiers are now available via the new &lt;a href="https://developers.google.com/adwords/api/docs/appendix/reports/adgroup-performance-report#adgroupmobilebidmodifier"&gt;AdGroupMobileBidModifier&lt;/a&gt; field in the &lt;a href="https://developers.google.com/adwords/api/docs/appendix/reports/adgroup-performance-report"&gt;ADGROUP_PERFORMANCE_REPORT&lt;/a&gt; report. Null values will appear as two dashes (--) for String fields in all reports.&lt;/li&gt;&lt;/ul&gt; If you’re using v201509 of the AdWords API, please note that it’s now deprecated and will &lt;a href="https://developers.google.com/adwords/api/docs/sunset-dates"&gt;be sunset&lt;/a&gt; on June 21st, 2016. We encourage you to skip v201601 and migrate straight to v201603.&lt;br /&gt;&lt;br /&gt; As with every new version of the AdWords API, we encourage you to carefully review all changes in the &lt;a href="https://developers.google.com/adwords/api/docs/reference/#v201603"&gt;release notes&lt;/a&gt; and the &lt;a href="https://developers.google.com/adwords/api/docs/guides/migration/v201603"&gt;v201603 migration guide&lt;/a&gt;. The updated &lt;a href="https://developers.google.com/adwords/api/docs/clientlibraries"&gt;client libraries&lt;/a&gt; and code examples will be published shortly. With this release, we’ve also updated the &lt;a href="https://developers.google.com/adwords/api/docs/requirements"&gt;Required Minimum Functionality document&lt;/a&gt; to include some of the newly added features.&lt;br /&gt;&lt;br /&gt; If you have any questions or need help with migration, please post on the &lt;a href="https://developers.google.com/adwords/api/community/"&gt;forum&lt;/a&gt; or the &lt;a href="https://plus.google.com/+GoogleAdsDevelopers"&gt;Ads Developers Plus Page&lt;/a&gt;.&lt;br /&gt; &lt;span class='byline-author'&gt;&lt;img height="40" width="40" src="https://lh5.googleusercontent.com/ibeUI_8AfTMqP8C6MzGeu8neKIdTgjjffkt4vIFiwlHjlyAeF-_9zLRfKL8N8X2DQJ5nqH5BJdRUhso-ghq6fvQlVsw1no1d9KWj-iiRbBFZJBcLKowhH4awsvGh3Kdt5PlLJOk2" style="vertical-align: middle; border:none;"/&gt; - &lt;a href="https://plus.google.com/100205313733177937765/posts"&gt;Josh Radcliff&lt;/a&gt; &lt;a href="https://plus.google.com/100205313733177937765/posts"&gt;on behalf of&lt;/a&gt; the AdWords API Team&lt;/span&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/Vc2DoXlTW5E" height="1" width="1" alt=""/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/3674747235433591015" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/3674747235433591015" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/lQlzL/~3/Vc2DoXlTW5E/announcing-v201603-of-adwords-api.html" title="Announcing v201603 of the AdWords API" /><author><name>Google Ads Developer Advisor</name><uri>http://www.blogger.com/profile/16700526826531306391</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img1.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googleadsdeveloper.blogspot.com/2016/03/announcing-v201603-of-adwords-api.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-7815614485808579332.post-6671727386258114671</id><published>2016-03-15T11:04:00.000-07:00</published><updated>2016-03-15T11:04:13.427-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api" /><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api_v201506" /><category scheme="http://www.blogger.com/atom/ns#" term="sunset" /><title type="text">AdWords API v201506 sunset reminder</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;&lt;b&gt;AdWords API v201506 will be &lt;a href="https://developers.google.com/adwords/api/docs/sunset-dates"&gt;sunset&lt;/a&gt; on April 11, 2016, after which all v201506 API requests will begin to fail.&lt;/b&gt; This version was &lt;a href="http://googleadsdeveloper.blogspot.com/2015/10/announcing-v201509-of-adwords-api.html"&gt;deprecated&lt;/a&gt; on October 5, 2015. If you are still on v201506, we recommend that you migrate directly to &lt;a href="http://googleadsdeveloper.blogspot.com/2016/02/announcing-v201601-of-adwords-api.html"&gt;v201601&lt;/a&gt; and skip v201509. Please be sure to migrate prior to sunset to ensure your API access is unaffected.&lt;br /&gt;&lt;br /&gt; We've prepared various resources to help you with the migration: &lt;ul&gt; &lt;li&gt;&lt;a href="https://developers.google.com/adwords/api/docs/guides/migration/v201601"&gt;v201601 migration guide&lt;/a&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="https://developers.google.com/adwords/api/docs/guides/migration/v201509"&gt;v201509 migration guide&lt;/a&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="https://developers.google.com/adwords/api/docs/reference/"&gt;Release notes&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt; As always, if you have any questions about this migration, please contact us via the &lt;a href="https://groups.google.com/forum/#!forum/adwords-api"&gt;forum&lt;/a&gt; or the &lt;a href="https://plus.google.com/+GoogleAdsDevelopers"&gt;Ads Developers Plus Page&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt; &lt;span class='byline-author'&gt;- Michael Cloonan, AdWords API Team&lt;/span&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/_U0ArPZ3rZE" height="1" width="1" alt=""/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/6671727386258114671" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/6671727386258114671" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/lQlzL/~3/_U0ArPZ3rZE/adwords-api-v201506-sunset-reminder.html" title="AdWords API v201506 sunset reminder" /><author><name>Google Ads Developer Advisor</name><uri>http://www.blogger.com/profile/16700526826531306391</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img1.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googleadsdeveloper.blogspot.com/2016/03/adwords-api-v201506-sunset-reminder.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-7815614485808579332.post-8235642486446853934</id><published>2016-03-04T08:09:00.000-08:00</published><updated>2016-03-04T08:09:38.295-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api" /><category scheme="http://www.blogger.com/atom/ns#" term="keywords" /><category scheme="http://www.blogger.com/atom/ns#" term="optimization" /><title type="text">Introducing the Keyword Optimizer sample app for the AdWords API</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;In AdWords, &lt;a href="https://support.google.com/adwords/answer/2453981"&gt;finding the right keywords&lt;/a&gt; to trigger your ads is one of the main drivers of success — yet a major challenge at the same time. You can use our &lt;a href="https://www.google.com.au/url?sa=t&amp;amp;rct=j&amp;amp;q=&amp;amp;esrc=s&amp;amp;source=web&amp;amp;cd=1&amp;amp;cad=rja&amp;amp;uact=8&amp;amp;ved=0ahUKEwjw9aa-5f_KAhVJHJQKHWVnBxAQFggpMAA&amp;amp;url=https%3A%2F%2Fadwords.google.com.au%2FKeywordPlanner&amp;amp;usg=AFQjCNGJBEDUw_j_nl94guRv8A_2fqiX1Q&amp;amp;sig2=Jx2M4NT-wa7_9jzP2ML-gw"&gt;Keyword Planner&lt;/a&gt; to browse for new keyword ideas, or utilize the AdWords API services for &lt;a href="https://developers.google.com/adwords/api/docs/guides/targeting-idea-service"&gt;keyword suggestion&lt;/a&gt; and &lt;a href="https://developers.google.com/adwords/api/docs/guides/traffic-estimator-service"&gt;traffic estimation&lt;/a&gt; to find and evaluate keywords at scale.&lt;br /&gt;&lt;br /&gt; But wait, now there’s more! We’ve just released &lt;a href="https://github.com/googleads/keyword-optimizer"&gt;KeywordOptimizer&lt;/a&gt;, a sample app showcasing how to combine these services to find the perfect set of keywords. Starting from an initial set of seed keywords (obtained using a sample URL, business category etc.), the iterative process repeatedly discards low-quality keywords and “reproduces” high-quality ones. With each step, the average quality across all keywords increases, just like evolution!&lt;br /&gt;&lt;br /&gt; KeywordOptimizer is designed to provide guidance on how to use the &lt;a href="https://developers.google.com/adwords/api/docs/guides/targeting-idea-service"&gt;TargetingIdeaService&lt;/a&gt; and &lt;a href="https://developers.google.com/adwords/api/docs/guides/traffic-estimator-service"&gt;TrafficEstimatorService&lt;/a&gt;. Simply &lt;a href="https://github.com/googleads/keyword-optimizer#run-keywordoptimizer"&gt;run it from the command-line&lt;/a&gt; to get a CSV file with keywords and estimation with minimal effort. Advanced users can easily extend the tool with custom implementations. For example, you can change the calculation for the keyword quality score to combine clicks with impressions, or your own metrics in a way that works best for you.&lt;br /&gt;&lt;br /&gt; Get started with Keyword Optimizer’s &lt;a href="https://github.com/googleads/keyword-optimizer"&gt;GitHub repository&lt;/a&gt;. Feel free to ask questions or give feedback via the &lt;a href="https://github.com/googleads/keyword-optimizer/issues"&gt;project’s issue tracker&lt;/a&gt;, the &lt;a href="https://groups.google.com/forum/#!forum/adwords-api"&gt;AdWords API Forum&lt;/a&gt;, or our &lt;a href="https://plus.google.com/115658573333388777174/posts/bA8W5r3KwZb"&gt;Google+ page&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt; &lt;span class='byline-author'&gt;&lt;img height="40" width="40" src="https://lh6.googleusercontent.com/NnTtEceqgWG8J0LxDn85MZTHvrhr2YIF4KwMHJB_QtBnyhBaFKarUAEWXEm2ffsuuFkRqxm7Sh1Wgk_aRqxdg4beKNyz6MG-xyhCLZdwI7JjvL-sqKYfH_yS_nU7Hsnq1kP8IOQg" style="vertical-align: middle; border:none;"/&gt; Timo Bozsolik, AdWords API Team&lt;/span&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/lo-Ues0KQ2A" height="1" width="1" alt=""/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/8235642486446853934" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/8235642486446853934" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/lQlzL/~3/lo-Ues0KQ2A/introducing-keyword-optimizer-sample.html" title="Introducing the Keyword Optimizer sample app for the AdWords API" /><author><name>Google Ads Developer Advisor</name><uri>http://www.blogger.com/profile/16700526826531306391</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img1.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googleadsdeveloper.blogspot.com/2016/03/introducing-keyword-optimizer-sample.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-7815614485808579332.post-6226147313744312031</id><published>2016-02-22T09:44:00.000-08:00</published><updated>2016-02-22T09:46:06.111-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api" /><category scheme="http://www.blogger.com/atom/ns#" term="dfp_api" /><category scheme="http://www.blogger.com/atom/ns#" term="php" /><title type="text">Announcing BETA release of the new Ads PHP Client Library</title><content type="html">&lt;p&gt;Today we're pleased to announce that we have released an updated &lt;a target="_blank" href="https://github.com/googleads/googleads-php-lib/tree/experimental"&gt;BETA version&lt;/a&gt; of the &lt;a target="_blank" href="https://github.com/googleads/googleads-php-lib/"&gt;Ads PHP Client Library&lt;/a&gt;. This is the first step in completely refactoring the Ads PHP Client Library to adhere to modern PHP standards. Major changes include: &lt;ul&gt;&lt;li&gt;Namespaced and conforms to &lt;a target="_blank" href="http://www.php-fig.org/psr/psr-4/"&gt;PSR-4&lt;/a&gt; for autoloading.&lt;/li&gt;&lt;li&gt;Conforms to &lt;a target="_blank" href="http://www.php-fig.org/psr/psr-3/"&gt;PSR-3&lt;/a&gt; for logging standards.&lt;/li&gt;&lt;li&gt;Entry point classes use a builder pattern for their construction.&lt;/li&gt;&lt;li&gt;Core class design is composition-based instead of inheritance-based.&lt;/li&gt;&lt;li&gt;Classes generated from WSDLs now use getters and setters for accessing fields.&lt;/li&gt;&lt;/ul&gt; &lt;p&gt;To get started with this new library, please see the &lt;a target="_blank" href="https://github.com/googleads/googleads-php-lib/blob/experimental/README.md#getting-started"&gt;README's "Basic usage"&lt;/a&gt; section. &lt;p&gt;As a reminder, since this new client library is in BETA, it is &lt;b&gt;not yet recommended&lt;/b&gt; for production usage. We do however recommend that you test it out, play around with it, and give us your feedback on the &lt;a target="_blank" href="https://github.com/googleads/googleads-php-lib/labels/beta"&gt;issue tracker&lt;/a&gt;. &lt;p&gt;Stay tuned for more changes to this BETA library in the coming year. &lt;p&gt;As always, if you have any questions, feel free to drop us a line on the &lt;a target="_blank" href="https://groups.google.com/forum/#!forum/adwords-api"&gt;AdWords API forums&lt;/a&gt;, &lt;a target="_blank" href="https://groups.google.com/forum/#!forum/google-doubleclick-for-publishers-api"&gt;DFP API forums&lt;/a&gt; or the &lt;a target="_blank" href="https://plus.google.com/+GoogleAdsDevelopers/posts"&gt;Ads Developer Google+ page&lt;/a&gt;. &lt;p&gt;&lt;span class='byline-author'&gt;&lt;a target="_blank" href="https://plus.google.com/u/0/+VincentTsao"&gt;&lt;img width="40" height="40" src="https://lh3.googleusercontent.com/-I5VHr9twxlU/AAAAAAAAAAI/AAAAAAAABoc/XKIvgIIEw7I/s120-c/photo.jpg" style="vertical-align:middle; border:none;"&gt;&lt;/a&gt;&amp;nbsp;-&amp;nbsp;&lt;a target="_blank" href="https://plus.google.com/u/0/+VincentTsao" rel="author"&gt;Vincent Tsao&lt;/a&gt;, DFP API Team&lt;/span&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/4fL4sqBFJ7Q" height="1" width="1" alt=""/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/6226147313744312031" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/6226147313744312031" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/lQlzL/~3/4fL4sqBFJ7Q/announcing-beta-release-of-new-ads-php.html" title="Announcing BETA release of the new Ads PHP Client Library" /><author><name>Google Ads Developer Advisor</name><uri>http://www.blogger.com/profile/16700526826531306391</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img1.blogblog.com/img/b16-rounded.gif" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://lh3.googleusercontent.com/-I5VHr9twxlU/AAAAAAAAAAI/AAAAAAAABoc/XKIvgIIEw7I/s72-c/photo.jpg" height="72" width="72" /><feedburner:origLink>http://googleadsdeveloper.blogspot.com/2016/02/announcing-beta-release-of-new-ads-php.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-7815614485808579332.post-5230697490054376322</id><published>2016-02-17T07:01:00.001-08:00</published><updated>2016-02-17T07:01:11.915-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="adwords" /><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api" /><category scheme="http://www.blogger.com/atom/ns#" term="adwords_scripts" /><category scheme="http://www.blogger.com/atom/ns#" term="upgraded_urls" /><title type="text">Reminder: Upgrade your AdWords destination URLs by March 25th, 2016</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;We would like to remind you to &lt;a href="http://googleadsdeveloper.blogspot.com/2015/02/announcing-upgraded-urls-for-adwords-api.html"&gt;upgrade&lt;/a&gt; destination URLs for ads, criteria, and sitelinks by &lt;b&gt;March 25, 2016.&lt;/b&gt;&lt;br /&gt;&lt;br /&gt; Shortly after &lt;b&gt;March 25, 2016&lt;/b&gt;, we will apply the following changes to the ads, criteria, and extensions in your account that have not been upgraded: &lt;ul&gt; &lt;li&gt;&lt;b&gt;Ads and sitelinks&lt;/b&gt; will be permanently designated as “Removed” and will stop serving. In rare cases, destination URLs for ads may be upgraded for you, which may impact how your ads run.&lt;/li&gt; &lt;li&gt;&lt;b&gt;Destination URLs&lt;/b&gt; for your keywords will be removed. Clicks on your ads for these keywords will go to the ad's landing page. You'll need to set up new &lt;a href="https://support.google.com/adwords/answer/2404246#kw"&gt;landing page URLs&lt;/a&gt; and &lt;a href="https://support.google.com/adwords/answer/6273460"&gt;tracking&lt;/a&gt; parameters.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Note&lt;/b&gt;: Dynamic Display Ads, Gmail Sponsored Promotion, and Lightbox ads are not impacted by this change and will continue to serve.&lt;/li&gt;&lt;/ul&gt; &lt;font size="4"&gt;How to upgrade your remaining destination URLs&lt;/font&gt;&lt;br /&gt; To ensure your existing ads continue to run and your URL tracking works as expected, you'll need to: &lt;ul&gt; &lt;li&gt;&lt;a href="https://developers.google.com/adwords/api/docs/guides/upgraded-urls#identify_destination_urls_to_migrate"&gt;Identify&lt;/a&gt; all remaining &lt;b&gt;enabled&lt;/b&gt; or &lt;b&gt;paused&lt;/b&gt; destination URLs within your account that require an upgrade.&lt;/li&gt; &lt;li&gt;Upgrade your destination URLs by following the &lt;a href="https://developers.google.com/adwords/api/docs/guides/upgraded-urls#migrate_to_upgraded_urls"&gt;steps in the Upgraded URL guide&lt;/a&gt;.&lt;/li&gt;&lt;/ul&gt; &lt;font size="4"&gt;What if I can’t upgrade in time?&lt;/font&gt;&lt;br /&gt; If you do not plan to upgrade destination URLs by &lt;b&gt;March 25, 2016&lt;/b&gt; or wish to keep the destination URL details for future use, then we advise you to download the ads, criteria and extensions that are not upgraded using an &lt;a href="https://developers.google.com/adwords/api/docs/guides/upgraded-urls#download_entities"&gt;appropriate AdWords API service&lt;/a&gt;. Destination URL data is accessible for now via &lt;a href="https://developers.google.com/adwords/api/docs/appendix/reports"&gt;AdWords API reports&lt;/a&gt; and services, but this field will be removed in a future version of the AdWords API.&lt;br /&gt;&lt;br /&gt; If you have any questions or need help with migration, please post on our &lt;a href="https://developers.google.com/adwords/api/community/"&gt;developer forum&lt;/a&gt; or the &lt;a href="https://plus.google.com/+GoogleAdsDevelopers"&gt;Ads Developers Plus Page&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt; &lt;span class='byline-author'&gt;&lt;img height="40" width="40" src="https://lh5.googleusercontent.com/US8gT-L1ezuhsR3DCqe3ftoAbLfUf4KOrWNKiIT_P2sWrIiU8sDFc0OFslnP_oBpsBxVL1BtKFCir64YAwCOUJ_9TB9ihHzkstEU7o8F4Wv-mWjMJlqWMGjzbQlUDYas_KTtB_QM" style="vertical-align: middle; border:none;"/&gt; Anash P. Oommen, AdWords API Team&lt;/span&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/Ys4XcOEvYwU" height="1" width="1" alt=""/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/5230697490054376322" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/5230697490054376322" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/lQlzL/~3/Ys4XcOEvYwU/reminder-upgrade-your-adwords.html" title="Reminder: Upgrade your AdWords destination URLs by March 25th, 2016" /><author><name>Google Ads Developer Advisor</name><uri>http://www.blogger.com/profile/16700526826531306391</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img1.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googleadsdeveloper.blogspot.com/2016/02/reminder-upgrade-your-adwords.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-7815614485808579332.post-1835690356711460161</id><published>2016-02-02T12:05:00.001-08:00</published><updated>2016-02-02T12:05:20.551-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api" /><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api_v201601" /><category scheme="http://www.blogger.com/atom/ns#" term="release" /><title type="text">Announcing v201601 of the AdWords API</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;Today we’re announcing the release of &lt;a href="https://developers.google.com/adwords/api/docs/reference/#v201601"&gt;AdWords API v201601&lt;/a&gt;. This is the first release that follows the &lt;a href="http://googleadsdeveloper.blogspot.com/2016/01/new-release-schedule-for-adwords-api.html"&gt;new release schedule announced earlier this month&lt;/a&gt;. Here are the highlights: &lt;ul&gt; &lt;li&gt;&lt;b&gt;Reporting improvements.&lt;/b&gt; Several new fields were added to the &lt;a href="https://developers.google.com/adwords/api/docs/appendix/reports/video-performance-report"&gt;VIDEO_PERFORMANCE_REPORT&lt;/a&gt;. New quality score and first position bid fields were added to the &lt;a href="https://developers.google.com/adwords/api/docs/appendix/reports/criteria-performance-report"&gt;CRITERIA_PERFORMANCE_REPORT&lt;/a&gt; and &lt;a href="https://developers.google.com/adwords/api/docs/appendix/reports/keywords-performance-report"&gt;KEYWORDS_PERFORMANCE_REPORT&lt;/a&gt;, and a new &lt;a href="https://developers.google.com/adwords/api/docs/appendix/reports/parental-status-performance-report"&gt;PARENTAL_STATUS_PERFORMANCE_REPORT&lt;/a&gt; was added. See the &lt;a href="https://developers.google.com/adwords/api/docs/reference/#v201601-reporting"&gt;reporting section of the release notes&lt;/a&gt; for the complete list of changes, including all fields removed or added in this release.&lt;/li&gt; &lt;li&gt;&lt;b&gt;Improved batch processing.&lt;/b&gt; The &lt;a href="https://developers.google.com/adwords/api/docs/reference/v201601/BatchJobService"&gt;BatchJobService&lt;/a&gt; was improved to reduce latency when uploading operations for a job. Check out the updated &lt;a href="https://developers.google.com/adwords/api/docs/guides/batch-jobs"&gt;Batch Processing guide&lt;/a&gt; for details.&lt;/li&gt; &lt;li&gt;&lt;b&gt;Managing customer accounts.&lt;/b&gt; You can now update the &lt;a href="https://developers.google.com/adwords/api/docs/reference/v201601/ManagedCustomerService.ManagedCustomer#name"&gt;ManagedCustomer.name&lt;/a&gt; of accounts under your account manager using a &lt;code&gt;SET&lt;/code&gt; operation.&lt;/li&gt; &lt;li&gt;&lt;b&gt;Advanced conversions.&lt;/b&gt; You can control whether the Conversions column and conversion-based bid strategies &lt;a href="https://support.google.com/adwords/answer/6238665"&gt;include cross-device conversions&lt;/a&gt; via the new &lt;a href="https://developers.google.com/adwords/api/docs/reference/v201601/CustomerService.ConversionTrackingSettings#optimizeonestimatedconversions"&gt;optimizeOnEstimatedConversions&lt;/a&gt; attribute of &lt;a href="https://developers.google.com/adwords/api/docs/reference/v201601/CustomerService.Customer#conversiontrackingsettings"&gt;Customer.conversionTrackingSettings&lt;/a&gt;.&lt;/li&gt; &lt;li&gt;&lt;b&gt;Enhanced CPC bidding.&lt;/b&gt; Setting the &lt;a href="https://developers.google.com/adwords/api/docs/reference/v201601/BiddingStrategyService.ManualCpcBiddingScheme#enhancedcpcenabled"&gt;enhancedCpcEnabled attribute&lt;/a&gt; of a &lt;code&gt;ManualCpcBiddingScheme&lt;/code&gt; is now supported in the API. Previously, this setting was read-only.&lt;/li&gt; &lt;li&gt;&lt;b&gt;Targeting.&lt;/b&gt; The new &lt;a href="https://developers.google.com/adwords/api/docs/reference/v201601/CampaignCriterionService.Parent"&gt;Parent&lt;/a&gt; criteria type is available for targeting and bidding according to a user's parental status on the Display Network. In addition, &lt;a href="https://developers.google.com/adwords/api/docs/reference/v201601/ConstantDataService"&gt;ConstantDataService&lt;/a&gt; now supports retrieving the lists of &lt;a href="https://developers.google.com/adwords/api/docs/appendix/mobileappcategories"&gt;mobile app category&lt;/a&gt; and &lt;a href="https://developers.google.com/adwords/api/docs/appendix/smartphone-userinterest"&gt;new smartphone user&lt;/a&gt; criteria.&lt;/li&gt;&lt;/ul&gt; If you’re using v201506 of the AdWords API, please note that it’s &lt;a href="https://developers.google.com/adwords/api/docs/sunset-dates"&gt;being sunset&lt;/a&gt; on April 11th, 2016 as &lt;a href="http://googleadsdeveloper.blogspot.com/2015/10/announcing-v201509-of-adwords-api.html"&gt;previously announced&lt;/a&gt;. We encourage you to skip v201509 and migrate straight to v201601.&lt;br /&gt;&lt;br /&gt; As with every new version of the AdWords API, we encourage you to carefully review all changes in the &lt;a href="https://developers.google.com/adwords/api/docs/reference/#v201601"&gt;release notes&lt;/a&gt; and the &lt;a href="https://developers.google.com/adwords/api/docs/guides/migration/v201601"&gt;v201601 migration guide&lt;/a&gt;. The updated &lt;a href="https://developers.google.com/adwords/api/docs/clientlibraries"&gt;client libraries&lt;/a&gt; and code examples will be published shortly. With this release, we’ve also updated the &lt;a href="https://developers.google.com/adwords/api/docs/requirements"&gt;Required Minimum Functionality document&lt;/a&gt; to include some of the newly added features.&lt;br /&gt;&lt;br /&gt; If you have any questions or need help with migration, please post on the &lt;a href="https://developers.google.com/adwords/api/community/"&gt;forum&lt;/a&gt; or the &lt;a href="https://plus.google.com/+GoogleAdsDevelopers"&gt;Ads Developers Plus Page&lt;/a&gt;. &lt;br /&gt;&lt;br /&gt; &lt;span class='byline-author'&gt;&lt;img height="40" width="40" src="https://lh6.googleusercontent.com/uiRP8dQcYRiuOOO6pbpueHAA54OYiopuNiaJTESmUs8kTsFPocly04JsfEC99uDW4JfrOwaqFUu8FiB8DahD-IcxGQoawwx5vMcdPbCs5dwnvVU5R1nnAWnouLs940tPplMaDtLi" style="vertical-align: middle; border:none;"/&gt; - &lt;a href="https://plus.google.com/100205313733177937765/posts"&gt;Josh Radcliff&lt;/a&gt; on behalf of the AdWords API Team.&lt;/span&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/cWkNNrcQkw4" height="1" width="1" alt=""/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/1835690356711460161" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/1835690356711460161" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/lQlzL/~3/cWkNNrcQkw4/announcing-v201601-of-adwords-api.html" title="Announcing v201601 of the AdWords API" /><author><name>Google Ads Developer Advisor</name><uri>http://www.blogger.com/profile/16700526826531306391</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img1.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googleadsdeveloper.blogspot.com/2016/02/announcing-v201601-of-adwords-api.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-7815614485808579332.post-6398731188152304435</id><published>2016-02-01T07:44:00.000-08:00</published><updated>2016-02-01T07:44:09.318-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api" /><category scheme="http://www.blogger.com/atom/ns#" term="geotargeting" /><category scheme="http://www.blogger.com/atom/ns#" term="location_extensions" /><category scheme="http://www.blogger.com/atom/ns#" term="sunset" /><title type="text">Adjusting the manual location extension sunset</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;In October 2015, we &lt;a href="http://googleadsdeveloper.blogspot.com.au/2015/10/using-google-my-business-api-to-manage.html"&gt;announced the Google My Business API&lt;/a&gt; and the sunset of manual location extensions in AdWords. To give developers more time to migrate their locations from AdWords to Google My Business, we have decided to &lt;b&gt;extend the manual location extensions sunset and voluntary migration deadline beyond March 31&lt;/b&gt;. Existing locations in AdWords will not be auto-migrated until further notice. We will announce the revised sunset timeline and more details about auto-migration on this blog at a future date. Apologies for any inconvenience, please &lt;a href="https://groups.google.com/forum/#!forum/adwords-api"&gt;contact us&lt;/a&gt; if you have any questions.&lt;br /&gt;&lt;br /&gt; &lt;span class='byline-author'&gt;&lt;img height="40" width="40" src="https://lh6.googleusercontent.com/M20O4JpdxCNvk8YCb5zR93Vr1PkP2GVxzabllrHDJ3-z_le5QoUOeAqgTmOnvognoR-KTAzRiJnNsM4nRlKfCL6Sft2GDuhQjClQuzoKQYYRwetNj-uV7CJ-C3Jo8a2nV7tPdNge" style="vertical-align: middle; border:none;"/&gt; Timo Bozsolik, AdWords API Team&lt;/span&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/_dbWK1jx4Rg" height="1" width="1" alt=""/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/6398731188152304435" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/6398731188152304435" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/lQlzL/~3/_dbWK1jx4Rg/adjusting-manual-location-extension.html" title="Adjusting the manual location extension sunset" /><author><name>Google Ads Developer Advisor</name><uri>http://www.blogger.com/profile/16700526826531306391</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img1.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googleadsdeveloper.blogspot.com/2016/02/adjusting-manual-location-extension.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-7815614485808579332.post-2372731558118812465</id><published>2016-01-12T02:56:00.000-08:00</published><updated>2016-01-13T08:08:56.521-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api" /><category scheme="http://www.blogger.com/atom/ns#" term="new_features" /><category scheme="http://www.blogger.com/atom/ns#" term="release" /><category scheme="http://www.blogger.com/atom/ns#" term="sunset" /><title type="text">New release schedule for AdWords API</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;In response to overwhelming feedback from our most active developers, we're announcing that we will begin releasing new versions of the AdWords API more frequently on an experimental basis, compared to the current &lt;i&gt;three-times-a-year&lt;/i&gt; schedule. Starting at the end of January 2016, API releases will occur at the end of every alternate month, continuing through March, May, July, and September. We will reassess the cost and benefits of this release schedule to the developer community throughout the experiment and determine whether to continue with it or fall back to the current three-times-a-year schedule.&lt;br /&gt;&lt;br /&gt;We believe that delivering API releases more frequently will help you, the API users, get quicker access to AdWords innovations for making continuous improvements to your tools and platforms.&lt;br /&gt;&lt;br /&gt;Each of these releases will be considered a major release and will trigger the deprecation of the oldest outstanding major release. Previously, we supported 2 releases concurrently at any given time, and 3 releases for a brief period of 4 weeks to help you skip a major release entirely. With the new release schedule, we will support 3 releases concurrently at any given time and 4 releases for a brief period of 4 weeks to accommodate developers who want to skip &lt;b&gt;two&lt;/b&gt; major releases entirely. Overall, every AdWords API version will still be available for roughly the same time period as before.&lt;br /&gt;&lt;br /&gt;The new experimental schedule will result in the following releases: &lt;br /&gt;&lt;br /&gt;&lt;table style="border-collapse: collapse; border: none;"&gt;&lt;colgroup&gt;&lt;col width="25%"&gt;&lt;/col&gt;&lt;col width="25%"&gt;&lt;/col&gt;&lt;col width="25%"&gt;&lt;/col&gt;&lt;col width="25%"&gt;&lt;/col&gt;&lt;/colgroup&gt;&lt;tbody&gt;&lt;tr style="background-color: #6199df; border-bottom: solid #4d90fe 1px; border-left: solid #4d90fe 1px; border-right: solid #4d90fe 1px; border-top: solid #4d90fe 1px; height: 0px; vertical-align: top;"&gt; &lt;th style="border-bottom: solid #4d90fe 1px; border-left: solid #4d90fe 1px; border-right: solid #4d90fe 1px; border-top: solid #4d90fe 1px; padding: 7px 7px 7px 7px;"&gt;&lt;span style="color: white;"&gt;New Release&lt;/span&gt;&lt;br /&gt;&lt;i&gt;&lt;span style="color: white;"&gt;(recommended)&lt;/span&gt;&lt;/i&gt;&lt;/th&gt; &lt;th style="border-bottom: solid #4d90fe 1px; border-left: solid #4d90fe 1px; border-right: solid #4d90fe 1px; border-top: solid #4d90fe 1px; padding: 7px 7px 7px 7px;"&gt;&lt;span style="color: white;"&gt;Old Release&lt;/span&gt;&lt;br /&gt;&lt;i&gt;&lt;span style="color: white;"&gt;(supported, just not the latest)&lt;/span&gt;&lt;/i&gt;&lt;/th&gt; &lt;th style="border-bottom: solid #4d90fe 1px; border-left: solid #4d90fe 1px; border-right: solid #4d90fe 1px; border-top: solid #4d90fe 1px; padding: 7px 7px 7px 7px;"&gt;&lt;span style="color: white;"&gt;Deprecated Release&lt;/span&gt;&lt;br /&gt;&lt;i&gt;&lt;span style="color: white;"&gt;(supported, but going away soon)&lt;/span&gt;&lt;/i&gt;&lt;/th&gt; &lt;th style="border-bottom: solid #4d90fe 1px; border-left: solid #4d90fe 1px; border-right: solid #4d90fe 1px; border-top: solid #4d90fe 1px; padding: 7px 7px 7px 7px;"&gt;&lt;span style="color: white;"&gt;Sunset Release&lt;/span&gt;&lt;br /&gt;&lt;i&gt;&lt;span style="color: white;"&gt;(not supported 4 weeks after new release date)&lt;/span&gt;&lt;/i&gt;&lt;/th&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: middle;"&gt;&lt;b&gt;January 2016&lt;/b&gt;&lt;/td&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: middle;"&gt;September 2015&lt;/td&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: middle;"&gt;June 2015&lt;/td&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: middle;"&gt;—&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: middle;"&gt;March 2016&lt;/td&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: middle;"&gt;&lt;b&gt;January 2016&lt;/b&gt;&lt;/td&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: middle;"&gt;September 2015&lt;/td&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: middle;"&gt;June 2015&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: middle;"&gt;May 2016&lt;/td&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: middle;"&gt;March 2016&lt;/td&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: middle;"&gt;&lt;b&gt;January 2016&lt;/b&gt;&lt;/td&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: middle;"&gt;September 2015&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: middle;"&gt;July 2016&lt;/td&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: middle;"&gt;May 2016&lt;/td&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: middle;"&gt;March 2016&lt;/td&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: middle;"&gt;&lt;b&gt;January 2016&lt;/b&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: middle;"&gt;September 2016&lt;/td&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: middle;"&gt;July 2016&lt;/td&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: middle;"&gt;May 2016&lt;/td&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: middle;"&gt;March 2016&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;br /&gt;Our current published &lt;a href="https://developers.google.com/adwords/api/docs/sunset-dates"&gt;sunset schedule&lt;/a&gt; remains unaffected. The &lt;a href="http://googleadsdeveloper.blogspot.com/2015/06/announcing-v201506-of-adwords-api.html"&gt;v201506&lt;/a&gt; release will be sunset on 11 April 2016 as previously announced. The &lt;a href="http://googleadsdeveloper.blogspot.com/2015/10/announcing-v201509-of-adwords-api.html"&gt;v201509&lt;/a&gt; release will continue to be supported concurrently with the v201601 release and will be deprecated once the v201603 release is announced. &lt;br /&gt;&lt;br /&gt;If you have any questions about this announcement please post them on the &lt;a href="https://groups.google.com/forum/#!forum/adwords-api"&gt;forum&lt;/a&gt;. &lt;br /&gt;&lt;br /&gt;&lt;span class='byline-author'&gt;- Vishal Goenka, Senior Product Manager, AdWords API Team&lt;/span&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/2o8ZNtoKrZc" height="1" width="1" alt=""/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/2372731558118812465" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/2372731558118812465" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/lQlzL/~3/2o8ZNtoKrZc/new-release-schedule-for-adwords-api.html" title="New release schedule for AdWords API" /><author><name>Google Ads Developer Advisor</name><uri>http://www.blogger.com/profile/16700526826531306391</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img1.blogblog.com/img/b16-rounded.gif" /></author><georss:featurename>Mountain View, CA, USA</georss:featurename><georss:point>37.3860517 -122.0838511</georss:point><georss:box>37.285155700000004 -122.2452126 37.4869477 -121.9224896</georss:box><feedburner:origLink>http://googleadsdeveloper.blogspot.com/2016/01/new-release-schedule-for-adwords-api.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-7815614485808579332.post-1536168540891180105</id><published>2016-01-05T07:26:00.001-08:00</published><updated>2016-01-05T07:26:41.910-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api" /><category scheme="http://www.blogger.com/atom/ns#" term="adwords_BatchJobService" /><category scheme="http://www.blogger.com/atom/ns#" term="adwords_MutateJobService" /><title type="text">Migrate from MutateJobService to BatchJobService before v201509 sunsets</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;&lt;font size="4"&gt;What do I need to do now?&lt;/font&gt;&lt;br /&gt;&lt;br /&gt; AdWords API versions after v201509 will no longer support &lt;a href="https://developers.google.com/adwords/api/docs/reference/v201509/MutateJobService"&gt;MutateJobService&lt;/a&gt;. Migrate to &lt;a href="https://developers.google.com/adwords/api/docs/reference/latest/BatchJobService"&gt;BatchJobService&lt;/a&gt;, &lt;a href="http://googleadsdeveloper.blogspot.com/2015/10/announcing-v201509-of-adwords-api.html"&gt;introduced&lt;/a&gt; in v201509, as soon as you can. For sunset dates, check out our &lt;a href="https://developers.google.com/adwords/api/docs/sunset-dates"&gt;Deprecation Schedule&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt; &lt;font size="4"&gt;What’s new?&lt;/font&gt;&lt;br /&gt;&lt;br /&gt; &lt;code&gt;BatchJobService&lt;/code&gt; supports all of the same operations as &lt;code&gt;MutateJobService&lt;/code&gt;. Plus, we’ve provided some improvements: &lt;ul&gt; &lt;li&gt;Creation of dependent objects using temporary IDs &lt;ul&gt;&lt;li&gt;For example, you can create an entire campaign including ad groups and criteria in one job.&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt; &lt;li&gt;Improved performance&lt;/li&gt; &lt;li&gt;Better error reporting &lt;ul&gt;&lt;li&gt;If some operations failed, the errors returned by BatchJobService are correlated with those operations, making it easier to understand what went wrong.&lt;/li&gt; &lt;li&gt;If the service was unable to process any operations, it returns a detailed list of errors.&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="https://developers.google.com/adwords/api/docs/guides/batch-jobs#limitations"&gt;Higher limit&lt;/a&gt; on the number of operations per job &lt;ul&gt;&lt;li&gt;&lt;code&gt;BatchJobService&lt;/code&gt; supports potentially hundreds of thousands of operations.&lt;/li&gt; &lt;li&gt;&lt;code&gt;MutateJobService&lt;/code&gt; only supported thousands of operations.&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;/ul&gt; Check out our &lt;a href="https://developers.google.com/adwords/api/docs/guides/batch-jobs"&gt;Batch Processing guide&lt;/a&gt; for more details on these new features.&lt;br /&gt;&lt;br /&gt; &lt;font size="4"&gt;How do I migrate?&lt;/font&gt;&lt;br /&gt;&lt;br /&gt; Thanks to the new utilities we’ve created in our &lt;a href="https://developers.google.com/adwords/api/docs/clientlibraries"&gt;client libraries&lt;/a&gt;, migration will be a simple process of passing in your existing operations to the &lt;code&gt;BatchJobService&lt;/code&gt; rather than the &lt;code&gt;MutateJobService&lt;/code&gt;.&lt;br /&gt;&lt;br /&gt; Our guide has a section on &lt;a href="https://developers.google.com/adwords/api/docs/guides/batch-jobs#migrating_from_mutatejobservice"&gt;Migrating from MutateJobService&lt;/a&gt;. Each of our &lt;a href="https://developers.google.com/adwords/api/docs/clientlibraries"&gt;client libraries&lt;/a&gt; have &lt;a href="https://developers.google.com/adwords/api/docs/guides/batch-jobs#code_examples"&gt;code examples&lt;/a&gt; that include utilities for the &lt;code&gt;BatchJobService&lt;/code&gt;. The utilities in each of the client libraries do all of the heavy lifting for you, which will simplify your code and make the transition easier.&lt;br /&gt;&lt;br /&gt; &lt;font size="4"&gt;Where can I learn more?&lt;/font&gt;&lt;br /&gt;&lt;br /&gt; If you missed our Fall 2015 workshops, we have a &lt;code&gt;BatchJobService&lt;/code&gt; &lt;a href="https://youtu.be/qBCc-y59Euk?list=PLKByxjzUC-N8mEDQF9ARMMkSv0AmYbpsh"&gt;video&lt;/a&gt; with accompanying &lt;a href="http://www.slideshare.net/supergigas/batchjobservice"&gt;slides&lt;/a&gt; available on our &lt;a href="http://www.adwordsapiworkshops.com/"&gt;AdWords API Workshop site&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt; Questions? Visit us on the &lt;a href="https://groups.google.com/forum/#!forum/adwords-api"&gt;AdWords API Forum&lt;/a&gt; or our &lt;a href="https://plus.google.com/115658573333388777174/posts/bA8W5r3KwZb"&gt;Google+ page&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt; &lt;span class='byline-author'&gt;&lt;a href="https://plus.google.com/109542956637533475940/posts"&gt;&lt;img height="40" width="40" src="https://lh6.googleusercontent.com/WbNv4mDfIa4inextIF_mTmMEb9GCYsK99ojBCBm5J9i8o4972_Xl_2FkROQDC-3aoHyVW1lC50UPRSr1r4MiuNMR_WNI1U_po288VDA2y5zIM9K5rnJ7a6nQ8Udw_Gsq7uYpUO0x" style="vertical-align: middle; border:none;"/&gt; Nadine Sundquist&lt;/a&gt;, AdWords API Team&lt;/span&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/1tTBNHDMUtQ" height="1" width="1" alt=""/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/1536168540891180105" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/1536168540891180105" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/lQlzL/~3/1tTBNHDMUtQ/migrate-from-mutatejobservice-to.html" title="Migrate from MutateJobService to BatchJobService before v201509 sunsets" /><author><name>Google Ads Developer Advisor</name><uri>http://www.blogger.com/profile/16700526826531306391</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img1.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googleadsdeveloper.blogspot.com/2016/01/migrate-from-mutatejobservice-to.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-7815614485808579332.post-3120601886317203814</id><published>2015-12-17T07:12:00.000-08:00</published><updated>2015-12-17T07:12:36.719-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api" /><category scheme="http://www.blogger.com/atom/ns#" term="sunset" /><title type="text">Removing legacy geo targeting locations from AdWords API</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;Starting in January 2016, we’ll be cleaning up some older geo targeting locations in the AdWords API. On &lt;b&gt;January 21, 2016&lt;/b&gt;, the &lt;a href="https://developers.google.com/adwords/api/docs/reference/v201509/LocationCriterionService.Location#targetingstatus"&gt;targetingStatus&lt;/a&gt; of these locations will be changed to &lt;code&gt;PHASING_OUT&lt;/code&gt;, and they will be completely removed in an upcoming version of the API.&lt;br /&gt;&lt;br /&gt; Most of the targets we're removing are no longer used. However, there are a few with some traffic, and these largely fall into two categories: &lt;ul&gt; &lt;li&gt;Criteria that are duplicates of other criteria. You should migrate these as soon as possible for consistency. Any that are not migrated by the time the criteria are removed will be automatically migrated to the new criteria IDs.&lt;/li&gt; &lt;li&gt;Criteria that designate places that no longer exist, but previously were meaningful targets.&lt;/li&gt;&lt;/ul&gt; Please see our developers site for a &lt;a href="https://developers.google.com/adwords/api/geo-location-sunsets"&gt;complete list of IDs affected&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt; If you have any questions about this change, or other questions about the AdWords API, please contact us via the &lt;a href="https://groups.google.com/forum/#!forum/adwords-api"&gt;forum&lt;/a&gt; or the &lt;a href="https://plus.google.com/+GoogleAdsDevelopers"&gt;Ads Developers Plus Page&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt; &lt;span class='byline-author'&gt;- Michael Cloonan, AdWords API Team&lt;/span&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/DRiTMfgYeSk" height="1" width="1" alt=""/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/3120601886317203814" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/3120601886317203814" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/lQlzL/~3/DRiTMfgYeSk/removing-legacy-geo-targeting-locations.html" title="Removing legacy geo targeting locations from AdWords API" /><author><name>Google Ads Developer Advisor</name><uri>http://www.blogger.com/profile/16700526826531306391</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img1.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googleadsdeveloper.blogspot.com/2015/12/removing-legacy-geo-targeting-locations.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-7815614485808579332.post-6054834783852474791</id><published>2015-11-24T09:45:00.000-08:00</published><updated>2015-11-24T09:45:07.861-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api" /><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api_v201509" /><category scheme="http://www.blogger.com/atom/ns#" term="remarketing" /><title type="text">Reach your most valuable customers with Customer Match</title><content type="html">&lt;p&gt;Did you know that you can reach past website visitors and app users? Let's say you’re a travel brand. You can now reach people who have joined your rewards program as they plan their next trip. For example, when these rewards members search for “non-stop flights to new york” on Google.com, you can show relevant ads at the top of their search results on any device right when they’re looking to fly to New York. And when those members are watching their favorite videos on YouTube or catching up on Gmail, you can show ads that inspire them to plan their next trip.&lt;/p&gt; Behind the scenes, this works by adding people to a &lt;a href="https://developers.google.com/adwords/api/docs/reference/latest/AdwordsUserListService.UserList"&gt;UserList&lt;/a&gt;. &lt;p&gt;Prior to v201509 there were four different types:&lt;/p&gt;&lt;ul&gt; &lt;li&gt;&lt;a href="https://developers.google.com/adwords/api/docs/reference/latest/AdwordsUserListService.BasicUserList"&gt;BasicUserList&lt;/a&gt;: Remarketing to people who took specific actions (such as purchasing shoes) on your website or app.&lt;/li&gt; &lt;li&gt;&lt;a href="https://developers.google.com/adwords/api/docs/reference/latest/AdwordsUserListService.RuleBasedUserList"&gt;RuleBasedUserList&lt;/a&gt;: Remarketing to people who follow advertiser-defined rules. The rule can be as simple as all visitors to your website (which is the easiest way to start remarketing).&lt;/li&gt; &lt;li&gt;&lt;a href="https://developers.google.com/adwords/api/docs/reference/latest/AdwordsUserListService.LogicalUserList"&gt;LogicalUserList&lt;/a&gt;: Combining two or more user lists. For example, customers who purchased shoes and/or visited specific pages of your website at specific times.&lt;/li&gt; &lt;li&gt;&lt;a href="https://developers.google.com/adwords/api/docs/reference/latest/AdwordsUserListService.SimilarUserList"&gt;SimilarUserList&lt;/a&gt;: Remarketing to people that share similar interests and behaviors with those in other user lists. For example, you can reach new potential customers that share similar interests and behaviors with those who purchased shoes on your website.&lt;/li&gt;&lt;/ul&gt; &lt;p&gt;A &lt;code&gt;SimilarUserList&lt;/code&gt; is automatically created by Google for each &lt;code&gt;UserList&lt;/code&gt; based on a variety of factors, such as the number of people on the original list, how recently these people joined the original list, the types of sites that these people browsed and whether the original list is your own. This process may take up to 4 days once the seed list is created.&lt;/p&gt; &lt;p&gt;You can target or exclude user lists at the ad group level, but you can only exclude them at the campaign level.&lt;/p&gt; &lt;p&gt;As a reminder, please have a look at the &lt;a href="https://support.google.com/adwordspolicy/answer/143465"&gt;policy for advertising based on interests and location&lt;/a&gt; and the &lt;a href="https://support.google.com/adwordspolicy/answer/6242605"&gt;policy for remarketing lists for search ads&lt;/a&gt;.&lt;/p&gt; &lt;h2&gt;Customer Match&lt;/h2&gt; &lt;p&gt;v201509 introduced a new user list type: &lt;a href="https://developers.google.com/adwords/api/docs/reference/latest/AdwordsUserListService.CrmBasedUserList"&gt;CrmBasedUserList&lt;/a&gt;. It enables you to create a user list using your customers’ email addresses.&lt;/p&gt; &lt;p&gt;Suppose you have an existing database of email addresses of your newsletter subscribers for “people who love shoes”. With a &lt;code&gt;CrmBasedUserList&lt;/code&gt; you can reach these subscribers and adjust your bidding accordingly, present different ads, and more. You can use a &lt;code&gt;SimilarUserList&lt;/code&gt; of your subscribers list to potentially find new customers who share similar behaviors and interests.&lt;/p&gt; &lt;p&gt;Each &lt;code&gt;CrmBasedUserList&lt;/code&gt; must have an &lt;a href="https://developers.google.com/adwords/api/docs/reference/latest/AdwordsUserListService.CrmBasedUserList#optOutLink"&gt;optOutLink&lt;/a&gt; to provide a link to the page where people can manage their preferences for receiving email messages from the advertiser, including opting out of the advertiser email messages.&lt;/p&gt; &lt;p&gt;Before using this targeting strategy, please take the time to read our &lt;a href="https://support.google.com/adwordspolicy/answer/6299717"&gt;policy page&lt;/a&gt;.&lt;/p&gt; &lt;p&gt;A &lt;code&gt;CrmBasedUserList&lt;/code&gt; can be used for targeting on the Search network, YouTube and Gmail, whereas a &lt;code&gt;SimilarUserList&lt;/code&gt; of a &lt;code&gt;CrmBasedUserList&lt;/code&gt; can only be used for targeting on YouTube and Gmail.&lt;/p&gt; &lt;p&gt;Keep the following points in mind when using a &lt;code&gt;CrmBasedUserList&lt;/code&gt;:&lt;/p&gt;&lt;ul&gt; &lt;li&gt;Advertisers &lt;b&gt;must&lt;/b&gt; collect email addresses as 1st party. For example, an agency can submit email addresses on behalf of an advertiser if the advertiser collected the email addresses directly from its customers.&lt;/li&gt; &lt;li&gt;Email addresses can be from Gmail or non Gmail addresses as long as they are associated with a Google account. We recommend adding all available email addresses to maximize the size of the result.&lt;/li&gt; &lt;li&gt;Ads will serve only when the user list has at least 1,000 active members. Active members are those who have used Google Search, YouTube, or Gmail at least once over the last 30 days.&lt;/li&gt;&lt;/ul&gt; &lt;p&gt;If you want to read more about &lt;code&gt;CrmBasedUserList&lt;/code&gt;, have a look at our &lt;a href="https://developers.google.com/adwords/api/docs/guides/remarketing#remarketing-using-customer-match"&gt;guide&lt;/a&gt; and &lt;a href="https://developers.google.com/adwords/api/docs/clientlibraries"&gt;code examples&lt;/a&gt;.&lt;/p&gt; &lt;p&gt;As always, feel free to visit us or ask questions on the &lt;a href="https://groups.google.com/forum/#!forum/adwords-api"&gt;AdWords API Forum&lt;/a&gt; or our &lt;a href="https://plus.google.com/115658573333388777174/posts/bA8W5r3KwZb"&gt;Google+ page&lt;/a&gt;.&lt;/p&gt; &lt;span class="post-author" style="font-family: Arial, Helvetica, sans-serif;"&gt;&lt;a target="_blank" href="https://plus.google.com/u/0/+amirlazarovich" style="margin-right: 5px;"&gt;&lt;img height="40" width="40" src="https://lh3.googleusercontent.com/-G-24eXjxBas/AAAAAAAAAAI/AAAAAAAASo8/S9CdXKt3n9o/s60-p-rw-no/photo.jpg" style="vertical-align: middle;border-radius: 50%;border: solid 1px gray;"&gt;&lt;/a&gt;&lt;a target="_blank" href="https://plus.google.com/u/0/+amirlazarovich" rel="author"&gt;Amir Lazarovich&lt;/a&gt;, AdWords API Team&lt;/span&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/k-cH238YL9I" height="1" width="1" alt=""/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/6054834783852474791" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/6054834783852474791" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/lQlzL/~3/k-cH238YL9I/reach-your-most-valuable-customers-with.html" title="Reach your most valuable customers with Customer Match" /><author><name>Google Ads Developer Advisor</name><uri>http://www.blogger.com/profile/16700526826531306391</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img1.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googleadsdeveloper.blogspot.com/2015/11/reach-your-most-valuable-customers-with.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-7815614485808579332.post-2559227489214030735</id><published>2015-11-13T08:10:00.004-08:00</published><updated>2015-11-13T08:10:58.679-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api" /><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api_workshops" /><title type="text">Check out the latest workshop content!</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;We’ve completed the last round of the AdWords API Workshops, and you can check out all the content online by visiting the official website, &lt;a href="http://www.adwordsapiworkshops.com/"&gt;www.adwordsapiworkshops.com&lt;/a&gt;, and clicking on &lt;i&gt;Resources&lt;/i&gt;.&lt;br /&gt;&lt;br /&gt; Be sure to also check out our &lt;a href="https://www.youtube.com/playlist?list=PLKByxjzUC-N8mEDQF9ARMMkSv0AmYbpsh"&gt;YouTube channel&lt;/a&gt; for the recorded presentations.&lt;br /&gt;&lt;br /&gt; If you have any questions about the AdWords API Workshops, you can post them on our forums. Check out our &lt;a href="https://plus.google.com/+GoogleAdsDevelopers/posts"&gt;Google+&lt;/a&gt; page for Ads APIs updates.&lt;br /&gt;&lt;br /&gt; &lt;span class='byline-author'&gt;&lt;img height="40" width="40" src="https://lh5.googleusercontent.com/AoI6sErqRwv5nKLnrxDLY8Z3JKrDw4A37PnYyxZI6qkbbnz7i63gUqEPlSunJZVmtFhIkgX8ZBHi_R94a4z9-GlWiKVWBrPnawag6a5LcdzZgr7tiyhyyU9WGlHA_En6yiicELkx" style="vertical-align: middle; border:none;"/&gt;&lt;a href="http://google.com/+GustavoMenezes"&gt; Gustavo M. P. Moreira&lt;/a&gt;, AdWords API Team&lt;/span&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/Wmgi8i6azSI" height="1" width="1" alt=""/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/2559227489214030735" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/2559227489214030735" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/lQlzL/~3/Wmgi8i6azSI/check-out-latest-workshop-content.html" title="Check out the latest workshop content!" /><author><name>Google Ads Developer Advisor</name><uri>http://www.blogger.com/profile/16700526826531306391</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img1.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googleadsdeveloper.blogspot.com/2015/11/check-out-latest-workshop-content.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-7815614485808579332.post-1615760852088609927</id><published>2015-11-03T10:24:00.000-08:00</published><updated>2015-11-03T10:24:46.345-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api" /><category scheme="http://www.blogger.com/atom/ns#" term="conversion" /><title type="text">Changes to validation for AdWords API iTunes AppConversions</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;&lt;font size="4"&gt;What’s new?&lt;/font&gt;&lt;br /&gt;&lt;br /&gt; The validation for &lt;a href="https://developers.google.com/adwords/api/docs/reference/latest/ConversionTrackerService.AppConversion"&gt;AppConversions&lt;/a&gt; will become stricter starting on &lt;b&gt;November 9, 2015&lt;/b&gt;. If you’re using &lt;code&gt;AppConversions&lt;/code&gt; in v201509 or v201506 with &lt;a href="https://developers.google.com/adwords/api/docs/reference/latest/ConversionTrackerService.AppConversion#appPlatform"&gt;AppPlatform&lt;/a&gt;: &lt;code&gt;ITUNES&lt;/code&gt;, you’ll need to make sure that you’re using the correct &lt;a href="https://developers.google.com/adwords/api/docs/reference/v201509/ConversionTrackerService.AppConversion#appConversionType"&gt;AppConversionType&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt; &lt;font size="4"&gt;What was the old behavior?&lt;/font&gt;&lt;br /&gt;&lt;br /&gt; When v201509 was first released, the API would not throw an error if the incorrect value was sent in a request for an iTunes &lt;code&gt;AppConversion&lt;/code&gt;. The API automatically converted to the correct &lt;code&gt;AppConversionType&lt;/code&gt;. For example, if the value &lt;b&gt;DOWNLOAD&lt;/b&gt; was passed into v201509 for an iTunes &lt;code&gt;AppConversion&lt;/code&gt;, then that value would automatically be converted to &lt;b&gt;FIRST_OPEN&lt;/b&gt;.&lt;br /&gt;&lt;br /&gt; &lt;font size="4"&gt;What is the new behavior?&lt;/font&gt;&lt;br /&gt;&lt;br /&gt; In v201509, &lt;code&gt;AppConversionType&lt;/code&gt; &lt;b&gt;DOWNLOAD&lt;/b&gt; changed to &lt;b&gt;FIRST_OPEN&lt;/b&gt; for iTunes apps. Here’s what you will need to do: &lt;ul&gt; &lt;li&gt;For v201506 or earlier, you must pass in &lt;code&gt;AppConversionType&lt;/code&gt; &lt;b&gt;DOWNLOAD&lt;/b&gt; rather than &lt;b&gt;FIRST_OPEN&lt;/b&gt;.&lt;/li&gt; &lt;li&gt;For v201509 or later, you must pass in &lt;b&gt;FIRST_OPEN&lt;/b&gt; instead of &lt;b&gt;DOWNLOAD&lt;/b&gt;.&lt;/li&gt;&lt;/ul&gt; Passing in the incorrect value will result in the error &lt;b&gt;DOMAIN_EXCEPTION&lt;/b&gt; from the API starting on November 9.&lt;br /&gt;&lt;br /&gt; &lt;b&gt;Note&lt;/b&gt;: This only impacts iTunes conversions. There will be no changes to the validation for &lt;code&gt;AppConversions&lt;/code&gt; with an &lt;code&gt;AppPlatform&lt;/code&gt; of &lt;code&gt;ANDROID&lt;/code&gt;.&lt;br /&gt;&lt;br /&gt; &lt;font size="4"&gt;Where can I learn more?&lt;/font&gt;&lt;br /&gt;&lt;br /&gt; For more information on mobile apps and conversions, check out these guides: &lt;ul&gt; &lt;li&gt;&lt;a href="https://developers.google.com/adwords/api/docs/guides/conversion-tracking#app_conversions"&gt;Conversion Tracking&lt;/a&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="https://support.google.com/adwords/answer/6032059"&gt;Mobile App Install Campaigns&lt;/a&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="https://developers.google.com/adwords/api/docs/guides/increasing-mobile-app-engagement"&gt;Increasing Mobile App Engagement&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt; Questions? Visit us on the &lt;a href="https://groups.google.com/forum/#!forum/adwords-api"&gt;AdWords API Forum&lt;/a&gt; or our &lt;a href="https://plus.google.com/115658573333388777174/posts/bA8W5r3KwZb"&gt;Google+ page&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt; &lt;span class='byline-author'&gt;&lt;a href="https://plus.google.com/109542956637533475940/posts"&gt;&lt;img height="40" width="40" src="https://lh6.googleusercontent.com/KEq4I1vQckO56m_W9aB7bAYjPM217-03D2sv74JAAWmPT6g2lkwRDxhG_OtvMl-6Lkkaeix_OjpEcBQGIeh9sQnaoSQlDGPayKcrgEyD8l38qUmqm9Jh1RKTOC9RpisPkd7i2EE4" style="vertical-align: middle; border:none;"/&gt; Nadine Sundquist&lt;/a&gt;, AdWords API Team&lt;/span&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/PP0sVMwvjn4" height="1" width="1" alt=""/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/1615760852088609927" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/1615760852088609927" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/lQlzL/~3/PP0sVMwvjn4/changes-to-validation-for-adwords-api.html" title="Changes to validation for AdWords API iTunes AppConversions" /><author><name>Google Ads Developer Advisor</name><uri>http://www.blogger.com/profile/16700526826531306391</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img1.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googleadsdeveloper.blogspot.com/2015/11/changes-to-validation-for-adwords-api.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-7815614485808579332.post-8649969579759117112</id><published>2015-10-27T15:21:00.000-07:00</published><updated>2015-10-27T15:21:53.967-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api" /><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api_v201506" /><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api_v201509" /><category scheme="http://www.blogger.com/atom/ns#" term="reporting" /><title type="text">Reporting changes in AdWords API v201509</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;&lt;a href="http://googleadsdeveloper.blogspot.com/2015/10/announcing-v201509-of-adwords-api.html"&gt;AdWords API v201509&lt;/a&gt; introduces some changes to reporting columns, particularly &lt;a href="https://developers.google.com/adwords/api/docs/appendix/reports/all-reports#clicks"&gt;Clicks&lt;/a&gt;. Recently, AdWords introduced new columns called &lt;a href="https://plus.sandbox.google.com/+GoogleAds/posts/SxjMpNVyfYW"&gt;Engagements&lt;/a&gt; and &lt;a href="http://adwords.blogspot.com/2015/09/new-reporting-columns-for-multi-channel.html"&gt;Interactions&lt;/a&gt;. It also added reporting columns related to video campaigns such as &lt;code&gt;VideoViews&lt;/code&gt;, which have previously been unavailable via API reporting. &lt;b&gt;AdWords API version v201509 has updated its reporting to match these changes.&lt;/b&gt;&lt;br /&gt;&lt;br /&gt; The new &lt;code&gt;Interactions&lt;/code&gt; field, available in API performance reports, can be thought of as the main action a user takes with the ad format: clicks for text ads, engagements for Lightbox ads, and views for video ads. Previously, views for video ads were not returned in API reporting, so having access to this data is new.&lt;br /&gt;&lt;br /&gt; Prior to v201509, the &lt;code&gt;Clicks&lt;/code&gt; field always included both clicks and engagements. Starting in v201509, the &lt;code&gt;Clicks&lt;/code&gt; field includes only click actions, like clickthroughs to a landing page or clicks to call. This means that clicks on video ads, which are unpaid, will be included in this field. However, engagements for Lightbox ads &lt;b&gt;will not&lt;/b&gt; be counted.&lt;br /&gt;&lt;br /&gt; If measuring performance across multiple ad formats, you might consider using &lt;code&gt;Interactions&lt;/code&gt; to view the total number of primary user actions on ads, all in the same column. &lt;code&gt;Clicks&lt;/code&gt;, &lt;code&gt;Engagements&lt;/code&gt;, and &lt;code&gt;VideoViews&lt;/code&gt; are available as well for more fine-grained reporting by ad format.&lt;br /&gt;&lt;br /&gt; The table below summarizes the changes in each field for various ad formats.&lt;br /&gt;&lt;br /&gt; &lt;table style="border-collapse: collapse; border: none; width: 648px;"&gt;&lt;colgroup&gt;&lt;col width="15%"&gt;&lt;/col&gt;&lt;col width="25%"&gt;&lt;/col&gt;&lt;col width="25%"&gt;&lt;/col&gt;&lt;/colgroup&gt;&lt;tbody&gt;&lt;tr style="height: 0px; background-color: #6199df; border-bottom: solid #4d90fe 1px; border-left: solid #4d90fe 1px; border-right: solid #4d90fe 1px; border-top: solid #4d90fe 1px; vertical-align: top;"&gt; &lt;td style="padding: 7px 7px 7px 7px; border-bottom: solid #4d90fe 1px; border-left: solid #4d90fe 1px; border-right: solid #4d90fe 1px; border-top: solid #4d90fe 1px;"&gt;&lt;div dir="ltr" style="line-height: 1; margin-bottom: 0pt; margin-top: 0pt;"&gt;&lt;span style="color: white; font-weight: bold;"&gt;Field&lt;/span&gt;&lt;/div&gt;&lt;/td&gt; &lt;td style="padding: 7px 7px 7px 7px; border-bottom: solid #4d90fe 1px; border-left: solid #4d90fe 1px; border-right: solid #4d90fe 1px; border-top: solid #4d90fe 1px;"&gt;&lt;div dir="ltr" style="line-height: 1; margin-bottom: 0pt; margin-top: 0pt;"&gt;&lt;span style="color: white; font-weight: bold;"&gt;v201506&lt;/span&gt;&lt;/div&gt;&lt;/td&gt; &lt;td style="padding: 7px 7px 7px 7px; border-bottom: solid #4d90fe 1px; border-left: solid #4d90fe 1px; border-right: solid #4d90fe 1px; border-top: solid #4d90fe 1px;"&gt;&lt;div dir="ltr" style="line-height: 1; margin-bottom: 0pt; margin-top: 0pt;"&gt;&lt;span style="color: white; font-weight: bold;"&gt;v201509&lt;/span&gt;&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr style="height: 0px;"&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: top;"&gt;&lt;div dir="ltr" style="line-height: 1; margin-bottom: 0pt; margin-top: 0pt;"&gt;&lt;code&gt;Clicks&lt;/code&gt;&lt;/div&gt;&lt;/td&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: top;"&gt;&lt;div dir="ltr" style="line-height: 1; margin-bottom: 0pt; margin-top: 0pt;"&gt;&lt;b&gt;Text ads&lt;/b&gt;: clickthrough to a landing page&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Lightbox ads&lt;/b&gt;: hover to expanded ad format &lt;/div&gt;&lt;/td&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: top;"&gt;&lt;div dir="ltr" style="line-height: 1; margin-bottom: 0pt; margin-top: 0pt;"&gt;&lt;b&gt;Text ads&lt;/b&gt;: clickthrough to a landing page or clicks to call&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Lightbox ads&lt;/b&gt;: clickthrough to a landing page&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Video ads&lt;/b&gt;: clickthrough to a landing page &lt;/div&gt;&lt;/td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr style="height: 0px;"&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: top;"&gt;&lt;div dir="ltr" style="line-height: 1; margin-bottom: 0pt; margin-top: 0pt;"&gt;&lt;code&gt;Engagements&lt;/code&gt;&lt;/div&gt;&lt;/td&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: top;"&gt;&lt;div dir="ltr" style="line-height: 1; margin-bottom: 0pt; margin-top: 0pt;"&gt;N/A &lt;/div&gt;&lt;/td&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: top;"&gt;&lt;div dir="ltr" style="line-height: 1; margin-bottom: 0pt; margin-top: 0pt;"&gt;&lt;b&gt;Lightbox ads&lt;/b&gt;: hover to expanded ad format &lt;/div&gt;&lt;/td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr style="height: 0px;"&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: top;"&gt;&lt;div dir="ltr" style="line-height: 1; margin-bottom: 0pt; margin-top: 0pt;"&gt;&lt;code&gt;VideoViews&lt;/code&gt;&lt;/div&gt;&lt;/td&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: top;"&gt;&lt;div dir="ltr" style="line-height: 1; margin-bottom: 0pt; margin-top: 0pt;"&gt;N/A &lt;/div&gt;&lt;/td&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: top;"&gt;&lt;div dir="ltr" style="line-height: 1; margin-bottom: 0pt; margin-top: 0pt;"&gt;&lt;b&gt;Video ads&lt;/b&gt;: view &lt;/div&gt;&lt;/td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr style="height: 0px;"&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: top;"&gt;&lt;div dir="ltr" style="line-height: 1; margin-bottom: 0pt; margin-top: 0pt;"&gt;&lt;code&gt;Interactions&lt;/code&gt;&lt;/div&gt;&lt;/td&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: top;"&gt;&lt;div dir="ltr" style="line-height: 1; margin-bottom: 0pt; margin-top: 0pt;"&gt;N/A &lt;/div&gt;&lt;/td&gt;&lt;td style="border-bottom: solid #bbbbbb 1px; border-left: solid #bbbbbb 1px; border-right: solid #bbbbbb 1px; border-top: solid #bbbbbb 1px; padding: 7px 7px 7px 7px; vertical-align: top;"&gt;&lt;div dir="ltr" style="line-height: 1; margin-bottom: 0pt; margin-top: 0pt;"&gt;&lt;b&gt;Text ads&lt;/b&gt;: clickthrough to a landing page or clicks to call&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Lightbox ads&lt;/b&gt;: hover to expanded ad format&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Video ads&lt;/b&gt;: views &lt;/div&gt;&lt;/td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt; &lt;br /&gt;Please note that &lt;b&gt;reporting in v201506 and previous versions is unaffected&lt;/b&gt;; they return the same data that they always have, represented the same way. This means that when comparing the data you receive from older versions of the API to user interface reports, or to v201509 reports, the numbers will not directly match up. Video-related stats will still be excluded from v201506. The &lt;code&gt;Clicks&lt;/code&gt; column in v201506 will match the &lt;code&gt;Interactions&lt;/code&gt; column from v201509 if you subtract out video interactions.&lt;br /&gt;&lt;br /&gt; For ease of reporting, it’s recommended to migrate to v201509 as soon as possible.&lt;br /&gt;&lt;br /&gt; Keep in mind these aren’t the only reporting changes in v201509 — for more details on conversion-related reporting changes, please see the &lt;a href="https://developers.google.com/adwords/api/docs/reference/#conversion-reporting"&gt;release notes&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt; If you have any questions about this or other aspects of the AdWords API, please contact us via the &lt;a href="https://groups.google.com/forum/#!forum/adwords-api"&gt;forum&lt;/a&gt; or the &lt;a href="https://plus.google.com/+GoogleAdsDevelopers"&gt;Ads Developers Plus Page&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt; &lt;span class='byline-author'&gt;- Michael Cloonan, AdWords API Team&lt;/span&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/PUsNV7oy3Z8" height="1" width="1" alt=""/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/8649969579759117112" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/8649969579759117112" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/lQlzL/~3/PUsNV7oy3Z8/reporting-changes-in-adwords-api-v201509.html" title="Reporting changes in AdWords API v201509" /><author><name>Google Ads Developer Advisor</name><uri>http://www.blogger.com/profile/16700526826531306391</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img1.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googleadsdeveloper.blogspot.com/2015/10/reporting-changes-in-adwords-api-v201509.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-7815614485808579332.post-4693387723249102222</id><published>2015-10-22T14:46:00.002-07:00</published><updated>2015-10-22T14:46:27.863-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api" /><category scheme="http://www.blogger.com/atom/ns#" term="bidding" /><title type="text">Upcoming changes to inactive ad group CPA bids in AdWords</title><content type="html">&lt;p&gt;In preparation for improvements to CPA bidding in AdWords, starting &lt;b&gt;October 26, 2015&lt;/b&gt;, we'll perform a &lt;b&gt;one-time&lt;/b&gt; removal of inactive ad group-level CPA bids. &lt;p&gt;What's an inactive ad group CPA bid, you ask? An ad group-level CPA bid is inactive if the ad group's effective bidding strategy is not a &lt;code&gt;CONVERSION_OPTIMIZER&lt;/code&gt; strategy. This includes CPA bids on ad groups whose effective bidding strategy is &lt;code&gt;TARGET_CPA&lt;/code&gt;, since the target for such ad groups is specified at the strategy level. The effective bidding strategy is the ad group-level strategy, if specified. Otherwise, it’s the bidding strategy set at the campaign-level. &lt;p&gt;&lt;h2&gt;How this change impacts the AdWords API&lt;/h2&gt;After the one-time removal of inactive CPA bids, there are two categories of ad groups you'll want to review: &lt;ul&gt;&lt;li&gt;&lt;b&gt;Ad groups from which inactive CPA bids were removed:&lt;/b&gt; For these ad groups, the &lt;a target="_blank" href="https://developers.google.com/adwords/api/docs/reference/latest/AdGroupService.AdGroup"&gt;AdGroup&lt;/a&gt; object will no longer have a &lt;a target="_blank" href="https://developers.google.com/adwords/api/docs/reference/latest/AdGroupService.CpaBid"&gt;CpaBid&lt;/a&gt; in the &lt;a target="_blank" href="https://developers.google.com/adwords/api/docs/reference/latest/AdGroupService.BiddingStrategyConfiguration#bids"&gt;bids&lt;/a&gt; attribute of its ad group-level &lt;code&gt;BiddingStrategyConfiguration&lt;/code&gt;. Therefore, if you change the effective bidding strategy of these ad groups back to a &lt;code&gt;CONVERSION_OPTIMIZER&lt;/code&gt; strategy, you will have to add a &lt;i&gt;new&lt;/i&gt; &lt;code&gt;CpaBid&lt;/code&gt; to the ad group’s &lt;code&gt;BiddingStrategyConfiguration&lt;/code&gt; for your ads in the ad group to serve. You will only have to make this change &lt;i&gt;once&lt;/i&gt;.&lt;/li&gt;&lt;li&gt;&lt;b&gt;Ad groups you change from &lt;code&gt;TARGET_CPA&lt;/code&gt; to &lt;code&gt;CONVERSION_OPTIMIZER&lt;/code&gt;:&lt;/b&gt; AdWords will no longer copy the &lt;a target="_blank" href="https://developers.google.com/adwords/api/docs/reference/latest/BiddingStrategyService.TargetCpaBiddingScheme#targetCpa"&gt;TargetCpaBiddingScheme.targetCpa&lt;/a&gt; value to a &lt;code&gt;CpaBid&lt;/code&gt; on the ad group's bidding strategy configuration. Therefore, you will not automatically get the &lt;code&gt;TARGET_CPA&lt;/code&gt; strategy bid if you transition to &lt;code&gt;CONVERSION_OPTIMIZER&lt;/code&gt;. If the ad group's bidding strategy configuration already has a &lt;code&gt;CpaBid&lt;/code&gt;, then &lt;code&gt;CONVERSION_OPTIMIZER&lt;/code&gt; will use that bid. Otherwise, you will have to add a new &lt;code&gt;CpaBid&lt;/code&gt; to the ad group &lt;code&gt;BiddingStrategyConfiguration&lt;/code&gt; before ads in your ad group will serve.&lt;/li&gt;&lt;/ul&gt; &lt;p&gt;&lt;h2&gt;How this change impacts bidding&lt;/h2&gt;Since the CPA bids being removed are inactive, this change will have no impact on bidding or ad serving. &lt;p&gt;&lt;h2&gt;What you should do&lt;/h2&gt;If you are interested in inactive CPA bids for &lt;code&gt;CONVERSION_OPTIMIZER&lt;/code&gt; bidding strategies, download the current bids using &lt;a target="_blank" href="https://developers.google.com/adwords/api/docs/reference/latest/AdGroupService"&gt;AdGroupService&lt;/a&gt; before the removal date. &lt;p&gt;&lt;h2&gt;More bidding resources&lt;/h2&gt;&lt;ul&gt;&lt;li&gt;&lt;a target="_blank" href="https://developers.google.com/adwords/api/docs/guides/bidding"&gt;AdWords API bidding guide&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a target="_blank" href="https://developers.google.com/adwords/api/docs/reference/latest/BiddingStrategyService.TargetCpaBiddingScheme"&gt;Latest API docs for TargetCpaBiddingScheme&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt; &lt;p&gt;Still have questions? Feel free to visit us on the &lt;a target="_blank" href="https://groups.google.com/forum/#!forum/adwords-api"&gt;AdWords API Forum&lt;/a&gt; or our &lt;a target="_blank" href="https://plus.google.com/115658573333388777174/posts/bA8W5r3KwZb"&gt;Google+ page&lt;/a&gt;. &lt;p&gt;&lt;span class='byline-author'&gt;&lt;img height="40" width="40" src="https://lh4.googleusercontent.com/XRLRWJr-oErh4FOG2geCSBVWjoq3wsf9_8hIg_vudFzd02NZc6roEazoK-c_KVCEAdMawStXArkfbNRDpgzVEn8rzYJpEcBim6fSfdfHoV7nVLDhiARUeTvFrMhedck1f3cTdEA" style="vertical-align: middle; border:none;"/&gt; - &lt;a target="_blank" href="https://plus.google.com/100205313733177937765/posts"&gt;Josh Radcliff&lt;/a&gt;, AdWords API Team&lt;/span&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/9tGzuXadnVk" height="1" width="1" alt=""/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/4693387723249102222" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/4693387723249102222" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/lQlzL/~3/9tGzuXadnVk/upcoming-changes-to-inactive-ad-group.html" title="Upcoming changes to inactive ad group CPA bids in AdWords" /><author><name>Google Ads Developer Advisor</name><uri>http://www.blogger.com/profile/16700526826531306391</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img1.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googleadsdeveloper.blogspot.com/2015/10/upcoming-changes-to-inactive-ad-group.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-7815614485808579332.post-6949253538302421333</id><published>2015-10-15T04:20:00.001-07:00</published><updated>2015-10-15T04:20:50.312-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="adwords_api" /><category scheme="http://www.blogger.com/atom/ns#" term="location_extensions" /><category scheme="http://www.blogger.com/atom/ns#" term="sunset" /><title type="text">Using the Google My Business API to manage your location extensions</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;Last year, we announced &lt;a href="http://googleadsdeveloper.blogspot.com.au/2014/07/adwords-api-upgrading-to-account-level.html"&gt;upgraded location extensions&lt;/a&gt;, a more efficient way to manage and use business locations in ads by linking &lt;a href="https://support.google.com/business/answer/6002002?&amp;amp;ref_topic=4596653"&gt;Google My Business&lt;/a&gt; and AdWords accounts. To help you manage your business locations more easily at scale, we’re now releasing the &lt;a href="https://developers.google.com/my-business"&gt;Google My Business API&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt; Google My Business will be the central repository for managing your business locations. The creation of &lt;a href="https://developers.google.com/adwords/api/docs/guides/feed-services-locations#upgraded_manual_location_extensions"&gt;manual location extensions as feed items&lt;/a&gt; through the AdWords API has been deprecated and will sunset in Q2 2016. Please update your code before &lt;b&gt;March 31, 2016&lt;/b&gt; to avoid being impacted by this transition.&lt;br /&gt;&lt;br /&gt; &lt;font size="4"&gt;Supported features&lt;/font&gt;&lt;br /&gt;The first version of the Google My Business API allows you to read, create, update and delete unverified business locations. Supported attributes are name, address, contact numbers, URL, categories, and business hours. Unverified locations can be used as location extensions in AdWords, but &lt;a href="https://support.google.com/business/answer/2911778"&gt;have to be verified&lt;/a&gt; to be eligible to show up on Google Maps.&lt;br /&gt;&lt;br /&gt; Future releases of the Google My Business API will support additional functionality that will allow you to fully manage your location data across Google Ads and Maps.&lt;br /&gt;&lt;br /&gt; &lt;font size="4"&gt;Getting started with the Google My Business API&lt;/font&gt;&lt;br /&gt;If you already use the AdWords API and manage more than 50 business locations, you can &lt;a href="https://docs.google.com/a/google.com/forms/d/1J9TaV8UaidPVpt85wrQOrbNFxdMP-jpX8fbB6Uk2n1o/viewform"&gt;apply for access&lt;/a&gt; to the Google My Business API. Once granted, you will have access to the &lt;a href="https://developers.google.com/my-business/"&gt;Google My Business API documentation&lt;/a&gt; and you can follow the steps there to get started. For accounts with 50 or fewer locations, please use &lt;a href="https://business.google.com/manage/"&gt;Google My Business Locations&lt;/a&gt; &lt;a href="https://www.google.com/local/manage/"&gt;for now&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt; &lt;font size="4"&gt;Linking locations to accounts, campaigns or ad groups as location extensions&lt;/font&gt;&lt;br /&gt;Users managing multi-location businesses (chains) must have a separate Google My Business account for each chain for bulk-verification. If you already manage locations under bulk-verified accounts in Google My Business today, you can link those accounts to AdWords to have your location extensions in sync.&lt;br /&gt;&lt;br /&gt; For developers managing AdWords accounts with a large number of locations for small and medium businesses, we recommend creating one Google My Business account as a central repository for all locations. Each physical location should be created only once. If different owners and managers are involved per location or for sets of locations, we suggest using &lt;a href="https://support.google.com/business/answer/6085326"&gt;Business Accounts&lt;/a&gt;. &lt;br /&gt;&lt;br /&gt; Once the AdWords accounts are linked to your shared Google My Business account, the locations will be available as &lt;a href="https://developers.google.com/adwords/api/docs/appendix/placeholders#location"&gt;feed items&lt;/a&gt; in AdWords. You are responsible for creating a &lt;a href="https://developers.google.com/adwords/api/docs/reference/latest/CustomerFeedService.CustomerFeed"&gt;CustomerFeed&lt;/a&gt; and using an appropriate &lt;a href="https://developers.google.com/adwords/api/docs/guides/feed-matching-functions"&gt;matching function&lt;/a&gt; to make sure only locations that actually belong to the customer are linked to their related AdWords account. You can use &lt;a href="https://developers.google.com/adwords/api/docs/reference/latest/CampaignFeedService.CampaignFeed"&gt;CampaignFeed&lt;/a&gt;s or &lt;a href="https://developers.google.com/adwords/api/docs/reference/latest/AdGroupFeedService.AdGroupFeed"&gt;AdGroupFeed&lt;/a&gt;s for additional filtering based on campaigns or ad groups.&lt;br /&gt;&lt;br /&gt; The best way to filter locations from a shared Google My Business account is to create &lt;a href="https://support.google.com/business/answer/3370250?hl=en#labels"&gt;location labels&lt;/a&gt; through the Google My Business API and use a matching function that uses these labels for selection. For example, you can label each location with its AdWords Customer ID in Google My Business and use these Customer ID labels for filtering in AdWords. Or you can label each location with a unique ID, as long as you keep track of these IDs.&lt;br /&gt;&lt;br /&gt; Please see our &lt;a href="https://developers.google.com/adwords/api/docs/guides/feed-services-locations"&gt;guide for managing location extensions&lt;/a&gt; for further details, which also includes an &lt;a href="https://developers.google.com/adwords/api/docs/guides/feed-services-locations#complete_code_example"&gt;end-to-end code example&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt; &lt;font size="4"&gt;Migration of existing location extensions&lt;/font&gt;&lt;br /&gt;If you are using manual location extensions through the AdWords API, we recommend &lt;a href="https://developers.google.com/adwords/api/docs/guides/feed-services-locations"&gt;migrating your locations to Google My Business&lt;/a&gt; before &lt;b&gt;March 31, 2016&lt;/b&gt;. After this date, the creation of manual location extensions will sunset. All unmigrated locations stored in AdWords will be auto-migrated to Google My Business at a later date. Further details about the timeline and process will be announced in this blog.&lt;br /&gt;&lt;br /&gt; &lt;span class='byline-author'&gt;&lt;img height="40" width="40" src="https://lh6.googleusercontent.com/DGymUlwQpGo-ZzXF9-yxh9cp-DrPU5-yt2tisn7QsZw6dywEw-Wx8jlhWOqAIOcUXqmpfBiiVjFv3AQpQKP9HO8GaG-FRk1NHYRB5UdaLmwlNLe3ROIkf02e5tilrcpB09WpUXs" style="vertical-align: middle; border:none;"/&gt; Timo Bozsolik, AdWords API Team&lt;/span&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/84XhteoQdCg" height="1" width="1" alt=""/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/6949253538302421333" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7815614485808579332/posts/default/6949253538302421333" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/lQlzL/~3/84XhteoQdCg/using-google-my-business-api-to-manage.html" title="Using the Google My Business API to manage your location extensions" /><author><name>Google Ads Developer Advisor</name><uri>http://www.blogger.com/profile/16700526826531306391</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img1.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googleadsdeveloper.blogspot.com/2015/10/using-google-my-business-api-to-manage.html</feedburner:origLink></entry></feed>