Tag Archives: adwords_scripts

Support for v201609 reports in AdWords Scripts

We have added support for AdWords API v201609 reports in AdWords Scripts. The major changes in this release are: See the AdWords API release notes for more details.

The v201607 will remain the default version for reports until the week of November 28, 2016. This gives you enough time to verify your scripts and make sure they work with the latest report version.

If you use API versioning in your reports, you need to modify your code to use v201609: 

var report = AdWordsApp.report(query {
  apiVersion: 'v201609'
});
If you don't use API versioning, no code changes are required. Your reports will continue using v201607 for now, and switch to v201609 when we make v201609 the default version the week of November 28, 2016.

If you have any questions about these changes or AdWords scripts in general, you can post them on our developer forum.
- Mike Cloonan, AdWords API Team

Changes to ClickType field compatibility in AdWords API & Scripts Reports

We are marking the ClickType column in AdWords API and Scripts reports as incompatible with the following engagement and video-related fields in version v201607 and earlier:
  • AverageCpe
  • EngagementRate
  • VideoQuartile25Rate
  • VideoQuartile50Rate
  • VideoQuartile75Rate
  • VideoQuartile100Rate
  • VideoViews
  • VideoViewRate
  • AverageCpv
These fields refer to engagement and video view interactions, and aren’t compatible with the ClickType column, a click interaction metric. This restriction is already enforced in v201609 reports, see our migration guide for more details.

Starting Dec 1, 2016, you will get a ReportDefinitionError.INVALID_FIELD_NAME_FOR_REPORT error if ClickType column is requested with any of these fields.

Questions? Visit us on the AdWords API Forum or our Google+ page.
 - , AdWords API Team

Support for new ad formats in AdWords Scripts

AdWords scripts now fully support responsive ads, image ads, HTML5 ads and multiple Gmail ad formats. See our guideon ad types and related code snippets to learn more about using these ad formats in Scripts.

This update also introduces a media service which can be used to upload and query media for use in ads. See our ad media guide for a more detailed overview of media support.

If you have any questions about these changes or AdWords scripts in general, you can post them on our developer forum.

 - , AdWords Scripts Team

Changes to Conversion-related stats in AdWords Scripts

We are making two changes related to how various conversion-related stats are retrieved in AdWords Scripts.

New methods for Conversion stats

We are reintroducing two methods in the AdWordsApp.​Statsand MccApp.​ManagedAccountStatsclasses to work with Conversions.

Note: Since Conversions is a stat of type Double, the equality operators (= and !=) won’t work with these new methods when using the withCondition filters or comparing values in code. Instead, you need to use comparison operators like < and >or round Conversions off to an Integer.

Sunsetting ConvertedClicks

As part of sunsetting Converted clicks in AdWords, we are deprecating the getConvertedClicks()and getClickConversionRate()methods in the AdWordsApp.​Statsand MccApp.​ManagedAccountStatsclasses. These methods will be sunset on February 21, 2017.

If your scripts use these methods, update them to use the new Conversion stats methods if applicable before February 21, 2017 to ensure they continue to work.

If you have any questions about these changes please reply to this email or post them on our developer forum and we'll be glad to help you.

 - , AdWords Scripts Team

Support for v201607 reports in AdWords Scripts

We have added support for AdWords API v201607 reports in AdWords scripts. The major changes in this release are: See the AdWords API release notes for more details.

v201605 will remain the default version for reports until the week of October 10th, 2016. This gives you enough time to verify your scripts and make sure it works with the latest report version.

If you use API versioning in your reports, you need to modify your code to use v201607: 

var report = AdWordsApp.report(query, {
   apiVersion: 'v201607'
});
If you don’t use API versioning, no code changes are required. Your reports will continue using v201605 for now, and switch to v201607 when we make v201607 the default version the week of October 10th, 2016.

If you have any questions about these changes or AdWords scripts in general, you can post them on our developer forum.
 - , AdWords Scripts Team

Support for Search Audiences in AdWords Scripts

AdWords Scripts now supports Audiences for Search and Shopping campaigns. This release covers all the features you can do through the Audiences Tab in the AdWords UI - target or exclude audiences for an ad group, exclude audiences for a campaign, and apply or adjust bid modifiers. You may also retrieve audiences and their stats associated with ad groups and campaigns. Audience creation is not supported in this release.

See the code snippets to learn how to use this feature. As always, let us know your questions and feedback on our developer forum.

 - , AdWords Scripts Team

New dates for quality score changes in AdWords scripts

We recently announced some changes to the way AdWords scripts returns quality score data for keywords. To give developers more time to review their scripts that rely on Quality Scores in preparation for this update, null Quality Scores will now roll out on the the week of October 10th, 2016.

If you need help updating your script, or have any questions about these changes or AdWords scripts in general, you can post them on our developer forum.
Anash P. Oommen, AdWords Scripts Team

Changes to quality score in AdWords scripts

We are making some changes to the way AdWords scripts returns quality score data for keywords.

We will return a null quality score for keywords that don’t have enough impressions and clicks to determine a Quality Score, such as new keywords or old ones that haven't served a long time. This will impact your scripts in two ways:
  • Reports: Starting with version v201607, the Critieria Performance and Keywords Performance reports will return a quality score of “--” for these keywords. Past versions (v201605 and earlier) of these reports will remain unchanged.
  • getQualityScore method: Starting the week of Sep 12, 2016, the getQualityScore method of the Keyword entity will return NULL score for these keywords instead of a numeric value.
If you use use quality score information in your script, please make sure you update it to work with the new changes.

Filtering on quality score

Filtering on quality score will work as follows:
  • If no filtering conditions are specified on the QualityScore field, all matching keywords are returned, including those with NULL quality score.
  • If numerical filtering conditions are specified on the QualityScore field, keywords with NULL quality score information are excluded automatically. For example, QualityScore <= 6 will include keywords with quality score from 1 to 6 but exclude keywords with NULL quality score.
  • To retrieve keywords with NULL quality score, filter using the condition HasQualityScore = FALSE.
  • To retrieve keywords with NULL quality score along with keywords with specific quality scores, you need to run two separate reports and combine the results locally.
If you have any questions about these changes or AdWords scripts in general, you can post them on our developer forum.

Anash P. Oommen, AdWords Scripts Team

Expanded Support for Device Bid Modifiers in AdWords Scripts

Along with the AdWords UI and API, AdWords scripts will be rolling out support for desktop and tablet bid modifiers (in addition to mobile) to accounts over the coming weeks. This functionality will be available for ad groups in the new AdGroupDevices class. For campaigns, you will be able to use the new tablet() and desktop() methods in the PlatformSelector class. See our code examples for ad groups and campaigns to learn more about using these methods.

Note: During the rollout, if the feature is not yet enabled in your account, attempts to set tablet and desktop bid modifiers will fail.

With this launch, the getMobileBidModifier() and setMobileBidModifier() methods of the AdGroup and ShoppingAdGroup classes will be deprecated. Updating existing scripts to use the new ad group interface is straightforward. For example, adGroup.getMobileBidModifier() becomes adGroup.devices().getMobileBidModifier().

If you have any questions about these changes or AdWords scripts in general, you can post them on our developer forum.

Jason Goodman, AdWords Scripts Team

Support for Expanded Text Ads in AdWords Scripts

The expanded text ad format is now fully supported in Scripts. Expanded text ads are the next generation of the standard AdWords text ad and are optimized for smartphone screen sizes. The new format features two headlines, each up to 30 characters, and one 80-character description line. See our guide on ad types and related code snippets to learn more about using expanded text ads in Scripts.

Along with the AdWords user interface, AdWords scripts will stop supporting the creation of standard text ads on October 26, 2016. If you use the AdGroup.newTextAdBuilder() method to create standard text ads, be sure to update your scripts to use the new ExpandedTextAdBuilder class. Existing standard text ads will continue to serve beyond this date and scripts will still be able to retrieve them.

If you have any questions about these changes or AdWords scripts in general, you can post them on our developer forum.

Jason Goodman, AdWords Scripts Team