Today we’re excited to announce the general availability v1 release of the new AdMob API. It allows publishers to programmatically get information on their AdMob account.

The AdMob API v1 release offers the following benefits for app developers compared with the existing AdSense API used to access AdMob data:

Read More

Today we’re excited to announce the general availability v1 release of the new AdMob API. It allows publishers to programmatically get information on their AdMob account.

The AdMob API v1 release offers the following benefits for app developers compared with the existing AdSense API used to access AdMob data:

• Retrieve metrics that are consistent with how the AdMob UI defines and calculates them
• Retrieve mediation reports previously not available through the AdSense API

How can I get started?

The AdMob API is now available to all AdMob users. You can use the Getting Started guide and the client libraries to get started.

If you’re already working with the AdSense API, please refer to our migration guide to get started. Please make plans to migrate to the new AdMob API, as we will sunset access to AdMob data via the AdSense API in the fall of 2021.

If you have any questions, please contact us via the AdMob API Developer Forum. We will be able to provide suggestions on how to best migrate your workflow. We look forward to hearing your feedback.

 - Amira Badreldin, AdMob API team

 - Jonathon Imperiosi, Publisher Ads Audits Team Read More

Today, we're announcing the general release of Publisher Ads Audits for Lighthouse v1.2.0. The major highlights of this release are:

• A new cumulative ad shift metric
• Support for auditing AMP pages (thanks to @adamsilverstein)
• Updates to support Lighthouse 6.0

A number of smaller enhancements and bug fixes are also included. For complete details, see the changelog on GitHub.

Measuring the impact of ads on the user experience

The new cumulative ad shift metric is the first publisher ads audit aimed at measuring the impact of ads on Core Web Vitals metrics. In particular, this metric provides insight into how ads affect the stability of your page's layout. To learn more about how ads affect layout stability and steps you can take to address this, see our article on minimizing layout shift with GPT.

The APIs for measuring layout stability are new and still evolving, so it's not currently possible to attribute layout shifts to ads with 100% accuracy. We'll be updating this audit as these APIs mature, so scores may change over time.

Try it out and let us know what you think

Publisher Ads Audits v1.2.0 is available to use right now. You can try generating an updated report from the web app, or grab the latest CLI release from GitHub or npm to run locally. Updates to the Chrome DevTools version will land in Chrome Stable with the Chrome 87 release (mid-November).

Have questions about this or anything else Ad Speed related? Interested in contributing? Visit our GitHub repo.

 - Jonathon Imperiosi, Publisher Ads Audits Team

Today we’re releasing an incremental update to the Display & Video 360 API v1 which includes the following features:

• New filterable fields for various list methods, including targeting option subtypes carrierAndIspDetails.type and geoRegionDetails.geo_region_type for the targetingTypes.targetingOptions.list method.
• Additional fields in the advertisers.audit method response body that allow for the tracking of more entity counts against their account entity limits.

Read More

Today we’re releasing an incremental update to the Display & Video 360 API v1 which includes the following features:

• New filterable fields for various list methods, including targeting option subtypes carrierAndIspDetails.type and geoRegionDetails.geo_region_type for the targetingTypes.targetingOptions.list method.
• Additional fields in the advertisers.audit method response body that allow for the tracking of more entity counts against their account entity limits.

More detailed information about this update can be found on the Display & Video 360 API release notes page.

Before using these new features, make sure to update your client to the latest version.

If you run into issues or need help with these new features, please contact us using our support contact form.
- Trevor Mulchay, Display & Video 360 API Team

Google Ads API beta v2 will sunset on October 21, 2020. After this date, all v2 API requests will begin to fail. Please migrate to a newer version prior to October 21, 2020 to ensure your API access is unaffected.Read More

Google Ads API beta v2 will sunset on October 21, 2020. After this date, all v2 API requests will begin to fail. Please migrate to a newer version prior to October 21, 2020 to ensure your API access is unaffected.

We've prepared various resources to help you with the migration:

• Upgrading to the newest version
• Release notes

If you have questions while you’re upgrading, please reach out to us on the forum or at googleadsapi-support@google.com.
 - Thanet Knack Praneenararat, Google Ads API Team

Today we’re announcing the deprecation of the Doubleclick Bid Manager (DBM) API v1.1 Line Item service and the sunset of all deprecated DBM API services on February 26, 2021. Deprecated DBM API services include the entirety of ...Read More

Today we’re announcing the deprecation of the Doubleclick Bid Manager (DBM) API v1.1 Line Item service and the sunset of all deprecated DBM API services on February 26, 2021. Deprecated DBM API services include the entirety of DBM API v1 and DBM API v1.1 Structured Data File (SDF) Download service. This sunset was originally scheduled for June 15, 2020, but was postponed due to COVID-19.


Refer to the table below to verify if the methods you are currently using will be available in v1.1 after February 26, 2021:

Service	Methods	Available in v1.1 after February 26, 2021?
Reporting	queries.createquery queries.deletequery queries.getquery queries.listqueries queries.runquery reports.listreports	Yes
Line Item	lineitems.downloadlineitems lineitems.uploadlineitems	No. Use the new Display & Video 360 API instead.
SDF Download	sdf.download	No. Use the new Display & Video 360 API instead.

If you are still using the DBM API v1 Reporting service, you must migrate to v1.1 by the sunset date to avoid an interruption of service. Consult the API release notes for the finer details of the changes between v1 and v1.1. Differences to note during this migration include:

• Queries created and accessed through the Reporting service require more specific filters in the params.groupBy field in v1.1. You might have to add more values to the params.groupBy field in order to create the same report structure generated in v1.
• Responses from queries.listqueries and reports.listreports calls are paginated in v1.1. Users have to update their implementation to traverse multiple pages if they wish to consume more than the first 100 items returned.

If you are using any version of any other DBM API service, you must migrate to the Display & Video 360 (DV360) API.

• The DBM API SDF Download service is being replaced by the DV360 API asynchronous SDF Download service. It features new filter options and a new download format.
• The DBM API Line Item service is being replaced by the DV360 API Line Item service. This service provides create, update, and delete methods for line items using a more easily managed REST Line Item resource separate from Entity Write File format currently used in the DBM API.

Guides are available to help you set up the Display & Video 360 API and get started using it to download SDFs and manage your line items.

If you encounter issues with your migration or want to report a separate issue, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Today, we’re announcing the v5 release of the Google Ads API beta. To use the v5 features, you will need to upgrade your client libraries and client code. The updated client libraries and code examples will be published next week. For more information on breaking changes, see the ...Read More

Today, we’re announcing the v5 release of the Google Ads API beta. To use the v5 features, you will need to upgrade your client libraries and client code. The updated client libraries and code examples will be published next week. For more information on breaking changes, see the migration guide.

Here are the highlights:

• Return metrics for entities not formally supported in the API, such as Discovery campaigns, are now available. These entities will show UNKNOWN enum values returned. See the release notes for more details.
• New request parameter to opt into returning all mutable fields in the response during a mutate.
• The API is moving towards using field presence such as optional string and optional double instead of wrapper types such as StringValue and DoubleValue. Your code will be easier to use and simplifies the API with payloads that are significantly smaller. Approximately half of our resources have been updated in this release. The full list is in the migration guide, and our code examples have been updated. The rest of the resources will change to field presence in a future release.
• Subfields of AdGroupAd.policy_summary are now selectable. Non-repeated subfields of AdGroupAd.policy_summary are now filterable.
• Support for Keyword Planner:
  • Added KeywordPlanKeywordHistoricalMetrics.close_variants to return the close variant keywords that have been merged to compute the historical metrics.
  • Added KeywordPlanService.GenerateForecastTimeSeries that returns the weekly forecast trend for Keyword Plan for the next 52 weeks.

Where can I learn more?
The following resources can help you get started:

• Release Notes
• Guides
• Reference
• Upgrading to the newest version

If you have any questions or need additional help, contact us via the forum.
Nadine Wang, on behalf of the Google Ads API Team

Beginning in June 2020, we rolled out stricter validation of long and integer request fields in the Doubleclick Bid Manager (DBM) API. This rollout finished in early August and now applies to all traffic.Read More

Beginning in June 2020, we rolled out stricter validation of long and integer request fields in the Doubleclick Bid Manager (DBM) API. This rollout finished in early August and now applies to all traffic.

This new request validation no longer allows the use of decimals in string values submitted for long and integer field types. Previously, an integer field in a request body would accept, for example, “123.0” as a permissible value. Now, identical requests will return an HTTP 400 error with status INVALID_ARGUMENT.

Before the implementation of this validation, the API truncated invalid values at the decimal point and the digits after it were ignored. You can replicate this previous behavior by truncating values at the decimal place before making a request.

Verify that your code converts values with decimals to longs and integers. If you receive an INVALID_ARGUMENT error, make sure your numbers are actual longs or integers.

If you need help adjusting for this new validation or want to report a separate issue, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team

We're happy to announce that v202008 of the Google Ad Manager API is available starting today. Upgrade to this version to take advantage of new functionality, like support for Audio Ads ...Read More

We're happy to announce that v202008 of the Google Ad Manager API is available starting today. Upgrade to this version to take advantage of new functionality, like support for Audio Ads and the ability to specify multiple Viewability Provider Companies on a LineItem.

If you work with video ads, there are several new useful features available to you in v202008:

• We’ve added nielsenCtvPacingType for specifying the pacing computation method for impressions on connected devices for a Nielsen measured LineItem.
• You can now call the performCmsMetadataKeyAction to activate and deactivate CmsMetadataKeys.

For the full list of changes for v202008 and all other active API versions, check the release notes. Feel free to reach out to us on the Ad Manager API forum with any API-related questions.

 - Donovan McMurray, Ad Manager API Team

On Monday, August 31, 2020, in accordance with the deprecation schedule, v201908 of the Ad Manager API will sunset. At that time, any requests made to this version will return errors.Read More

On Monday, August 31, 2020, in accordance with the deprecation schedule, v201908 of the Ad Manager API will sunset. At that time, any requests made to this version will return errors.

If you’re still using v201908, now is the time to upgrade to a newer release and take advantage of additional functionality. For example, in v201911 we improved reporting error messages and added the ability to break down reports by CMS Metadata.

When you’re ready to upgrade, check the full release notes to identify any breaking changes, like Activity and ActivityGroup IDs changing from type int to type long in v202005. Then, grab the latest version of your client library and update your code.

As always, don't hesitate to reach out to us on the developer forum with any questions.

 - Donovan McMurray, Ad Manager API Team

Read More

Today, we are announcing beta support for a new search method in Google Ads scripts. This method is backed by the Google Ads API and supports most queries supported by that API. Please see the documentation page for the AdsApp.search method for more information.

Additionally, we are adding beta support for the Google Ads Query Language to our existing AdsApp.report method. When using the report method, Google Ads scripts will automatically determine the correct reporting engine (either AdWords API or Google Ads API) to use based on the FROM clause in your query.

The key difference between the report and search methods is in how the results are returned.

• The report method will return a Report object, as it always has. Each row will be a map of column names to values.
• The search method will return an iterator of rows, and each row will be analogous to a GoogleAdsRow in the Google Ads API.

For example, the campaign.name column would be accessed using row['campaign.name'] if you use report, and row.campaign.name if you use search. The flat format from report can be useful for exporting to a spreadsheet or CSV. The object format from search is useful for programmatically processing results. Additionally, handling repeated fields is more intuitive since they will be returned as true arrays in the object format rather than concatenated together into a single string.

To help you build queries for your search, check out our query builder tool. If you have any questions, concerns, or feedback on the new beta features, please contact us via our forum.
- Mike Cloonan, Google Ads scripts Team

- Trevor Mulchay, Display & Video 360 API Team Read More

Today we’re releasing an update to the Display & Video 360 API v1 which includes the following features:

• A user service that allows for the management of Display & Video 360 users and their assigned user roles.
• Partner and partner targeting services that enable users to retrieve partner resources and edit partner targeting.
• A custom bidding algorithm service that users can utilize to retrieve existing custom bidding algorithm resources for use in managing insertion order or line item bidding strategies.
• The additions of a new advertiser.audit method and lineItem.list orderBy and filter capabilities to give users tools to proactively avoid reaching account entity limits.
• A new audio line item type that enables API support for audio line items.

More detailed information about this update can be found on the Display & Video 360 API release notes page.

Before using these new features, make sure to update your client to the latest version. For more information on how to use some of these new features, you can read our new User Management guide and Auditing Account Limits page.

If you run into issues or need help with these new features, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team