Google Ads Developer Blog

Announcing v201908 of the Google Ad Manager API

Tuesday, August 13, 2019

We're happy to announce that v201908 of the Google Ad Manager API is available starting today. There are several highly requested features in this new version of the API.

Reporting

You can now access “Advertiser (Classified)” and “Brand (Classified)” dimensions through the API.
We’ve also added the dimensions and metrics for calculating video sell-through.

Programmatic

Programmatic LineItems and ProposalLineItems now have an allowedFormats field, which gives publishers more control over what types of creatives a buyer can add.

LiveStreamEvents

You can now use the slateCreativeId field to programmatically set live stream slates, which are shown during gaps in a live stream ad break that cannot be filled with a dynamically served ad.

The release notes contain the full list of API changes for v201908.

If you have questions about these or any other API changes, reach out to us on the Ad Manager API forums.

- Donovan McMurray, Ad Manager API Team

Announcing v2_1 of the Google Ads API beta

Thursday, August 8, 2019

Today we’re announcing the v2_1 releases of the Google Ads API beta. To use the v2_1 features via the new endpoint, please update update your client libraries. If you are upgrading from v1, some of your code may break when you switch to the new v2 endpoint. Please see the migration guide for more information on breaking changes.

Here are the highlights:

Introduced AdService for updating existing ads that were created using AdGroupAdService. Updating ads maintains existing metrics.
Introduced summary rows when retrieving data from GoogleAdService.Search() by setting return_summary_row to true in the request. The summary row contains the report totals.
Introduced the AdGroupAdAssetView resource for querying ad asset metrics.
Introduced the DistanceView resource (equivalent to the User Ad Distance Report in the AdWords API).
Introduced the UserLocationView resource (equivalent to the Geo Performance Report where isTargetingLocation is false in the AdWords API).
Added the ability to retrieve all label resource names associated with the AdGroup resource using AdGroup.labels and with the Campaign resource using Campaign.labels.
Added time_zone, test_account, manager, descriptive_name, currency_code, and id to CustomerClient to make it easier to retrieve customers in an account hierarchy.

Where can I learn more?
The following resources can help you get going with the Google Ads API:

The updated client libraries and code examples will be published by August 16. If you have any questions or need additional help, please contact us via the forum.

Nadine Sundquist, on behalf of the Google Ads API Team

Google Ads scripts now supports price extensions

Thursday, August 8, 2019

We’re excited to announce support for price extensions in Google Ads scripts starting today.

Price extensions allow you to add details about your business’s offerings and prices to a text ad, and are supported at the account, ad group, and campaign level.

You can see how to implement price extensions in our AdsApp.Extensions documentation, or check out some example code using these extension types.

If you have any questions or concerns, please don't hesitate to contact us via our Google Ads Scripts forum.

-Tina Nguyen, Google Ads scripts Team

DCM/DFA Reporting and Trafficking API v3.2 sunset reminder

Monday, August 5, 2019

In accordance with our deprecation schedule, we will be sunsetting version 3.2 of the API on August 31, 2019. Requests to version 3.2 will no longer work after this date, preventing you from updating and accessing information in Campaign Manager. To avoid an interruption in service, you must migrate to a newer API version as soon as possible.

To learn about changes between versions and get tips for migrating, visit the API developer site. Also consider subscribing to this blog to stay up to date about new releases, upcoming sunsets, and changes to the API.

If you have technical questions regarding new versions of the API, please reach out via the developer forum.

- Jonathon Imperiosi, DCM API Team

Sunset of the Average Position Metric in AdWords and Google Ads APIs

Thursday, July 25, 2019

Update (Jul 30, 2019): clarified the sunset schedule.

Starting the week of September 30, 2019, the average position metric will be sunset. This change was announced this past February in the Google Ads Help Center. The new alternatives were described in this November 2018 blog post. Once the sunset occurs, requests for the average position (AdWords API, Google Ads API) will return NULL values.

In the AdWords API v201809, NULL values are returned as two dashes. In the Google Ads API, NULL values are returned as NullValues.

If you use ValueTrack parameters, we encourage you to remove the ValueTrack parameter {adposition} from your tracking templates. When average position is sunset, the ValueTrack parameter {adposition} will begin returning the empty string.

Note that average position has already been removed from the current beta version of the Google Ads API, but is accessible in the earlier V1_x versions.

In lieu of average position, we recommend you use the new metrics of Impression (Absolute Top) %" and "Impression (Top) %. These are the new metrics:

Absolute Top Metrics
AdWords API	Google Ads API
AbsoluteTopImpressionPercentage	absolute_top_impression_percentage
SearchAbsoluteTopImpressionShare	search_absolute_top_impression_share
SearchBudgetLostAbsoluteTopImpressionShare	search_budget_lost_absolute_top_impression_share
SearchRankLostAbsoluteTopImpressionShare	search_rank_lost_absolute_top_impression_share

Top Metrics
AdWords API	Google Ads API
TopImpressionPercentage	top_impression_percentage
SearchTopImpressionShare	search_top_impression_share
SearchBudgetLostTopImpressionShare	search_budget_lost_top_impression_share
SearchRankLostTopImpressionShare	search_rank_lost_top_impression_share

As always, don't hesitate to reach out to us on the developer forum with any questions.
David Wihl, Google Ads API Team

Ad Manager Content Ingest Migration

Thursday, July 25, 2019

In case you missed it, Google Ad Manager's video content ingestion is getting an upgrade, and the API has been updated to support the new Content Metadata features.

If you create video line items through the API, you'll need to update your application to target metadata for video line items using CmsMetadataCriteria instead of CustomCriteria keys and values. The values for CmsMetadataCriteria can be retrieved from the CmsMetadataService, available in v201902 and later.

Migration Steps

A significant part of this migration will be coordinating your changes - especially if you work with multiple Ad Manager networks. You'll need to wait until Google migrates each network, then change your application's behavior when creating line items.

The order of operations will be:

Google backfills and verifies existing content metadata in new Ad Manager infrastructure.
Google enables the new content ingestion features on a network.
You update your application to use CMS Metadata targeting for all new line items.

If you need help with this migration, or coordinating changes with your partners, don't hesitate to reach out to us on the Ad Manager API forums.

- Chris Seeley, Ad Manager API Team

Campaign IDs and Budget IDs as 64-bit in Google Ads

Monday, July 22, 2019

Update (Aug 5, 2019): Please also include SharedSet ID in your verification for 64-bit compliance.
Update (Jul 26, 2019): Please also include Asset ID in your verification for 64-bit compliance.

In the AdWords API and Google Ads API, Campaign IDs and Budget IDs are 64-bit signed integers and are of type xsd:long in the AdWords API and INT64 in the Google Ads API. Applications that integrate with the API should handle ID values in that range.

Historically, Campaign and Budget IDs in Google Ads were within the maximum value of 32-bit signed integer, but will soon be exceeding this range. In order to avoid any issues, please make sure your applications are fully compliant with IDs within a range of 64-bit signed integer values.

If you have any questions or concerns, please don't hesitate to contact us via the forum.
--Stan Grinberg, Google Ads API Team

Ads Developer Blog

Announcing v201908 of the Google Ad Manager API

Announcing v2_1 of the Google Ads API beta

Google Ads scripts now supports price extensions

DCM/DFA Reporting and Trafficking API v3.2 sunset reminder

Sunset of the Average Position Metric in AdWords and Google Ads APIs

Ad Manager Content Ingest Migration

Campaign IDs and Budget IDs as 64-bit in Google Ads

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