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

As announced in August, deprecated services in the DoubleClick Bid Manager (DBM) API, comprised of DBM API v1, the DBM API v1.1 SDF Download service, and the DBM API v1.1 Line Item service, will be sunset on February 26, 2021.

If you are still using the DBM API v1 Reporting service, you must migrate to the DBM API v1.1 Reporting service before the sunset date to avoid an interruption of service. Consult the API release notes for 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. You have to update your implementation to traverse multiple pages if you want 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 and start using the Display & Video 360 API 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

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

Starting January 2021, over 1500 deprecated Geo Region targeting options will no longer be supported in Display & Video 360. This announcement, along with the full list of deprecated options, can be found on the Geography Targeting Help Center article. These deprecated targeting options reflect outdated geographical regions and, therefore, do not change the serving of line items.

How will this happen in the API?

This sunset will be reflected in the Display & Video 360 API through the following sequence of events:

1. Starting today, we will begin removing deprecated targeting from older resources. These resources consist of Line Items or Insertion Orders that are currently archived or have been paused for more than six months.
2. In February 2021, the deprecated targeting options will no longer be retrievable through the Targeting Options service and attempts at assigning or removing deprecated targeting through the Line Item Assigned Targeting Options service will return an error.
3. After the deprecated targeting options are no longer able to be assigned, we will begin removing deprecated targeting from all remaining resources. Any line items only using deprecated targeting will be paused upon the removal of said targeting. This concludes the formal sunset of the deprecated targeting options.

What should I do to prepare for this?

In anticipation of this sunset, it is recommended that you do the following:

1. Check to see if any existing Line Items utilize deprecated targeting options. Use advertisers.lineItems.targetingTypes.assignedTargetingOptions.list to list the assigned Geo Region targeting for each active line item and check the targeting against the deprecated targeting options. Remove or replace any deprecated targeting as soon as possible using advertisers.lineItems.bulkEditLineItemAssignedTargetingOptions.
2. If you are storing oft-used targeting option IDs locally, cross-reference them against the list of deprecated targeting options. This will avoid errors caused by attempting to assign sunset targeting options.

Should I expect more deprecations in the future?

Users should expect the occasional deprecation and sunset of targeting options in Display & Video 360 in much smaller quantities than this deprecation. As such, future deprecations likely won’t be announced through a blog post or documentation change.

In order to account for these deprecations, it is recommended that you use targetingTypes.targetingOptions.get to confirm that a targeting option is still available before assigning it. This should be done before assigning any option not obtained through the Targeting Options service, including those stored locally or copied from existing targeting. This will avoid errors caused by attempting to assign deprecated targeting.

You can read more about the Targeting Options and Assigned Targeting Options services in our reference documentation and on the Set Targeting page of our Managing Line Items guide.
If you have questions or run into issues navigating this process, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team

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

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

• Support for auditing sites that use Google Publisher Tag limited ads
• Improved ad density measurement to better align with industry best practices
• Updates to support Lighthouse v6.4.1

A number of smaller enhancements and bug fixes are also included. For complete details, see the changelog on GitHub. Additional Lighthouse changes included in this release can be found in the v6.3.0 and v6.4.0 release notes.

Try it out and let us know what you think

Publisher Ads Audits v1.3.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 89 release (est. March 2021).

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 are announcing the launch of two new features in the AdMob API:

• New admob.readonly OAuth 2.0 scope
• Inventory methods including list apps and ad units

New OAuth 2.0 scope

Read More

Today we are announcing the launch of two new features in the AdMob API:

• New admob.readonly OAuth 2.0 scope
• Inventory methods including list apps and ad units

New OAuth 2.0 scope

While the admob.report scope is only intended for reports, the new admob.readonly scope is intended for all read methods, including reports and inventory. We recommend using the admob.readonly scope as it can be used for all read only methods.

Scope	Functionality
https://www.googleapis.com/auth/admob.readonly	See all of your AdMob data. This may include your account information, inventory and mediation settings, reports, and other data. If you agree, this app will be allowed to see, but not make changes to your AdMob data. This doesn't include sensitive data, such as payments or campaign details.
https://www.googleapis.com/auth/admob.report	See ad performance and earnings reports. See publisher ID, timezone and default currency code.

New methods

We have added the following new methods to the v1beta AdMob API, which allow you to view your AdMob apps and ad units.

• listApps
• listAdUnits

How can I start using the new methods and scope?

The beta is available to all AdMob users. You can start with the client libraries that we have created for you.

Where can I learn more?

• Get started with the AdMob API - Follow this guide to learn how to generate credentials and make your first request using the AdMob API.
• Reference documentation - Read the page for detailed information on each REST method and its specific parameters.
• Client Library Samples - Check out this page for code samples on how to make requests in Java and Python.

Feel free to reach out to us via the AdMob API forum if you have questions or feedback regarding the AdMob API.

 - Amira Badreldin, AdMob API team

The Google Ads API Developer Relations team will be hosting a live webinar, Intro to Reporting & the Google Ads Query Language, on December 4 at 10 AM EST (3 PM GMT).Read More

The Google Ads API Developer Relations team will be hosting a live webinar, Intro to Reporting & the Google Ads Query Language, on December 4 at 10 AM EST (3 PM GMT).

Mark your calendar

Agenda
The webinar will cover the topics below and include code walkthroughs to demonstrate how to perform different actions with the Google Ads API client libraries. We will also host a live Q&A at the end.

• Reporting in the Google Ads API vs. the AdWords API
• Types of search requests you can perform with the Google Ads API
• The syntax and structure of Google Ads Query Language queries
• How to discover available fields to construct Google Ads Query Language queries

Prerequisites
In order to get the most out of this webinar, we suggest you develop a basic understanding of the Google Ads API. To learn more, please visit our API Overview documentation or check out this Google Ads API Overview workshop from 2019. In addition, you may find this guide useful to learn about reporting with the Google Ads API, though much of this information will be covered in the webinar.

Reminders
Feel free to add the event to your calendar. In addition, you can set a reminder for the event on YouTube by clicking the “Set reminder” button on the YouTube event page.

We look forward to sharing our knowledge of the Google Ads API with you and answering your questions. If you have any questions or need additional help, contact us via the forum or at googleadsapi-support@google.com.
- Devin Chasanoff, on behalf of the Google Ads API Team

What’s changing?

The Content API for Shopping will gradually roll out improvements to request validation from January 1, 2021 to February 15, 2021. These changes will be applied to a growing percentage of requests during that time, reaching 100% by February 15, 2021. The validation improvements will ensure that certain requests that are not in the proper format result in an error instead of having the Content API attempt to infer the request's intent. As long as you are submitting the proper type and structure for each field, you will not be affected by this change.

Read More

What’s changing?

The Content API for Shopping will gradually roll out improvements to request validation from January 1, 2021 to February 15, 2021. These changes will be applied to a growing percentage of requests during that time, reaching 100% by February 15, 2021. The validation improvements will ensure that certain requests that are not in the proper format result in an error instead of having the Content API attempt to infer the request's intent. As long as you are submitting the proper type and structure for each field, you will not be affected by this change.

The following sections describe two examples of incorrectly formatted requests that may fail after January 1st, 2021. If your requests start to fail after January 1st, 2021, please refer to the error message returned and correct the formatting issue.

Example: Providing an invalid structure for a repeated field

This error applies to providing any invalid type for a repeated field, such as providing a list of objects instead of a list of strings, or vice versa.

Example invalid v2.1 request

The following request is invalid because the includedDestinations field requires a list of strings, not a list of objects:

{
  "targetCountry": "US",
  "offerId": "123",
  "contentLanguage": "en",
  "channel": "online",
  "includedDestinations": [{"destinationName": "Shopping", "intention": "default"}]
}

Example valid v2.1 request

To correct this issue, change the list of objects to a list of strings:

{
  "targetCountry": "US",
  "offerId": "123",
  "contentLanguage": "en",
  "channel": "online",
  "includedDestinations": ["Shopping", "SurfacesAcrossGoogle"]
}

Other common fields affected by this change

• v2.1:
  • product.excluded_destinations (a common mistake is providing the v2 format of this field for requests to v2.1)
• v2:
  • product.destinations (a common mistake is providing the v2.1 format of this field for requests to v2)
  • product.sizes
  • product.additional_image_links
  • product.shipping

Example: Submitting a string that represents a float instead of an integer

This error applies to providing a string containing a floating point number when an integer is required.

Example invalid v2.1 request

The following request is invalid because the sellOnGoogleQuantity requires a string in int64 format, but the string “100.0” is a float:

{
  "targetCountry": "US",
  "offerId": "123",
  "contentLanguage": "en",
  "channel": "online",
  "sellOnGoogleQuantity": "100.0"
}

Example valid v2.1 request

To correct this issue, change the value to an integer:

{
  "targetCountry": "US",
  "offerId": "123",
  "contentLanguage": "en",
  "channel": "online",
  "sellOnGoogleQuantity": "100"
}

Other common fields affected by this change

• v2.1:
  • product.unit_pricing_base_measure.value
• v2:
  • inventory.sell_on_google_quantity
  • product.unit_pricing_base_measure.value

What do I do?

We recommend that you address any incorrectly formatted requests before January 1st, 2021 to avoid any disruptions to your application.

If you are already submitting the proper type for each field as described in the Content API for Shopping reference docs, no action is required.

Need More Help?

If you have any questions or need assistance, please reach out to us on the forum.

 Benji Rothman, Content API for Shopping Team

We are writing to remind you that the Content API for Shopping v2 will sunset on March 29, 2021. On this date, all requests made against v2 of the Content API will fail. Please migrate to v2.1 as soon as possible to ensure your applications are unaffected.

Read More

We are writing to remind you that the Content API for Shopping v2 will sunset on March 29, 2021. On this date, all requests made against v2 of the Content API will fail. Please migrate to v2.1 as soon as possible to ensure your applications are unaffected.

To help with the migration to v2.1, we have prepared the following resources:

• Migration guide -- Explains how to update your applications for v2.1.
• Supplemental feeds guide — In v2.1, supplemental feeds replace the v2 inventory service for partial updates to online products.
• Local inventory service guide — In v2.1, the local inventory service replaces the v2 inventory service for updates to local inventory.
• Release notes -- Lists all changes and new features added in v2.1, organized by release date.

If you have questions about the migration or encounter challenges that prevent you from migrating, we want to hear from you. Please reach out to us on the forum so we can help.

 Benji Rothman, Content API for Shopping Team

- Chris Seeley, Ad Manager API Team Read More

We're happy to announce that v202011 of the Google Ad Manager API is available starting today. Upgrade to this version to take advantage of new functionality, like support for Ad Speed reports. Now you can programmatically monitor ad speed, because fast ads matter to both you and your users.

This release also brings a new ForecastService method to let you explore historical and future impression opportunities. This is backed by the same data as your network's Traffic Forecast.

For the full list of changes for v202011 check the release notes. Feel free to reach out to us on the Ad Manager API forum with any API-related questions.

- Chris Seeley, Ad Manager API Team

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

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

• A manual trigger service that allows users to create, activate, and deactivate manual triggers through the API. Manual triggers, when assigned to a line item, allow you to quickly switch on and ramp up spending for that line item. Manual triggers can also now be assigned to line items using a new line item flight field and enum value.
• New targeting expansion options that can enable the widening of existing audience targeting to include similar users.
• The addition of customSegmentId fields for DoubleVerify and Integral Ad Science objects used in the assigning of third-party verification targeting.

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

Before using these new features, make sure to update your client library to the latest version. We have also updated our Managing Line Items guide to discuss serving ads using manual triggers.

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

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

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

Here are the highlights:

• The API now has Change History similar to the Google Ads UI with ChangeEvent including what interface and who made the changes.
• You can now manage user access in your Google Ads account.
• Maximize conversion value and maximize conversions are now available as portfolio bidding strategies, which includes Search.
• The new Customer.optimization_score_weight helps you calculate your overall optimization score for your manager account.
• New audience types are available including CombinedAudience and CustomAudience.

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

 - Donovan McMurray, Ad Manager API Team Read More

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

If you’re still using v201911, now is the time to upgrade to a newer release and take advantage of additional functionality. For example, in v202002 we added a number of video and reporting features.

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