In a future release, the Reporting Visibility Enum will be Renamed to ReportVisibility and moved from a nested type (Report.Visibility) to a top-level type. This change is wire compatible, but client library users will need to update import paths when upgrading client library versions.

Announcement

In the PrivateAuctionDeal service, the auctionPriorityEnabled field is deprecated and replaced by the new dealPriority field.

Both fields will be available until July 13, 2026. On or after July 13, 2026, the auctionPriorityEnabled field will be removed.

During the migration period, dealPriority will take precedence when set.

Added RichMediaAdsCompanies service.

Feature

Added LINE_ITEM_AVERAGE_NUMBER_OF_VIEWERS Report Dimension.

Feature

Added readonly OAuth scope. For more information, see the Ads Developer Blog.

Feature

Added CREATIVE_SSL_ Report Dimensions.

Feature

Added McmEarnings service.

Breaking

Removed DEMAND_SUBCHANNEL_ALL Report Dimension.

Feature

Added write operations to ApplicationService.

Breaking

Removed AdManagerError from error responses. Field level error information is now in google.Rpc.BadRequest.

Feature

Added TARGETS_CUSTOMER_MATCHING_LIST Report Dimension.

Breaking

Removed UNIFIED_PRICING_RULE_ dimensions. They have been replaced by PRICING_RULE_ dimensions.

Feature

Added AD_SERVER_ACTIVE_VIEW_REVENUE Report Metric.

The Report Dimensions UNIFIED_PRICING_RULE_ID and UNIFIED_PRICING_RULE_NAME have been deprecated. The replacement dimensions PRICING_RULE_ID and PRICING_RULE_NAME have been added as an alias to the deprecated dimensions.

On or after January 30, 2026 the server will return the new PRICING_RULE_ID and PRICING_RULE_NAME dimensions. The deprecated dimensions will be removed and requests to create or update reports using the deprecated dimensions will fail.

This change only impacts clients reading and writing report resources that use UNIFIED_PRICING_RULE_ID and UNIFIED_PRICING_RULE_NAME. There is no change to ReportService.runReport and ReportService.fetchReportResultRows.

Clients must migrate to using PRICING_RULE_ID and PRICING_RULE_NAME by January 30, 2026.

Upcoming changes to draft reports

On or after January 5, 2026:
Requests using SAVED visibility value will normalize to the alias value VISIBLE.

Reports with a DRAFT visibility will be automatically migrated: * The Report.visibility field will be set to VISIBLE * The current Report.reportDefinition value will be copied to a new draftReportDefinition field * The Report.reportDefinition field will be unset

Reports must have a reportDefinition to run:

Clients running or writing reports with Visibility.DRAFT must update the report to Visibility.VISIBLE using the API or by naming the report in the UI before January 5, 2026.

On or after January 30, 2026:
The DRAFT and SAVED values will be removed. Requests using DRAFT and SAVED values will fail.

Clients must migrate to using Visibility.VISIBLE by January 30, 2026.

Announcement

On or after January 30, 2026, errors will no longer include AdManagerError objects in the error.details field. The same error information is provided in the google.rpc.BadRequest object.

Before January 5, 2026:

{
  "error": {
    "code": 400,
    "message": "Field foo is not supported for filtering.",
    "status": "INVALID_ARGUMENT",
    "details": [
      {
        "@type": "type.googleapis.com/google.ads.admanager.v1.AdManagerError",
        "errorCode": "PARSE_ERROR_UNPARSABLE",
        "message": "Field foo is not supported for filtering."
      },
      {
        "@type": "type.googleapis.com/google.rpc.BadRequest",
        "fieldViolations": [
          {
            "description": "Field foo is not supported for filtering.",
            "reason": "PARSE_ERROR_UNPARSABLE",
            "localizedMessage": {
              "message": "Field foo is not supported for filtering."
            }
          }
        ]
      },
      {
        "@type": "type.googleapis.com/google.rpc.RequestInfo",
        "requestId": "8897430220173363092"
      }
    ]
  }
}

On or after January 5, 2026:

{
  "error": {
    "code": 400,
    "message": "Field foo is not supported for filtering.",
    "status": "INVALID_ARGUMENT",
    "details": [
      {
        "@type": "type.googleapis.com/google.rpc.BadRequest",
        "fieldViolations": [
          {
            "description": "Field foo is not supported for filtering.",
            "reason": "PARSE_ERROR_UNPARSABLE",
            "localizedMessage": {
              "message": "Field foo is not supported for filtering."
            }
          }
        ]
      },
      {
        "@type": "type.googleapis.com/google.rpc.RequestInfo",
        "requestId": "8897430220173363092"
      }
    ]
  }
}

Clients that rely on AdManagerError must migrate to use BadRequest before January 5, 2026.

Breaking

Renamed Report metric USER_MESSAGES_CCPA_MESSAGES_SHOWN to USER_MESSAGES_US_STATES_MESSAGES_SHOWN.

Feature

Added LineItem resource.

Feature

Added support for creating and updating customTargetingKeys.

Feature

Added support for creating and updating adUnits.

Feature

Added support for creating and updating customFields.

Feature

Added support for creating and updating placements.

Feature

Added support for reading, allowing, and blocking adReviewCenterAds.

Feature

Added additional report dimensions, metrics, types, and date ranges.

Feature

Added AudienceSegment resource.

Feature

Added BandwidthGroup resource.

Feature

Added Contact resource.

Feature

Added ContentLabel resource.

Feature

Added CreativeTemplate resource.

Feature

Added Team resource.

In an upcoming release, the following Report dimensions and metrics will be renamed:

The current values will be marked as deprecated but will be supported as an alias to the new value until October 1st, 2025. The server will normalize usage to the new values. For example, if a client uses PROGRAMMATIC_BUYER_ID when creating a Report, the response from the server will contain DEAL_BUYER_ID.

On or after October 1st, 2025 the deprecated values will be removed and requests using these values will fail. Clients must migrate to the new values before October 1st, 2025.

In an upcoming release, Report messages will be restructured. These changes are wire compatible, but this change will alter the import paths in client libraries.

Feature

Added BrowserLanguage resource.

Feature

Added MobileDevice resource.

Feature

Added Browser resource.

Feature

Added DeviceCapability resource.

Feature

Added additional Report dimensions and metrics.

Feature

Added ContentBundle resource.

Feature

Added methods for reading and writing Contact resources.

Feature

Added MobileDeviceSubmodel resource.

Feature

Added Content resource.

Feature

Added Application resource.

Feature

Added MobileCarrier resource.

Feature

Added DeviceManufacturer resource.

Feature

Added CmsMetadataKey resource.

Feature

Added CmsMetadataValue resource.

The canonical resource name for CustomTargetingValue has been changed from
networks/{networkCode}/customTargetingKeys/{customTargetingKeyId}/customTargetingValues/{customTargetingValueId}
to
networks/{networkCode}/customTargetingValues/{customTargetingValueId}.

To retrieve custom targeting values for a specific key, use the method networks.customTargetingValues.list with a filter on customTargetingKey.

Clients using the old format should migrate before July 28th, 2025. Requests using the old format will fail on or after July 28th, 2025.

Change

AdBreak, AdUnit, CustomField , Placement , and Role resources now include fields with default values in responses. Previously, fields with default values like 0 or an empty string were omitted from the response.

Old behavior

{
   "name": "/networks/123/exampleResource/1"
}

New behavior

{
   "name": "/networks/123/exampleResource/1",
   "stringField": "",
   "intField": 0
}

Feature

Added OperatingSystem and OperatingSystemVersion resources.

Feature

Added GeoTarget resource.

Feature

Added support for Targeting on Private Auction deals.

Feature

Added BandwidthGroup resource.

Feature

Added DeviceCategory resource.

Feature

Added ProgrammaticBuyer resource.

On or after June 23, 2025 the canonical resource name for CustomTargetingValue will change formats from networks/{networkCode}/customTargetingKeys/{customTargetingKeyId}/customTargetingValues/{customTargetingValueId} to networks/{networkCode}/customTargetingValues/{customTargetingValueId}.

Added support for Ad Breaks.

Feature

Added support for Private Auctions.

Breaking

Refactored type paths for Companies and Reports. This change is wire compatible, but import paths will change for Python client library versions >0.2.4. Other client libraries are not affected.

Fixed

Corrected resource name patterns and grammar in documentation.

Open Beta: The Ad Manager API is now available to all users.

Breaking

Temporarily removed Closed Beta services that had data discrepancies with the SOAP API:

• LineItem
• Creative
• Contact
• Label
• Team

These will be added back when the discrepancies are resolved.

Feature

Added support for Interactive Reporting

Feature

Request ID is set in the HTTP header X-Goog-Correlation-Id for all responses and in the error body for API errors. This ID can be shared with support to assist with troubleshooting.

All DateTime fields have been changed to use RFC3339 timestamp strings.

Breaking

Removed support for ReportService methods. These will be replaced by methods for running Interactive reports.

Feature

Added adUnitSizes resource to list the ad unit sizes available in a network.

Feature

Added support for publisher provided signals resources including entitySignalsMappings and taxonomyCategories.