Google Ads Developer Blog: reports

Support for v201809 reports in Google Ads Scripts

Monday, January 28, 2019

We have added support for AdWords API v201809 reports in Google Ads Scripts. The key changes in this release include:

The DESTINATION_URL_REPORT has been removed. Use the FINAL_URL_REPORT instead.
New conversion fields have been added to multiple reports:
- ConversionAttributionEventType (CAMPAIGN_PERFORMANCE_REPORT only)
- ConversionAdjustment
- ConversionAdjustmentLagBucket

Read the AdWords API release notes for complete details, including additional features not listed here.

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

var report = AdsApp.report(query, {
  apiVersion: 'v201809'
});

If you don't use API versioning, no code changes are required. We are updating the default reporting version to v201806 along with this change, and your reports will upgrade automatically.

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

- Mike Cloonan, Google Ads Scripts Team

New features in AdWords scripts

Wednesday, July 18, 2018

Today we're announcing the launch of a few new features in AdWords scripts:

Support for reporting version v201806
Multi-file script support
Support for final URL suffix for parallel tracking

Reporting
Support for v201806 of reports has been added. The main features in this reporting version are:

New fields for Responsive Search Ads and Multi-Asset Responsive Display Ads.
The ClickType and CampaignSubType columns will return new values to reflect changes in product names. The underlying data is unaffected; the rendered value is the only change. For example, the CampaignSubType of "Product Listing Ads" will now be "Shopping ads", and there are similar changes for ClickType.

Read the AdWords API release notes for complete details, including additional features not listed here.

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

var report = AdWordsApp.report(query, {
  apiVersion: 'v201806'
});

We will also be updating the default reporting version from v201710 to v201802 on July 23, 2018. This will affect you if you do not use API versioning as outlined above.

Multi-File Support
Over the next few weeks, we will be rolling out support for scripts with multiple files. This lets you separate your utility logic from your business logic, organize your code however you see fit, and generally produce more maintainable scripts. Please try it out and let us know what you think on the forum!

Parallel Tracking Support
We have added methods to support the final URL suffix for parallel tracking. You can use the new getFinalUrlSuffix, setFinalUrlSuffix, and clearFinalUrlSuffix methods on objects that have final URLs.

As announced earlier this year, starting October 30, 2018, parallel tracking will be required for all AdWords accounts. You can consult the AdWords API documentation on click tracking for more details on how to migrate, as the same concepts apply to scripts. Please make sure to update your scripts before the deadline.

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

- Mike Cloonan, AdWords Scripts Team

Click measurement changes in AdWords

Monday, May 7, 2018

Update (5/17): Starting October 30, 2018, parallel tracking will be required for all AdWords accounts. See the AdWords blog post for details.
AdWords now allows you to enable parallel tracking for all advertisers from frontend and API. People who click your ads will go directly to your landing page while their browser handles click measurement requests in the background. This helps reduce lost visits which can happen if a customer clicks on your ad but never sees your landing page because they navigate away before the redirect from your tracking URL completes.

All ads using third-party click measurement will begin using parallel tracking at a later date. However, you should start developing for compatibility as soon as possible to give yourself enough time for the migration. If you implement your own click measurement server or provide this service to your customers, refer to our newly published guide for help with implementation. If you are an advertiser who uses a third-party measurement solution, reach out to your service provider to prepare for the switch.

If you need additional support, please email us at ads-clicktracking-support@google.com.

- Anash P. Oommen, AdWords API Team

Support for v201802 reports in AdWords scripts

Wednesday, March 28, 2018

We have added support for AdWords API v201802 reports in AdWords scripts. The key changes in this release include:

A new report type, LANDING_PAGE_REPORT, to provide performance stats for the pages that receive traffic from your ads.
ConversionLagBucket field added to various reports to help you determine how long it takes customers to convert.
New fields added to support Gmail ads.

Read the AdWords API release notes for complete details, including additional features not listed here.

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

var report = AdWordsApp.report(query, {
  apiVersion: 'v201802'
});

If you don't use API versioning, no code changes are required. We are updating the default reporting version to v201710 along with this change, and your reports will upgrade automatically.

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

Upcoming changes to ad network type columns in AdWords API and Scripts reports

Tuesday, February 20, 2018

On March 19, 2018, we are updating how AdNetworkType1 and AdNetworkType2 columns report zero impression rows related to video networks.

Currently, if you request AdNetworkType1 or AdNetworkType2 columns and request zero impression rows by setting the includeZeroImpressions flag to true, you get back zero impression rows for YOUTUBE_SEARCH and YOUTUBE_WATCH values only if you target these networks in your Advertiser account. After this change, we will always return zero rows corresponding to these network types irrespective of whether you advertise on these networks. Other network types are not affected by this change.

This change makes the behavior of YOUTUBE_SEARCH and YOUTUBE_WATCH network types consistent with the behavior of other network types. Once this change goes live, you may start seeing a higher number of zero impression rows than what you see today when requesting AdNetworkType1 or AdNetworkType2 columns along with zero impression rows.

If you have any questions about these changes, post them in our developer forum.

- Anash P. Oommen, AdWords API Team

Changes to AdWords Express campaigns in AdWords API reports

Friday, November 10, 2017

If you use AdWords API reports to retrieve performance statistics for AdWords Express campaigns, please read on as these changes will affect you.

What's changing?
In preparation for upcoming improvements, an ongoing migration process is modifying campaigns managed by AdWords Express.

Currently, when you enable an AdWords Express promotion, it creates up to two AdWords campaigns:

A Search Network campaign with:
- AdvertisingChannelType = SEARCH (appears as Search)
- AdvertisingChannelSubType = SEARCH_EXPRESS (appears as Search Express)
A Display Network campaign with:
- AdvertisingChannelType = DISPLAY (appears as Display)
- AdvertisingChannelSubType = DISPLAY_EXPRESS (appears as Display Express)

As part of the migration, the two campaigns above will be paused and replaced by a single AdWords campaign with:

AdvertisingChannelType = EXPRESS (appears as Express)
AdvertisingChannelSubType = UNKNOWN (appears as an empty string)

After the campaigns for a promotion are migrated, performance statistics for the AdWords Express promotion will be available in reports as follows:

Performance statistics for dates prior to the migration will be attributed to the original campaigns with SEARCH / SEARCH_EXPRESS and DISPLAY / DISPLAY_EXPRESS.
Performance statistics for dates after the migration will be attributed to the new campaign with EXPRESS / UNKNOWN. The new campaign will only appear in the CAMPAIGN_PERFORMANCE_REPORT.

For example, assume an AdWords Express promotion manages the following two AdWords campaigns today:

Campaign ID	Campaign Status	Advertising Channel Type	Advertising Channel Sub Type
1000	ENABLED	SEARCH	SEARCH_EXPRESS
2000	ENABLED	DISPLAY	DISPLAY_EXPRESS

After the migration, the account will contain the following campaigns for the AdWords Express promotion:

Campaign ID	Campaign Status	Advertising Channel Type	Advertising Channel Sub Type	Performance statistics
1000	PAUSED	SEARCH	SEARCH_EXPRESS	Before the migration
2000	PAUSED	DISPLAY	DISPLAY_EXPRESS	Before the migration
3000	ENABLED	EXPRESS	UNKNOWN	After the migration

What should you do?
Ensure that your application properly handles all three combinations of AdvertisingChannelType and AdvertisingChannelSubType. For example:

If your application inspects AdvertisingChannelType or AdvertisingChannelSubType to handle AdWords Express campaigns, please adjust the logic to handle the new combination of EXPRESS / UNKNOWN.
If you use predicates on AdvertisingChannelType or AdvertisingChannelSubType to include or exclude AdWords Express campaigns, make sure that your predicate takes the new combination into account.

Reminder: The AdWords API only supports retrieving AdWords Express entities. You cannot modify AdWords Express entities in your account using the AdWords API.

If you have any questions about this change, please contact us via the forum.

- Josh Radcliff, AdWords API Team

Support for v201702 reports in AdWords scripts

Tuesday, March 28, 2017

We have added support for AdWords API v201702 reports in AdWords scripts. The major changes in this release are:

New conversion fields to help when changing attribution models: CostPerCurrentModelAttributedConversion, CurrentModelAttributedConversions, CurrentModelAttributedConversionValue, and ValuePerCurrentModelAttributedConversion
Fields of type Double that don't represent percentages now return without a thousands separator and with two decimal places.
The AdGroupName and AdGroupStatus fields of the Audience Performance Report now behave as segments
All fields in the Call Metrics Call Details Report now behave as attributes

See the AdWords API release notes for more details.

v201609 will remain the default version for reports until the week of April 24, 2017. 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 v201702:

var report = AdWordsApp.report(query {
  apiVersion: 'v201702'
});

If you don't use API versioning, no code changes are required. Your reports will continue using v201609 for now, and switch to v201702 when we make v201702 the default version the week of April 24, 2017.

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

Support for v201609 reports in AdWords Scripts

Wednesday, November 2, 2016

We have added support for AdWords API v201609 reports in AdWords Scripts. The major changes in this release are:

The ClickType column is no longer compatible with fields for other types of interactions, such as AverageCpe, AverageCpv, VideoViewRate, and more. See a complete list in the v201609 migration guide.
The ExternalConversionSource field was added to several reports to allow segmentation of conversions by source.
The AUDIENCE_PERFORMANCE_REPORT no longer returns rows for excluded criteria.
All fields related to AdWords Campaign Experiments have been removed, as the feature is being sunset.

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

Thursday, October 20, 2016

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.

- Anash P. Oommen, AdWords API Team

Support for v201607 reports in AdWords Scripts

Friday, October 7, 2016

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.

- Anash P. Oommen, AdWords Scripts Team

New dates for quality score changes in AdWords scripts

Friday, September 16, 2016

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

Monday, August 15, 2016

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

Support for v201605 reports in AdWords Scripts

Wednesday, July 6, 2016

We have added support for AdWords API v201605 reports in AdWords Scripts. The major changes in this release are:

The CRITERIA_PERFORMANCE_REPORT now returns rows for criteria types that are not supported in the AdWords API version of the report request. Rows for these criteria appear in the report with CriteriaType value unknown.

The KeywordId field on the AD_PERFORMANCE_REPORT was renamed to CriterionId since this field contains IDs for keywords as well as other criterion types.

The KeywordId field on the PLACEHOLDER_FEED_ITEM_REPORT was renamed KeywordTargetingId for consistency and clarity.

Several geo-specific columns were removed from the CLICK_PERFORMANCE_REPORT. For geographic information, use the AoiMostSpecificTargetId and LopMostSpecificTargetId fields instead.

All the final URL columns were removed from the PRODUCT_PARTITION_REPORT because final URLs cannot be specified for ProductPartition criteria.

Since CAMPAIGN_PERFORMANCE_REPORT now includes the CampaignMobileBidModifier field in all versions of the reports, CAMPAIGN_PLATFORM_TARGET_REPORT was removed.

See the AdWords API release notes for more details. v201603 will remain the default version of the reports until July 20, 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 v201605: var report = AdWordsApp.report(query, { apiVersion: 'v201605' }); If you don’t use API versioning, no code changes are required. Your reports will continue using v201603 for now, and switch to v201605 when we make v201605 the default version on July 20, 2016. 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

Support for v201603 reports in AdWords Scripts

Tuesday, May 3, 2016

We have added support for AdWords API v201603 reports in AdWords scripts. The major changes in this release are:

See the AdWords API release notes for more details.

Starting from this release, we will not switch to the latest reporting version on the day of the release by default. Instead, we will keep the previous report version as the default version for a while before switching to the latest reports version. This will give 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 v201603 as shown below.

var report = AdWordsApp.report(query, {
   apiVersion: 'v201603'
});

If you don’t use API versioning, no code changes are required. Your reports will continue using v201601 for now, and switch to v201603 when we make v201603 the default version on May 17, 2016.

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

Support for v201601 reports in AdWords Scripts

Friday, February 19, 2016

We have added support for AdWords API v201601 reports in AdWords scripts. The major changes in this release are:

The new PARENTAL_STATUS_PERFORMANCE_REPORT is now available. This report lets you view stats and targeting information by the new Parent criterion type.

CRITERIA_PERFORMANCE_REPORT now includes stats for Parental status and Custom affinity criteria. These were filtered out in older report versions.

Some obsolete columns (AvgCostForOfflineInteraction, OfflineInteractionCost, TotalCost) related to phone calls have been removed from various reports.

Several new fields have been added to existing reports.

The release also introduces some improvements to several reports in existing versions (v201506, v201509).

The CALL_METRICS_CALL_DETAILS_REPORT now allows you to specify a date range via the DURING clause of your AWQL statement.

The CRITERIA_PERFORMANCE_REPORT now returns REMOVED ProductPartition criteria if those criteria have statistics. Previously, REMOVED ProductPartition criteria did not appear in this report.

The StartTime and EndTime columns on the PLACEHOLDER_FEED_ITEM_REPORT can now be used for filtering in report requests for all versions.

See our release notes for more details. If you use API versioning in your reports, you need to modify your code to use v201601 as shown below. If you don’t use API versioning, no code changes are required.var report = AdWordsApp.report(query, { apiVersion: 'v201601' }); 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

Support for v201509 reports in AdWords Scripts

Wednesday, October 21, 2015

We have added support for AdWords API v201509 reports in AdWords scripts. Changes to conversion columnsThis release includes several changes that coincide with the recent announcement on conversion columns. Several reporting columns were removed and new columns were added. See the AdWords API release notes for more details. Video and multi-channel reportingWe are now including statistics and metrics for AdWords for video and TrueView video campaigns in several reports. This includes a new Video Performance Report. Note that reports will only include data for newly created video campaigns in AdWords campaign management or campaigns that were migrated from AdWords for video. We have also added new reporting columns that help multi-channel advertisers more easily manage reporting for specific campaign types like Search, Shopping, Display, and Video. See Video and multi-channel reporting changes for more details. Miscellaneous reporting changes

All columns that have a List or Map return type now return data in JSON format.

Shared set type is now returned as an ENUM instead of an Integer in SHARED_SET_REPORT and CAMPAIGN_SHARED_SET_REPORT.

Several new columns have been added to existing reports.

A few duplicate columns in existing reports were removed.

MatchType and MatchTypeWithVariant columns were renamed to QueryMatchType and QueryMatchTypeWithVariant in PAID_ORGANIC_QUERY_REPORT and SEARCH_QUERY_PERFORMANCE_REPORT.

See Miscellaneous reporting changes for more details. If you use API versioning in your reports, you need to modify your code to use v201509 as shown below. If you don’t use API versioning, no code changes are required. var report = AdWordsApp.report(query, { apiVersion: 'v201509' }); developer forum

- Anash P. Oommen, AdWords API Team

Support for v201506 reports in AdWords Scripts

Monday, September 21, 2015

We have added support for AdWords API v201506 reports in AdWords Scripts. This version adds support for FINAL_URL_REPORT, the Upgraded URLs-compatible replacement for the DESTINATION_URL_REPORT.

This version also introduces several changes to the reporting columns

The following new columns have been added to the existing reports:

Column	Reports
AdGroupStatus	PLACEHOLDER_FEED_ITEM_REPORT
CampaignName	CAMPAIGN_NEGATIVE_KEYWORDS_PERFORMANCE_REPORT CAMPAIGN_NEGATIVE_LOCATIONS_REPORT CAMPAIGN_NEGATIVE_PLACEMENTS_PERFORMANCE_REPORT
CampaignStatus	CAMPAIGN_NEGATIVE_KEYWORDS_PERFORMANCE_REPORT CAMPAIGN_NEGATIVE_LOCATIONS_REPORT CAMPAIGN_NEGATIVE_PLACEMENTS_PERFORMANCE_REPORT CAMPAIGN_SHARED_SET_REPORT PLACEHOLDER_FEED_ITEM_REPORT
EndDate	CAMPAIGN_PERFORMANCE_REPORT
FinalUrl	SEARCH_QUERY_PERFORMANCE_REPORT
StartDate	CAMPAIGN_PERFORMANCE_REPORT

If you use API versioning in your reports, then you need to modify your code to use v201506 as shown below. If you don’t use API versioning, no code changes are required.

var report = AdWordsApp.report(query, {
   apiVersion: 'v201506'
});

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

Anash P. Oommen, AdWords Scripts Team

Changes to DFP Reporting, now with more deprecation!

Tuesday, August 4, 2015

After our last round of spring cleaning, we've gone back to the drawing board to take another look at how we could make reporting better. There currently is an abundance of Dimensions, DimensionAttributes, and Columns (and more coming with each release), so in an effort to simplify the list of fields, we will be sunsetting the following reconciliation-related dimension attributes / columns in all versions. This will happen on September 1, 2015.Columns with equivalent replacements:

RECONCILIATION_LAST_DATE_TIME replaced by dimension attribute: PROPOSAL_LINE_ITEM_LAST_RECONCILIATION_DATE_TIME and LINE_ITEM_LAST_RECONCILIATION_DATE_TIME

RECONCILIATION_RECONCILIATION_STATUS replaced by dimension attribute: PROPOSAL_LINE_ITEM_RECONCILIATION_STATUS and LINE_ITEM_RECONCILIATION_STATUS

Columns without equivalent replacements:

LINE_ITEM_RECONCILED_RATE (in <= v201502)

CONTRACTED_REVENUE_CONTRACTED_PLACEMENT_NET_REVENUE (in <= v201411)

CONTRACTED_REVENUE_CONTRACTED_PLACEMENT_GROSS_REVENUE (in <= v201411)

DISCOUNT_BREAKDOWN_ADDITIONAL_ADJUSTMENT (in <= v201411)

While the first two have equivalent replacements, the latter ones are not being replaced, as they don’t exist in core product reporting either.This means that usage of these columns / dimension attributes will begin throwing errors in all versions starting September 1st. If your network is actively using any of these, please update your reports to switch to the supported fields or remove them entirely. If you have any questions, comments, or concerns about this, you know where to reach us!

- Nicholas Chen, DFP API Team

Upcoming changes to Paid and Organic Query report

Thursday, June 11, 2015

We are updating the Paid and Organic report to include only text ad statistics. Impressions and clicks for mobile app install ads and Product Listing Ads will be excluded from this report starting July 13, 2015.

These formats serve in places other than on search results, so we are excluding them to provide you a better comparison across paid and organic listings at the query level. If you use data from the Paid and Organic report in any of your AdWords API or Scripts applications, then make sure you update them to adjust for this data change. Historic stats for mobile app install ads and Product Listing Ads will continue to be available from this report type up to the following report dates:

Product Listing Ads - up to and including March 23, 2015
Mobile app install ads - up to and including July 13, 2015

If you have any further questions about this change, let us know via the API or scripts forum, or Google+ page.

Anash P. Oommen, AdWords API Team

New features in AdWords scripts

Wednesday, November 5, 2014

We have added the following new features in AdWords scripts.

Ad customizers
AdWords scripts now support ad customizers, a more advanced version of ad params. Ad customizers adapt your text ads to the full context of a search or the webpage someone's viewing, by inserting a customized parameter within the ad. Ad customizers let you customize your ads for each query without having to create a separate ad for each variation.

AdWords scripts allow you to create ad customizer sources, add or update items in the sources, and create parameterized ads. You can also target an ad customizer item to a specific campaign, ad group or keyword, and track the performance of ad customizers using the PLACEHOLDER_FEED_ITEM_REPORT.

To learn more about ad customizers, refer to our code snippets and guide. Also, check out the brand new ad customizers solution that shows how to use this new feature in your account.

v201409 reports
We now support AdWords API v201409 reports in AdWords scripts. See blog post for more details.

Product ads
You can now retrieve your product ads using the ads() method of the ShoppingAdGroup. You can create new product ads using the newAdBuilder() method of ShoppingAdGroup.

We hope you enjoy these new features. If you have any questions about these features or AdWords scripts in general, you can post them on the developer forum.

Anash P. Oommen, AdWords Scripts Team

Ads Developer Blog

Support for v201809 reports in Google Ads Scripts

New features in AdWords scripts

Click measurement changes in AdWords

Support for v201802 reports in AdWords scripts

Upcoming changes to ad network type columns in AdWords API and Scripts reports

Changes to AdWords Express campaigns in AdWords API reports

Support for v201702 reports in AdWords scripts

Support for v201609 reports in AdWords Scripts

Changes to ClickType field compatibility in AdWords API & Scripts Reports

Support for v201607 reports in AdWords Scripts

New dates for quality score changes in AdWords scripts

Changes to quality score in AdWords scripts

Support for v201605 reports in AdWords Scripts

Support for v201603 reports in AdWords Scripts

Support for v201601 reports in AdWords Scripts

Support for v201509 reports in AdWords Scripts

Support for v201506 reports in AdWords Scripts

Changes to DFP Reporting, now with more deprecation!

Upcoming changes to Paid and Organic Query report

New features in AdWords scripts

Labels

Archive

Feeds

Google Ads API [+]

AdWords API [+]

Google Ads scripts [+]

Content API for Shopping [+]

Google Ad Manager API [+]

DCM API [+]

Mobile Ads [+]

IMA SDK [+]

More Google blogs