rss-parser

Version:

A lightweight RSS parser, for Node and the browser

91 lines • 148 kB

JSON

{ "feed": { "items": [ { "title": "AdWords and DFP Java client library will soon require Java 7+", "link": "http://feedproxy.google.com/~r/blogspot/lQlzL/~3/Zjf41PDVLAc/adwords-and-dfp-java-client-library.html", "pubDate": "2016-06-03T14:38:22.568Z", "author": "Google Ads Developer Advisor", "content": "<div dir=\"ltr\" style=\"text-align: left;\" trbidi=\"on\">After November 2016, all releases of the <a href=\"https://github.com/googleads/googleads-java-lib\">Google Ads API Java Client Library</a> will only be compatible with Java 7 (1.7) and higher. Why this change is happening The primary reasons for this change are: <ul> <li>Java 6 is a bit outdated -- it was <a href=\"http://www.oracle.com/technetwork/java/eol-135779.html#java-commercial-offerings\">first introduced in Dec 2006</a>, and <a href=\"http://www.oracle.com/technetwork/java/eol-135779.html#java-commercial-offerings\">Oracle's support for Java 6 is approaching some key end dates</a>.</li> <li>Maintaining support for Java 6 means code examples cannot leverage <a href=\"http://www.oracle.com/technetwork/java/javase/jdk7-relnotes-418459.html\">useful features of Java 7</a>, such as catch clauses for multiple exception types and type inference for generic instance creation.</li> <li>Usage of Java 6 among Google Ads API Java Client Library developers is rapidly declining.</li></ul> Next steps If you are using Java 7 or higher, then no action is required. If you are still using Java 6 then you'll have to migrate your runtime to Java 7 or higher. Check out the <a href=\"http://docs.oracle.com/javase/7/docs/webnotes/adoptionGuide/\">Java 7 adoption guide from Oracle</a> to get started. Still have questions? Feel free to file an issue on the library's <a href=\"https://github.com/googleads/googleads-java-lib/issues\">issues page</a> or contact us via our <a href=\"https://plus.google.com/115658573333388777174/posts\">Google+ page</a>. <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;\"/> - <a href=\"https://plus.google.com/100205313733177937765/posts\">Josh Radcliff</a>, AdWords API Team</div><img src=\"http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/Zjf41PDVLAc\" height=\"1\" width=\"1\" alt=\"\"/>", "contentSnippet": "After November 2016, all releases of the Google Ads API Java Client Library will only be compatible with Java 7 (1.7) and higher. Why this change is happeningThe primary reasons for this change are: Java 6 is a bit outdated -- it was first introduced in Dec 2006, and Oracle's support for Java 6 is approaching some key end dates. Maintaining support for Java 6 means code examples cannot leverage useful features of Java 7, such as catch clauses for multiple exception types and type inference for generic instance creation. Usage of Java 6 among Google Ads API Java Client Library developers is rapidly declining. Next stepsIf you are using Java 7 or higher, then no action is required. If you are still using Java 6 then you'll have to migrate your runtime to Java 7 or higher. Check out the Java 7 adoption guide from Oracle to get started. Still have questions? Feel free to file an issue on the library's issues page or contact us via our Google+ page. - Josh Radcliff, AdWords API Team", "id": "tag:blogger.com,1999:blog-7815614485808579332.post-8394866751819460570" }, { "title": "Register now for the Fall 2016 AdWords API Workshops!", "link": "http://feedproxy.google.com/~r/blogspot/lQlzL/~3/DrA9NPZRSBY/register-now-for-fall-2016-adwords-api.html", "pubDate": "2016-06-01T15:35:29.005Z", "author": "Google Ads Developer Advisor", "content": "<div dir=\"ltr\" style=\"text-align: left;\" trbidi=\"on\">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: <a href=\"https://events.withgoogle.com/adwords-api-workshops-2016/\">https://events.withgoogle.com/adwords-api-workshops-2016/</a> Choose a location and type of event that works best for you. Once you register, we'll send you an email confirmation. The types of workshops this Fall are: <ul> <li>The Technical workshops are for experienced API users, and we are going to talk about advanced use cases on a very technical level.</li> <li>The Business workshop covers use cases, automation, scaling, and tools. There will not be any deep technical content in this workshop, so anyone can attend.</li></ul> We’ll be covering everything from what’s new in each of the releases to how to better utilize the API. If you have any questions about the AdWords API Workshops, you can post them on our <a href=\"https://groups.google.com/forum/#!forum/adwords-api\">forum</a>. Check out our <a href=\"https://plus.google.com/+GoogleAdsDevelopers/posts\">Google+</a> page for Ads API updates. <a href=\"https://plus.google.com/109542956637533475940/posts\"><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;\"/> Nadine Sundquist</a>, AdWords API Team</div><img src=\"http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/DrA9NPZRSBY\" height=\"1\" width=\"1\" alt=\"\"/>", "contentSnippet": "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: https://events.withgoogle.com/adwords-api-workshops-2016/ Choose a location and type of event that works best for you. Once you register, we'll send you an email confirmation. The types of workshops this Fall are: The Technical workshops are for experienced API users, and we are going to talk about advanced use cases on a very technical level. The Business workshop covers use cases, automation, scaling, and tools. There will not be any deep technical content in this workshop, so anyone can attend. We’ll be covering everything from what’s new in each of the releases to how to better utilize the API. If you have any questions about the AdWords API Workshops, you can post them on our forum. Check out our Google+ page for Ads API updates. Nadine Sundquist, AdWords API Team", "id": "tag:blogger.com,1999:blog-7815614485808579332.post-2252211805800199673" }, { "title": "Announcing v201605 of the AdWords API", "link": "http://feedproxy.google.com/~r/blogspot/lQlzL/~3/FnIR4Y1m5q4/announcing-v201605-of-adwords-api.html", "pubDate": "2016-05-27T20:25:53.983Z", "author": "Google Ads Developer Advisor", "content": "<div dir=\"ltr\" style=\"text-align: left;\" trbidi=\"on\">Today we’re announcing the release of <a href=\"https://developers.google.com/adwords/api/docs/reference/#v201605\">AdWords API v201605</a>. This is the third release that follows the <a href=\"http://googleadsdeveloper.blogspot.com/2016/01/new-release-schedule-for-adwords-api.html\">new release schedule announced in January 2016</a>. Here are the highlights: <ul> <li>Expanded Text Ads and responsive ads for Display. Support was added for creating the new <a href=\"https://developers.google.com/adwords/api/docs/reference/v201605/AdGroupAdService.ExpandedTextAd\">ExpandedTextAd</a> and <a href=\"https://developers.google.com/adwords/api/docs/reference/v201605/AdGroupAdService.ResponsiveDisplayAd\">ResponsiveDisplayAd</a> ad types in <a href=\"https://developers.google.com/adwords/api/docs/test-accounts\">test accounts</a>. Give these <a href=\"http://adwords.blogspot.com/2016/05/ads-and-analytics-innovations-for-a-mobile-first-world.html\">new formats</a> a try with your test accounts. This functionality will be made available for production accounts over the next few months.</li> <li>Campaign bid estimates by platform. Inclusion of campaign estimates by platform was added to <a href=\"https://developers.google.com/adwords/api/docs/reference/latest/TrafficEstimatorService\">TrafficEstimatorService</a>. Check out the updated <a href=\"https://developers.google.com/adwords/api/docs/guides/traffic-estimator-service#prepare_the_request\">Estimating Traffic</a> guide for more details.</li> <li>Bid modifiers for all platforms (test accounts only). <a href=\"https://developers.google.com/adwords/api/docs/reference/latest/CampaignCriterionService.CampaignCriterion#bidmodifier\">Campaign</a> and <a href=\"https://developers.google.com/adwords/api/docs/reference/latest/AdGroupBidModifierService.AdGroupBidModifier\">ad group</a> bid modifiers for all <a href=\"https://developers.google.com/adwords/api/docs/reference/latest/AdGroupBidModifierService.Platform\">platforms</a> are now supported across all versions, but only in <a href=\"https://developers.google.com/adwords/api/docs/test-accounts\">test accounts</a>. Previously, platform bid modifiers were only supported for the <a href=\"https://developers.google.com/adwords/api/docs/appendix/platforms\">HighEndMobile (30001) platform</a>. This functionality will be made available for production accounts over the next few months, as mentioned in a recent <a href=\"http://adwords.blogspot.com/2016/05/ads-and-analytics-innovations-for-a-mobile-first-world.html\">Inside AdWords blog post</a>.</li> <li>Improved reporting on quality score. The new <a href=\"https://developers.google.com/adwords/api/docs/appendix/reports/all-reports#hasqualityscore\">HasQualityScore</a> field lets you filter reporting rows based on the presence or absence of quality score data for each criterion. In addition, the <a href=\"https://developers.google.com/adwords/api/docs/appendix/reports/all-reports#qualityscore\">QualityScore</a> field will now have a value of '--' on rows where <code>HasQualityScore = false</code>. Previously, these rows had a <code>QualityScore</code> value of 6 for Search campaigns, and 0 (zero) for Display campaigns.</li> <li>Image dimensions in reports. The <a href=\"https://developers.google.com/adwords/api/docs/appendix/reports/ad-performance-report#imagecreativeimageheight\">ImageCreativeImageHeight</a> and <a href=\"https://developers.google.com/adwords/api/docs/appendix/reports/ad-performance-report#imagecreativeimagewidth\">ImageCreativeImageWidth</a> fields were added to the Ad Performance report so you can retrieve image dimensions for all <a href=\"https://developers.google.com/adwords/api/docs/reference/latest/AdGroupAdService.ImageAd\">image ads</a> without making multiple <a href=\"https://developers.google.com/adwords/api/docs/reference/latest/AdGroupAdService\">AdGroupAdService</a> requests.</li></ul> If you’re using v201601 of the AdWords API, please note that it’s now deprecated and will <a href=\"https://developers.google.com/adwords/api/docs/sunset-dates\">be sunset</a> on August 23, 2016. We encourage you to skip v201603 and migrate straight to v201605. As with every new version of the AdWords API, we encourage you to carefully review all changes in the <a href=\"https://developers.google.com/adwords/api/docs/reference/#v201605\">release notes</a> and the <a href=\"https://developers.google.com/adwords/api/docs/guides/migration/v201605\">v201605 migration guide</a>. The updated <a href=\"https://developers.google.com/adwords/api/docs/clientlibraries\">client libraries</a> and code examples will be published shortly. If you have any questions or need help with migration, please post on the <a href=\"https://developers.google.com/adwords/api/community/\">forum</a> or the <a href=\"https://plus.google.com/+GoogleAdsDevelopers\">Ads Developers Plus Page</a>. <img height=\"40\" width=\"40\" src=\"https://lh6.googleusercontent.com/qDcZnztzS6s1O4oPOk33OiQ8T7VErqUL0r4wA6CoAcjwrwJ5niktK0mm8UENvdZ8j4dfAKg4pAMKq72OCTlPvc3BrRvQ4fAOq6e4-jvI5FbJXSZQBOfNyQbvBR4fIqKiAMMjHdcF\" style=\"vertical-align: middle; border:none;\"/> - <a href=\"https://plus.google.com/100205313733177937765/posts\">Josh Radcliff</a> <a href=\"https://plus.google.com/100205313733177937765/posts\">on behalf of</a> the AdWords API Team</div><img src=\"http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/FnIR4Y1m5q4\" height=\"1\" width=\"1\" alt=\"\"/>", "contentSnippet": "Today we’re announcing the release of AdWords API v201605. This is the third release that follows the new release schedule announced in January 2016. Here are the highlights: Expanded Text Ads and responsive ads for Display. Support was added for creating the new ExpandedTextAd and ResponsiveDisplayAd ad types in test accounts. Give these new formats a try with your test accounts. This functionality will be made available for production accounts over the next few months. Campaign bid estimates by platform. Inclusion of campaign estimates by platform was added to TrafficEstimatorService. Check out the updated Estimating Traffic guide for more details. Bid modifiers for all platforms (test accounts only). Campaign and ad group bid modifiers for all platforms are now supported across all versions, but only in test accounts. Previously, platform bid modifiers were only supported for the HighEndMobile (30001) platform. This functionality will be made available for production accounts over the next few months, as mentioned in a recent Inside AdWords blog post. Improved reporting on quality score. The new HasQualityScore field lets you filter reporting rows based on the presence or absence of quality score data for each criterion. In addition, the QualityScore field will now have a value of '--' on rows where HasQualityScore = false. Previously, these rows had a QualityScore value of 6 for Search campaigns, and 0 (zero) for Display campaigns. Image dimensions in reports. The ImageCreativeImageHeight and ImageCreativeImageWidth fields were added to the Ad Performance report so you can retrieve image dimensions for all image ads without making multiple AdGroupAdService requests. If you’re using v201601 of the AdWords API, please note that it’s now deprecated and will be sunset on August 23, 2016. We encourage you to skip v201603 and migrate straight to v201605. As with every new version of the AdWords API, we encourage you to carefully review all changes in the release notes and the v201605 migration guide. The updated client libraries and code examples will be published shortly. If you have any questions or need help with migration, please post on the forum or the Ads Developers Plus Page. - Josh Radcliff on behalf of the AdWords API Team", "id": "tag:blogger.com,1999:blog-7815614485808579332.post-6235991145009901362" }, { "title": "AdWords API v201509 sunset reminder", "link": "http://feedproxy.google.com/~r/blogspot/lQlzL/~3/GXBzN3fLqvM/adwords-api-v201509-sunset-reminder.html", "pubDate": "2016-05-19T18:10:13.205Z", "author": "Google Ads Developer Advisor", "content": "<div dir=\"ltr\" style=\"text-align: left;\" trbidi=\"on\">AdWords API v201509 will be <a href=\"https://developers.google.com/adwords/api/docs/sunset-dates\">sunset</a> on June 21, 2016, after which all v201509 API requests will begin to fail. This version was <a href=\"http://googleadsdeveloper.blogspot.com/2015/10/announcing-v201509-of-adwords-api.html\">deprecated</a> on February 2, 2016. If you are still on v201509, we recommend that you skip v201601 and migrate directly to <a href=\"http://googleadsdeveloper.blogspot.com/2016/03/announcing-v201603-of-adwords-api.html\">v201603</a>. Please be sure to migrate prior to sunset to ensure your API access is unaffected. We've prepared various resources to help you with the migration: <ul> <li><a href=\"https://developers.google.com/adwords/api/docs/guides/migration/v201603\">v201603 migration guide</a></li> <li><a href=\"https://developers.google.com/adwords/api/docs/guides/migration/v201601\">v201601 migration guide</a></li> <li><a href=\"https://developers.google.com/adwords/api/docs/reference/\">Release notes</a></li></ul> As always, if you have any questions about this migration, please contact us via the <a href=\"https://groups.google.com/forum/#!forum/adwords-api\">forum</a> or the <a href=\"https://plus.google.com/+GoogleAdsDevelopers\">Ads Developers Plus Page</a>. - Michael Cloonan, AdWords API Team</div><img src=\"http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/GXBzN3fLqvM\" height=\"1\" width=\"1\" alt=\"\"/>", "contentSnippet": "AdWords API v201509 will be sunset on June 21, 2016, after which all v201509 API requests will begin to fail. This version was deprecated on February 2, 2016. If you are still on v201509, we recommend that you skip v201601 and migrate directly to v201603. Please be sure to migrate prior to sunset to ensure your API access is unaffected. We've prepared various resources to help you with the migration: v201603 migration guide v201601 migration guide Release notes As always, if you have any questions about this migration, please contact us via the forum or the Ads Developers Plus Page. - Michael Cloonan, AdWords API Team", "id": "tag:blogger.com,1999:blog-7815614485808579332.post-1685210010231649994" }, { "title": "Sunset of MutateJobService in the AdWords API", "link": "http://feedproxy.google.com/~r/blogspot/lQlzL/~3/nTUTj2RrmUY/sunset-of-mutatejobservice-in-adwords.html", "pubDate": "2016-05-17T15:08:23.147Z", "author": "Google Ads Developer Advisor", "content": "<div dir=\"ltr\" style=\"text-align: left;\" trbidi=\"on\">If you've been following the AdWords API <a href=\"http://googleadsdeveloper.blogspot.com/search/label/sunset\">sunset</a> and <a href=\"http://googleadsdeveloper.blogspot.com/search/label/release\">release announcements</a>, you know that there have been some changes to batch processing: <ul> <li>Version <a href=\"http://googleadsdeveloper.blogspot.com/2015/10/announcing-v201509-of-adwords-api.html\">v201509</a> deprecated <a href=\"https://developers.google.com/adwords/api/docs/reference/v201601/MutateJobService\">MutateJobService</a> and introduced <a href=\"https://developers.google.com/adwords/api/docs/reference/latest/BatchJobService\">BatchJobService</a>.</li> <li>Version <a href=\"http://googleadsdeveloper.blogspot.com/2016/02/announcing-v201601-of-adwords-api.html\">v201601</a> supports both <a href=\"https://developers.google.com/adwords/api/docs/reference/v201601/MutateJobService\">MutateJobService</a> and <a href=\"https://developers.google.com/adwords/api/docs/reference/latest/BatchJobService\">BatchJobService</a> concurrently.</li> <li>Version <a href=\"http://googleadsdeveloper.blogspot.com/2016/03/announcing-v201603-of-adwords-api.html\">v201603</a> doesn't include <a href=\"https://developers.google.com/adwords/api/docs/reference/v201601/MutateJobService\">MutateJobService</a>.</li></ul> The planned <a href=\"http://googleadsdeveloper.blogspot.com/2016/01/new-release-schedule-for-adwords-api.html\">sunset date</a> of version <a href=\"http://googleadsdeveloper.blogspot.com/2016/02/announcing-v201601-of-adwords-api.html\">v201601</a> is August, 2016, after which <code>MutateJobService</code> will no longer be available. What do I need to do? If you are still using <code>MutateJobService</code>, please migrate to <code>BatchJobService</code> ahead of August, 2016. How do I migrate? The migration from MutateJobService to BatchJobService is relatively straightforward and covered in the <a href=\"https://developers.google.com/adwords/api/docs/guides/batch-jobs#migrating_from_mutatejobservice\">migration section of the batch processing guide</a>. The guide also contains <a href=\"https://developers.google.com/adwords/api/docs/guides/batch-jobs#code_examples\">code examples for each client library</a> to help you get started. If you have any questions or need help with migration, please post on the <a href=\"https://developers.google.com/adwords/api/community/\">forum</a> or the <a href=\"https://plus.google.com/+GoogleAdsDevelopers\">Ads Developers Plus Page</a>. <img height=\"40\" width=\"40\" src=\"https://lh6.googleusercontent.com/Kltft4ltAn8Pu1ga0uFUkOSZPLLAXXnEK-4ozIdvNObV7mnlSjZRgY3pFDt323Dxw0UR7nsRVzAEvWbDiE_Io7v1jLbyhnrlDWe18PS4Wl7iYV2glKdkNTRcG50LShndUdVqLzCj\" style=\"vertical-align: middle; border:none;\" /> - <a href=\"https://plus.google.com/100205313733177937765/posts\">Josh Radcliff</a>, AdWords API Team</div><img src=\"http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/nTUTj2RrmUY\" height=\"1\" width=\"1\" alt=\"\"/>", "contentSnippet": "If you've been following the AdWords API sunset and release announcements, you know that there have been some changes to batch processing: Version v201509 deprecated MutateJobService and introduced BatchJobService. Version v201601 supports both MutateJobService and BatchJobService concurrently. Version v201603 doesn't include MutateJobService. The planned sunset date of version v201601 is August, 2016, after which MutateJobService will no longer be available. What do I need to do?If you are still using MutateJobService, please migrate to BatchJobService ahead of August, 2016. How do I migrate?The migration from MutateJobService to BatchJobService is relatively straightforward and covered in the migration section of the batch processing guide. The guide also contains code examples for each client library to help you get started. If you have any questions or need help with migration, please post on the forum or the Ads Developers Plus Page. - Josh Radcliff, AdWords API Team", "id": "tag:blogger.com,1999:blog-7815614485808579332.post-8791945641366304416" }, { "title": "Begin migrating from Flash to HTML5 ads before June 30th", "link": "http://feedproxy.google.com/~r/blogspot/lQlzL/~3/Ye2IfXYTw6U/begin-migrating-from-flash-to-html5-ads.html", "pubDate": "2016-05-09T14:05:16.505Z", "author": "Google Ads Developer Advisor", "content": "<div dir=\"ltr\" style=\"text-align: left;\" trbidi=\"on\">What is changing? <a href=\"https://plus.google.com/+GoogleAds/posts/dYSJRrrgNjk\">Starting June 30, 2016</a>, 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 <a href=\"https://support.google.com/adwords/answer/6249073\">Help Center Article</a> on updating Flash ads to HTML5 ads. If you have video ads built in Flash, they will not be affected at this time. You do not need to migrate these ads. Where can I learn more? <ul> <li><a href=\"https://developers.google.com/adwords/api/docs/guides/template-ads#html5_ads\">HTML5 Ad Examples in the API</a></li> <li><a href=\"https://developers.google.com/adwords/api/docs/appendix/templateads#html5_upload_V1\">HTML5 Template Ads</a></li> <li><a href=\"https://support.google.com/adwordspolicy/answer/176108?hl=en#HTML5\">HTML5 Ad Specifications</a></li> <li><a href=\"https://developers.google.com/adwords/api/docs/clientlibraries#client-libraries\">Ads API Client Libraries</a>: 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: <ul> <li><a href=\"https://developers.google.com/adwords/api/docs/samples/java/advanced-operations#add-an-html-5-ad-to-an-ad-group\">Add an HTML5 ad to an ad group</a></li> <li><a href=\"https://developers.google.com/adwords/api/docs/samples/java/advanced-operations#upload-an-html5-zip-file-as-a-mediabundle\">Upload an HTML5 zip file as a MediaBundle</a></li> </ul> </li></ul> Questions? Visit us on the <a href=\"https://groups.google.com/forum/#!forum/adwords-api\">AdWords API Forum</a> or our <a href=\"https://plus.google.com/115658573333388777174/posts/bA8W5r3KwZb\">Google+ page</a>. <a href=\"https://plus.google.com/109542956637533475940/posts\"><img height=\"40\" width=\"40\" src=\"https://lh5.googleusercontent.com/NIB2rW268qTHsXN3Q83-7IhpnCVtKFEzNqqRtEPPoFrAhvyoHGSxZwYcohyVLi3EQyODrHtGzL223Bw4ZzrWfCfUMkCOpZAkl80taJj2wInfSnrIgoaxPcoNndc10eu5jCfZPq7c\" style=\"vertical-align: middle; border:none;\"/> Nadine Sundquist</a>, AdWords API Team</div><img src=\"http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/Ye2IfXYTw6U\" height=\"1\" width=\"1\" alt=\"\"/>", "contentSnippet": "What is changing? Starting June 30, 2016, 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 Help Center Article on updating Flash ads to HTML5 ads. If you have video ads built in Flash, they will not be affected at this time. You do not need to migrate these ads. Where can I learn more? HTML5 Ad Examples in the API HTML5 Template Ads HTML5 Ad Specifications Ads API Client Libraries: 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: Add an HTML5 ad to an ad group Upload an HTML5 zip file as a MediaBundle Questions? Visit us on the AdWords API Forum or our Google+ page. Nadine Sundquist, AdWords API Team", "id": "tag:blogger.com,1999:blog-7815614485808579332.post-4490476737491658732" }, { "title": "Upcoming changes to AdWords policy names", "link": "http://feedproxy.google.com/~r/blogspot/lQlzL/~3/yOTDtjykum4/upcoming-changes-to-adwords-policy-names.html", "pubDate": "2016-05-03T18:12:23.447Z", "author": "Google Ads Developer Advisor", "content": "<div dir=\"ltr\" style=\"text-align: left;\" trbidi=\"on\">If you submit AdWords API <a href=\"https://developers.google.com/adwords/api/docs/guides/exemption-requests\">exemption requests</a> for policy violations, then you may need to modify your application as a result of <a href=\"https://support.google.com/adwordspolicy/answer/6397420\">these recently announced policy changes</a>. What is changing? For some policy violations, the values of the <a href=\"https://developers.google.com/adwords/api/docs/reference/latest/AdGroupCriterionService.PolicyViolationError#externalpolicyname\">externalPolicyName</a>, <a href=\"https://developers.google.com/adwords/api/docs/reference/v201603/AdGroupCriterionService.PolicyViolationError#externalpolicyurl\">externalPolicyUrl</a>, and <a href=\"https://developers.google.com/adwords/api/docs/reference/v201603/AdGroupCriterionService.PolicyViolationError#externalpolicydescription\">externalPolicyDescription</a> fields on <code>PolicyViolationError</code> will change. What is not changing? The <a href=\"https://developers.google.com/adwords/api/docs/reference/latest/AdGroupCriterionService.PolicyViolationKey#policyname\">policyName</a> field value on <a href=\"https://developers.google.com/adwords/api/docs/reference/latest/AdGroupCriterionService.PolicyViolationError#key\">PolicyViolationError.key</a> will not change. Could you remind me what a PolicyViolationError looks like? Absolutely - glad you asked! In the following sample, after the policy changes go live, the content in <code>externalPolicyName</code>, <code>externalPolicyUrl</code>, and <code>externalPolicyDescription</code> may change, but the <code>policyName</code> field will stay the same. <pre class=\"prettyprint lang-xml\"> <errors xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:type=\"PolicyViolationError\"> <fieldPath>operations[0].operand.ad.headline</fieldPath> <trigger/> <errorString>AdPolicyError.POLICY_ERROR</errorString> <ApiError.Type>PolicyViolationError</ApiError.Type> <key> <policyName>nonstandard_punctuation</policyName> <violatingText>!!!</violatingText> </key> <externalPolicyName>Non-standard punctuation</externalPolicyName> <externalPolicyUrl/>...</externalPolicyUrl> <externalPolicyDescription>Google ads aren't allowed to have excessive or unnecessary punctuation or symbols such as the following: ... &lt;a href=\"https://support.google.com/adwordspolicy/answer/176095\" target=\"_blank\"&gt;See the full policy&lt;/a&gt; </externalPolicyDescription> <isExemptable>true</isExemptable> <violatingParts> <index>18</index> <length>3</length> </violatingParts> </errors> </pre> What should you do? If your application looks for specific values of <code>externalPolicyName</code>, <code>externalPolicyUrl</code>, or <code>externalPolicyDescription</code> to decide if a failed <a href=\"https://developers.google.com/adwords/api/docs/reference/latest/AdGroupAdService.AdGroupAdOperation\">AdGroupAdOperation</a> should be resubmitted with one or more <a href=\"https://developers.google.com/adwords/api/docs/reference/latest/AdGroupAdService.AdGroupAdOperation#exemptionrequests\">ExemptionRequests</a>, please make the following changes: <ol> <li>Modify your application to use the <a href=\"https://developers.google.com/adwords/api/docs/reference/latest/AdGroupCriterionService.PolicyViolationKey#policyname\">policyName</a> instead of one of the <code>externalPolicy</code> fields. The values for <code>policyName</code> are non-localized constants, so this is a more reliable field for this use case.</li> <li>In early June, 2016, monitor your logs for occurrences of <code>PolicyViolationError</code>. Look for any new <code>policyName</code> values that you may want to incorporate into your application's logic for submitting exemption requests.</li></ol> If you have any questions or need help, please post on the <a href=\"https://developers.google.com/adwords/api/community/\">forum</a> or the <a href=\"https://plus.google.com/+GoogleAdsDevelopers\">Ads Developers Plus Page</a>. <img height=\"40\" width=\"40\" src=\"https://lh5.googleusercontent.com/h0lsJ_xsvIvI245vS3Ai1vrBQwMJtbKzKSWecpZstsfg-51Ta3grDd2irb30xvHpwlZLf-tkxvd7ROBqXsDhU5zV5JFcofTWgnYWVx8yxsshtWvCvVPWFPhEX3oOjQXubizMpNGn\" style=\"vertical-align: middle; border:none;\"/> - <a href=\"https://plus.google.com/100205313733177937765/posts\">Josh Radcliff</a>, AdWords API Team</div><img src=\"http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/yOTDtjykum4\" height=\"1\" width=\"1\" alt=\"\"/>", "contentSnippet": "If you submit AdWords API exemption requests for policy violations, then you may need to modify your application as a result of these recently announced policy changes. What is changing?For some policy violations, the values of the externalPolicyName, externalPolicyUrl, and externalPolicyDescription fields on PolicyViolationError will change. What is not changing?The policyName field value on PolicyViolationError.key will not change. Could you remind me what a PolicyViolationError looks like?Absolutely - glad you asked! In the following sample, after the policy changes go live, the content in externalPolicyName, externalPolicyUrl, and externalPolicyDescription may change, but the policyName field will stay the same. <errors xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:type=\"PolicyViolationError\"> <fieldPath>operations[0].operand.ad.headline</fieldPath> <trigger/> <errorString>AdPolicyError.POLICY_ERROR</errorString> <ApiError.Type>PolicyViolationError</ApiError.Type> <key> <policyName>nonstandard_punctuation</policyName> <violatingText>!!!</violatingText> </key> <externalPolicyName>Non-standard punctuation</externalPolicyName> <externalPolicyUrl/>...</externalPolicyUrl> <externalPolicyDescription>Google ads aren't allowed to have excessive or unnecessary punctuation or symbols such as the following: ... <a href=\"https://support.google.com/adwordspolicy/answer/176095\" target=\"_blank\">See the full policy</a> </externalPolicyDescription> <isExemptable>true</isExemptable> <violatingParts> <index>18</index> <length>3</length> </violatingParts></errors> What should you do?If your application looks for specific values of externalPolicyName, externalPolicyUrl, or externalPolicyDescription to decide if a failed AdGroupAdOperation should be resubmitted with one or more ExemptionRequests, please make the following changes: Modify your application to use the policyName instead of one of the externalPolicy fields. The values for policyName are non-localized constants, so this is a more reliable field for this use case. In early June, 2016, monitor your logs for occurrences of PolicyViolationError. Look for any new policyName values that you may want to incorporate into your application's logic for submitting exemption requests. If you have any questions or need help, please post on the forum or the Ads Developers Plus Page. - Josh Radcliff, AdWords API Team", "id": "tag:blogger.com,1999:blog-7815614485808579332.post-4720282933844257873" }, { "title": "A new Java framework for large-scale AdWords API alerting", "link": "http://feedproxy.google.com/~r/blogspot/lQlzL/~3/YXU1YBFBSVw/a-new-java-framework-for-large-scale.html", "pubDate": "2016-04-25T14:15:25.849Z", "author": "Google Ads Developer Advisor", "content": "<div dir=\"ltr\" style=\"text-align: left;\" trbidi=\"on\">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. To reduce the technical barrier of the alerting workflow implementation, we are happy to announce <a href=\"https://github.com/googleads/adwords-alerting\">Alerting Framework on Adwords</a>, 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 <a href=\"https://developers.google.com/adwords/api/docs/appendix/reports\">AdWords report</a> 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 <a href=\"https://github.com/googleads/adwords-alerting/blob/master/src/main/resources/aw-alerting-alerts-sample.json\">sample alerts</a> to explore how it works, or set up your own alerting logic by implementing custom alert entities and plugging them into the system. Get started at the Alerting Framework on AdWords <a href=\"https://github.com/googleads/adwords-alerting\">GitHub repository</a>. If you have any questions or would like to provide feedback, please visit the <a href=\"https://github.com/googleads/adwords-alerting/issues\">project issue tracker</a>, <a href=\"https://groups.google.com/forum/#!forum/adwords-api\">AdWords API Forum</a>, or our <a href=\"https://plus.google.com/+GoogleAdsDevelopers\">Google+ page</a>. Zhuo Chen, AdWords API Team</div><img src=\"http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/YXU1YBFBSVw\" height=\"1\" width=\"1\" alt=\"\"/>", "contentSnippet": "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. To reduce the technical barrier of the alerting workflow implementation, we are happy to announce Alerting Framework on Adwords, 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 AdWords report 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 sample alerts to explore how it works, or set up your own alerting logic by implementing custom alert entities and plugging them into the system. Get started at the Alerting Framework on AdWords GitHub repository. If you have any questions or would like to provide feedback, please visit the project issue tracker, AdWords API Forum, or our Google+ page. Zhuo Chen, AdWords API Team", "id": "tag:blogger.com,1999:blog-7815614485808579332.post-8167222675782360098" }, { "title": "AdWords: Updates to impression share in reporting", "link": "http://feedproxy.google.com/~r/blogspot/lQlzL/~3/ME5jsxi8_Yk/adwords-updates-to-impression-share-in.html", "pubDate": "2016-04-12T14:53:36.866Z", "author": "Google Ads Developer Advisor", "content": "<div dir=\"ltr\" style=\"text-align: left;\" trbidi=\"on\">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 <a href=\"https://developers.google.com/adwords/api/docs/appendix/reports/all-reports#contentbudgetlostimpressionshare\">impression share columns</a> and run Video Campaigns. 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. 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. If you have any questions about this change, or other questions about the AdWords API, please contact us via the <a href=\"https://groups.google.com/forum/#!forum/adwords-api\">forum</a> or the <a href=\"https://plus.google.com/+GoogleAdsDevelopers\">Ads Developers Plus Page</a>. - Michael Cloonan, AdWords API Team</div><img src=\"http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/ME5jsxi8_Yk\" height=\"1\" width=\"1\" alt=\"\"/>", "contentSnippet": "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 impression share columns and run Video Campaigns. 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. 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. If you have any questions about this change, or other questions about the AdWords API, please contact us via the forum or the Ads Developers Plus Page. - Michael Cloonan, AdWords API Team", "id": "tag:blogger.com,1999:blog-7815614485808579332.post-5091548813815873971" }, { "title": "Announcing v201603 of the AdWords API", "link": "http://feedproxy.google.com/~r/blogspot/lQlzL/~3/Vc2DoXlTW5E/announcing-v201603-of-adwords-api.html", "pubDate": "2016-03-23T22:06:35.327Z", "author": "Google Ads Developer Advisor", "content": "<div dir=\"ltr\" style=\"text-align: left;\" trbidi=\"on\">Today we’re announcing the release of <a href=\"https://developers.google.com/adwords/api/docs/reference/#v201603\">AdWords API v201603</a>. This is the second release that follows the <a href=\"http://googleadsdeveloper.blogspot.com/2016/01/new-release-schedule-for-adwords-api.html\">new release schedule announced in January 2016</a>. Here are the highlights: <ul> <li>Campaign drafts and experiments. A new suite of services in v201603 gives you <a href=\"http://adwords.blogspot.com/2016/02/test-with-confidence-using-campaign.html\">more options and control</a> over experimenting with your Search Network and Search Network with Display Select campaign experiments. Check out the new <a href=\"https://developers.google.com/adwords/api/docs/guides/campaign-drafts-experiments\">Campaign Drafts and Experiments guide</a> for all the exciting details! If you're currently using <a href=\"https://developers.google.com/adwords/api/docs/reference/latest/ExperimentService\">ExperimentService</a> to manage your experiments, we recommend migrating to the new suite of services so you can make the most of your experiments.</li> <li>More flexibility with Target CPA and Target Spend. Following the <a href=\"https://plus.google.com/+GoogleAds/posts/FP5XUu5DayT\">revamped workflow for automated bidding announcement</a> last month, the <a href=\"https://developers.google.com/adwords/api/docs/guides/bidding#strategy-types\">TARGET_CPA and TARGET_SPEND (Maximize clicks)</a> 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 <code>TARGET_CPA</code> bidding strategies now support different CPA targets for individual ad groups.</li> <li>Top content bid modifiers. The new <a href=\"https://developers.google.com/adwords/api/docs/reference/v201603/AdGroupBidModifierService.PreferredContent\">PreferredContent</a> criteria type allows you to set a bid modifier for <a href=\"https://support.google.com/adwords/answer/2732132#types\">top content on YouTube or the Google Display Network</a>, and the new <a href=\"https://developers.google.com/adwords/api/docs/appendix/reports/top-content-performance-report\">TOP_CONTENT_PERFORMANCE_REPORT</a> lets you monitor your ad group's performance relative to those bid modifiers.</li> <li>Campaign mobile bid modifier simulations. <a href=\"https://developers.google.com/adwords/api/docs/reference/v201603/DataService\">DataService</a> has new <a href=\"https://developers.google.com/adwords/api/docs/reference/v201603/DataService#getcampaigncriterionbidlandscape\">getCampaignCriterionBidLandscape</a> and <a href=\"https://developers.google.com/adwords/api/docs/reference/v201603/DataService#querycampaigncriterionbidlandscape\">queryCampaignCriterionBidLandscape</a> methods that will return bid simulations for campaign-level <a href=\"https://developers.google.com/adwords/api/docs/appendix/platforms\">HighEndMobile Platform</a> (ID 30001) bid modifiers.</li> <li>Universal app campaigns in reports. Reports now include data for <a href=\"https://support.google.com/adwords/answer/6247380\">Universal App Campaigns</a>. You can identify these campaigns by looking for <a href=\"https://developers.google.com/adwords/api/docs/appendix/reports/all-reports#advertisingchanneltype\">AdvertisingChannelType</a> <code>MULTI_CHANNEL</code> or <a href=\"https://developers.google.com/adwords/api/docs/appendix/reports/all-reports#advertisingchannelsubtype\">AdvertisingChannelSubType</a> <code>UNIVERSAL_APP_CAMPAIGN</code>.</li> <li>Batch processing. <a href=\"https://developers.google.com/adwords/api/docs/reference/latest/BatchJobService\">BatchJobService</a> now supports job cancellation in all versions of the API. <a href=\"https://developers.google.com/adwords/api/docs/reference/v201601/MutateJobService\">MutateJobService</a> has been removed in v201603, so be sure to check out the <a href=\"https://developers.google.com/adwords/api/docs/guides/batch-jobs#migrating_from_mutatejobservice\">migration information</a> if you have not yet transitioned to <code>BatchJobService</code>.</li> <li>Targeting extensions. <a href=\"https://developers.google.com/adwords/api/docs/guides/extension-settings\">Extension setting services</a> now support setting campaign, ad group, keyword, and location targeting for each <a href=\"https://developers.google.com/adwords/api/docs/reference/latest/AdGroupExtensionSettingService.ExtensionFeedItem\">ExtensionFeedItem</a>, as shown in the <a href=\"https://developers.google.com/adwords/api/docs/guides/extension-settings\">updated code examples</a>.</li> <li>Reporting improvements. Ad group bid modifiers are now available via the new <a href=\"https://developers.google.com/adwords/api/docs/appendix/reports/adgroup-performance-report#adgroupmobilebidmodifier\">AdGroupMobileBidModifier</a> field in the <a href=\"https://developers.google.com/adwords/api/docs/appendix/reports/adgroup-performance-report\">ADGROUP_PERFORMANCE_REPORT</a> report. Null values will appear as two dashes (--) for String fields in all reports.</li></ul> If you’re using v201509 of the AdWords API, please note that it’s now deprecated and will <a href=\"https://developers.google.com/adwords/api/docs/sunset-dates\">be sunset</a> on June 21st, 2016. We encourage you to skip v201601 and migrate straight to v201603. As with every new version of the AdWords API, we encourage you to carefully review all changes in the <a href=\"https://developers.google.com/adwords/api/docs/reference/#v201603\">release notes</a> and the <a href=\"https://developers.google.com/adwords/api/docs/guides/migration/v201603\">v201603 migration guide</a>. The updated <a href=\"https://developers.google.com/adwords/api/docs/clientlibraries\">client libraries</a> and code examples will be published shortly. With this release, we’ve also updated the <a href=\"https://developers.google.com/adwords/api/docs/requirements\">Required Minimum Functionality document</a> to include some of the newly added features. If you have any questions or need help with migration, please post on the <a href=\"https://developers.google.com/adwords/api/community/\">forum</a> or the <a href=\"https://plus.google.com/+GoogleAdsDevelopers\">Ads Developers Plus Page</a>. <img height=\"40\" width=\"40\" src=\"https://lh5.googleusercontent.com/ibeUI_8AfTMqP8C6MzGeu8neKIdTgjjffkt4vIFiwlHjlyAeF-_9zLRfKL8N8X2DQJ5nqH5BJdRUhso-ghq6fvQlVsw1no1d9KWj-iiRbBFZJBcLKowhH4awsvGh3Kdt5PlLJOk2\" style=\"vertical-align: middle; border:none;\"/> - <a href=\"https://plus.google.com/100205313733177937765/posts\">Josh Radcliff</a> <a href=\"https://plus.google.com/100205313733177937765/posts\">on behalf of</a> the AdWords API Team</div><img src=\"http://feeds.feedburner.com/~r/blogspot/lQlzL/~4/Vc2DoXlTW5E\" height=\"1\" width=\"1\" alt=\"\"/>", "contentSnippet": "Today we’re announcing the release of AdWords API v201603. This is the second release that follows the new release schedule announced in January 2016. Here are the highlights: Campaign drafts and experiments. A new suite of services in v201603 gives you more options and control over experimenting with your Search Network and Search Network with Display Select campaign experiments. Check out the new Campaign Drafts and Experiments guide for all the exciting details! If you're currently using ExperimentService to manage your experiments, we recommend migrating to the new suite of services so you can make the most of your experiments. More flexibility with Target CPA and Target Spend. Following the revamped workflow for automated bidding announcement last month, the TARGET_CPA and TARGET_SPEND (Maximize clicks) 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 TARGET_CPA bidding strategies now support different CPA targets for individual ad groups. Top content bid modifiers. The new PreferredContent criteria type allows you to set a bid modifier for top content on YouTube or the Google Display Network, and the new TOP_CONTENT_PERFORMANCE_REPORT lets you monitor your ad group's performance relative to those bid modifiers. Campaign mobile bid modifier simulations. DataService has new getCampaignCriterionBidLandscape and queryCampaignCriterionBidLandscape methods that will return bid simulations for campaign-level HighEndMobile Platform (ID 30001) bid modifiers. Universal app campaigns in repo