Tag Archives: dbm_api

Introducing lower confidence reach data in the Bid Manager API

Starting today, you can populate reports in the Bid Manager API with data that had been previously omitted due to lower statistical significance by using a new filter, FILTER_UNIQUE_REACH_SAMPLE_SIZE_ID, and setting the value to “0”.

This filter setting only impacts reach metrics with the following Metric prefixes as defined in the Bid Manager API:

  • METRIC_UNIQUE_REACH_
  • METRIC_VIRTUAL_PEOPLE_DUPLICATE_
  • METRIC_VIRTUAL_PEOPLE_EXCLUSIVE_
  • METRIC_VIRTUAL_PEOPLE_OVERLAP_

queries.create requests with queries that filter by FILTER_UNIQUE_REACH_SAMPLE_SIZE_ID but don’t include impacted metrics will return a 400 error.

On February 4, 2025, Display & Video 360 will include unique reach data with lower statistical confidence by default. If you want to ensure that your reports continue to only return high-confidence data, we recommend that you update your integration to use the new filter value to filter to "1" when creating reports with any of the impacted metrics.

Read more about these changes in our release notes.

If you run into issues or have questions about these changes, please contact us using our new Bid Manager API Technical support contact form.

- Trevor Mulchay, Bid Manager API Team

Subscribe to the blog

If you want all new blog posts sent directly to your inbox, we have good news. The blog includes a customizable RSS feed that you can subscribe to with your favorite RSS service. Just paste the URL above into your RSS service and get the blog contents delivered in whatever way you prefer. If you're new to RSS, check out this community resource on GitHub describing how it works and providing a list of well-supported services.

If you want to filter to specific products that interest you, that's possible too. Here are some quick links to the RSS feeds for the products supported by this blog: - Mike Cloonan, Ads DevRel Team

Impact of upcoming reporting changes on Bid Manager API

On October 1, 2024, the Anonymous Inventory Modeling (AIM) reporting dimension will sunset and DST/ROC (Regulatory Operating Costs) and Total Media Cost metrics will become incompatible with YouTube reports in Display & Video 360. This will impact the structure of the reports that can be created and run using the Bid Manager API.

The relevant AIM dimension is defined by Filter value FILTER_ANONYMOUS_INVENTORY_MODELING. Once sunset, queries.create and queries.run requests creating and running Query resources with this dimension will return a 400 error.

The relevant cost metrics are defined by any Metric value using the prefix METRIC_TOTAL_MEDIA_COST_ or METRIC_FEE32_. Starting October 1, queries.create and queries.run requests creating and running Query resources of ReportType YOUTUBE that use these metrics will return a 400 error. In the weeks following October 1, we will update existing YouTube queries that use these values to remove the metrics. In place of total cost metrics, we recommend the use of individual media cost metrics instead, which can be added together with other supported fees to calculate the now unavailable total media cost.

To avoid any interruption of service, review your reports to remove the AIM dimension from any existing reports and all relevant cost metrics from any existing YouTube reports.

Read more about these changes on our release notes.

If you run into issues or have questions about these changes, please contact us using our new Bid Manager API Technical support contact form.

- Trevor Mulchay, Display & Video 360 API Team

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.

- Trevor Mulchay, Bid Manager API Team

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.

- Trevor Mulchay, Bid Manager API Team

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.

- Trevor Mulchay, Bid Manager API Team

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.

- Trevor Mulchay, Display & Video 360 API Team

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.

- Trevor Mulchay, Bid Manager API Team

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.

- Trevor Mulchay, Display & Video 360 API Team

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.

- Trevor Mulchay, Display & Video 360 API Team