Tag Archives: dbm_api

Instant reports will soon be available using Bid Manager API

In the upcoming months, Display & Video 360 instant reports will be made available using the Bid Manager API. We previously announced the migration of certain report types from Offline Reporting to Instant Reporting.

Once a partner is migrated, they will see the following changes:

  • Instant reports will be included in queries.list responses.
  • Existing Standard, Reach, YouTube, and URA reports will only be available under the Instant Reporting tab in the Display & Video 360 interface under the same query and report IDs.
  • If you use the Display & Video 360 interface to build new reports, you will need to build Standard, Reach, YouTube, and URA reports under the Instant Reporting tab.

This migration will happen by partner throughout the following months, with all reports under a partner migrated at once.

If you have questions about this migration in general, you can contact Display & Video 360 product support using this contact form. If you have questions about how this migration will impact the API, please contact us using our new Bid Manager API Technical support contact form.

Deprecation of Full Path and Path Attribution reports in Bid Manager API

Starting May 1, 2024, requests to retrieve, create, or run Full Path and Path Attribution reports through the Bid Manager API will return an error. We deprecated both report types in February 2024. We announced this deprecation last November.

After deprecation, running a query using the ReportType FULL_PATH or PATH_ATTRIBUTION generates an empty report. Existing Query and Report resources of these types are still retrievable, and report files generated previously will still be available.

Starting on May 1, 2024, ReportType values FULL_PATH or PATH_ATTRIBUTION and the pathQueryOptions field will sunset. As a result:

We’ve added these details to our change log. To avoid an interruption of service, we recommend that you stop creating, retrieving, or running any reports using these values before the applicable sunset date.

If you have questions regarding these changes, please contact us using our support contact form.

Deprecation of cross-device conversion metric values in the Bid Manager API

Today we’re deprecating cross-device conversion metric values in Bid Manager API. The following values will sunset on February 28, 2024:

  • METRIC_CM360_POST_CLICK_REVENUE_CROSS_ENVIRONMENT
  • METRIC_CM360_POST_VIEW_REVENUE_CROSS_ENVIRONMENT
  • METRIC_POST_CLICK_CONVERSIONS_CROSS_ENVIRONMENT
  • METRIC_POST_VIEW_CONVERSIONS_CROSS_ENVIRONMENT
  • METRIC_TOTAL_CONVERSIONS_CROSS_ENVIRONMENT

Upon sunset, queries.create requests using these values will return an INVALID_ARGUMENT error, and these values will be removed from existing Query resources.

We’ve added the upcoming sunset to our change log. To avoid an interruption of service, we recommend that you stop creating any reports using these values before the applicable sunset date.

If you have questions regarding these changes, please contact us using our support contact form.

Introducing a new way to discover Display & Video 360 bulk tools

Today we’re announcing a new guide to help Display & Video 360 users discover available bulk tools that they can use to optimize their integrations.

The guide offers a high-level overview of each of the following tools that allow you to integrate with Display & Video 360 at scale:

The guide also provides a recommendations page that can help you choose the right bulk tool based on your needs and circumstances and a page proposing potential platform-wide integrations using multiple bulk tools.

You can navigate to this new guide from the existing Display & Video 360 API, Bid Manager API, or Reporting Data Transfer documentation using the Discover Bulk Tools tab at the top of the page.

Deprecating Audience Composition Reports in Bid Manager API on June 8, 2023

On June 8, 2023, Audience Composition Reports will be deprecated in Display & Video 360. This means that you will no longer be able to retrieve, create or run Audience Composition Reports using the Bid Manager API.

In the Bid Manager API, an Audience Composition Report is a Query resource with a ReportType of AUDIENCE_COMPOSITION assigned to params.type. After deprecation:

  • Any request to the queries or queries.reports services identifying an Audience Composition Report will return an error.
  • All queries.create requests creating a new Audience Composition Report will return an error.
  • All queries.list responses will no longer include Audience Composition Report queries.

To avoid an interruption of service, we recommend that you stop creating or retrieving any existing reports of this type.

If you have questions regarding this change, please contact us using our support contact form.

Bid Manager API v1.1 will sunset on April 27, 2023

The Bid Manager API v1.1 will sunset on April 27, 2023. The Bid Manager API v1.1 was deprecated in August 2022 and originally scheduled to sunset on February 28, 2023.

Please migrate to v2 before the sunset date to avoid an interruption of service.

You can read our release notes for more information about v2. Follow the steps in our v2 migration guide to help you migrate from v1.1 to v2.

If you run into issues or need help with your migration, please contact us using our support contact form.

Bid Manager API v1.1 sunset reminder

As announced in August 2022, Bid Manager (DBM) API v1.1 will sunset on February 28, 2023. Please migrate to v2 before the sunset date to avoid an interruption of service.

You can read our release notes for more information about v2. Follow the steps in our v2 migration guide to help you migrate from v1.1 to v2.

If you run into issues or need help with your migration, please contact us using our support contact form.

Deprecation of Bid Manager API v1.1

Today we’re announcing the deprecation of the Bid Manager (DBM) API v1.1. This version will be fully sunset on February 28, 2023.

Please migrate to Bid Manager API v2 by the sunset date to avoid an interruption of service. v2 introduced a number of new features and breaking changes, which are listed in our release notes. Here are some of the changes introduced in v2:

Follow the steps in our v2 migration guide to help you migrate from v1.1 to v2.

If you run into issues or need help with your migration, please contact us using our support contact form.

Announcing Bid Manager API v2

We are pleased to announce that version 2 of the Bid Manager API is now available. Notable features added in this version include: This new version also includes significant changes to be aware of, such as:
  • The changing of the base Bid Manager API URL.
  • The renaming of existing services and methods.
  • The restructuring of Query and Report resources to use new named object types and enums.
  • The updating of method functionality to require queries to be run manually after creation.
  • The rewording of existing error messages to be more detailed and prescriptive.
More detailed information about this update can be found in the Bid Manager API release notes. Follow the steps on our migration guide to help you migrate from v1.1 to v2.

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

Ads API apps must complete OAuth verification

Last year, the OAuth scopes used by the following Ads APIs were classified as sensitive, requiring developers to complete the OAuth verification process for their Google Cloud projects:
  • Google Ads API & AdWords API
    • https://www.googleapis.com/auth/adwords
  • Content API for Shopping
    • https://www.googleapis.com/auth/content
  • DoubleClick Bid Manager API
    • https://www.googleapis.com/auth/doubleclickbidmanager
Any remaining OAuth clients using the above scopes that remain unverified may have their existing credentials revoked and lose access to the above APIs if they do not complete the OAuth verification process as soon as possible.

Certain apps may qualify for one of the exceptions for app verification. If your application meets any one of those exceptions, follow the steps listed for the appropriate use case. If not, you must complete OAuth verification to continue using these Ads APIs.

If you have any questions or need additional help, contact us using any of the following support options: