自
2025 年 9 月 8 日起,每個新委刊項都必須聲明是否會放送歐盟政治廣告。如果透過 Display & Video 360 API 和 SDF 上傳的檔案未提供聲明,系統就會失敗。如要進一步瞭解如何更新整合服務以進行這項聲明,請參閱
淘汰項目頁面。
從第 2 版遷移至第 3 版
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
上次更新時間:2023 年 10 月 31 日
遷移應用程式
從第 2 版遷移至第 3 版時,您必須更新端點網址以呼叫 v3,並更新應用程式以因應重大變更。
將 API 呼叫從 v2 更新為 v3
如要使用 v3 而非 v2,您必須更新要求,以便使用新的 v3 端點。
舉例來說,如要使用 v2 呼叫 advertisers.get
方法,請使用下列網址:
GET https://displayvideo.googleapis.com/v2/advertisers/advertiserId
針對 v3,請將網址更新為以下內容:
GET https://displayvideo.googleapis.com/v3/advertisers/advertiserId
如果您使用用戶端程式庫向 API 提出要求,請使用最新版本的用戶端程式庫,並更新設定以使用 v3。
進行必要變更
我們會在第 3 版中推出多項重大變更。請詳閱下列操作說明,並根據您現有的 Display & Video 360 API 使用情形,進行必要的變更。
建立廣告主時,請加入必要的帳單設定
billingConfig
現已是 Advertiser
資源中的必填欄位。更新 advertisers.create
要求,確認是否已設定這個欄位。您可以透過新的 Partner
資源 billingConfig
欄位,為上層合作夥伴擷取預設帳單資訊。
使用新欄位控管最佳化指定目標對象
新的布林 enableOptimizedTargeting
欄位已取代 TargetingExpansionConfig
物件中的 targetingExpansionLevel
欄位。
更新廣告訂單整合功能,使用新的 KPI 欄位
新的 kpi
欄位已取代 InsertionOrder
資源中的 performanceGoal
欄位。這個新欄位會使用 Kpi
物件取代 PerformanceGoal
物件,並使用新的欄位和列舉。
移除已淘汰服務和欄位的參照
為配合過去功能的淘汰,我們已在 v3 中移除各種實體:
其他異動
除了上述破壞性變更,v3 也推出了新功能。
在初次推出後新增至 v3 的功能,請參閱發布說明。
鄰近區域清單管理
在 v3 中,您可以全面管理鄰近位置清單,並使用 advertisers.locationLists.assignedLocations
服務建立及刪除指派給 TARGETING_LOCATION_TYPE_PROXIMITY
LocationList
資源的位置。系統會使用 TARGETING_TYPE_POI
TargetingOption
資源的 ID 識別位置。您可以使用 targetingTypes.targetingOptions.search
擷取這些資料。
能夠建立以規則為依據的自訂出價演算法
在 v3 中,您可以使用 customBiddingAlgorithms
、media
和 customBiddingAlgorithms.rules
服務,建立及擷取以規則為依據的自訂出價演算法。
這項功能目前為 Beta 版,僅供獲准的合作夥伴使用。如果合作夥伴未列入許可清單,您的要求會傳回錯誤。
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-07-25 (世界標準時間)。
[null,null,["上次更新時間:2025-07-25 (世界標準時間)。"],[[["\u003cp\u003eMigrating to v3 involves updating endpoint URLs and addressing breaking changes, such as replacing YouTube resource references and incorporating required billing configurations when creating advertisers.\u003c/p\u003e\n"],["\u003cp\u003eYouTube resources and their related targeting have been updated, requiring changes to resource and service calls, bidding strategy retrieval, and third-party measurement configuration.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003ebillingConfig\u003c/code\u003e field is now mandatory when creating advertisers, and optimized targeting is controlled using the new \u003ccode\u003eenableOptimizedTargeting\u003c/code\u003e field.\u003c/p\u003e\n"],["\u003cp\u003eInsertion order integration needs to utilize the new \u003ccode\u003ekpi\u003c/code\u003e field, and deprecated services and fields like \u003ccode\u003eadvertisers.manualTriggers\u003c/code\u003e and \u003ccode\u003ebillableOutcome\u003c/code\u003e should be removed.\u003c/p\u003e\n"],["\u003cp\u003eVersion 3 introduces new features like proximity location list management and the ability to build rule-based custom bidding algorithms (in beta for allowlisted partners).\u003c/p\u003e\n"]]],["To migrate to v3, update API request URLs from `/v2/` to `/v3/`, use the latest client library version, and adapt to breaking changes. Replace `YoutubeAdGroup` and `YoutubeAdGroupAd` with `AdGroup` and `AdGroupAd`. Update how YouTube bidding strategies and third-party measurements are handled. `billingConfig` is now required for new advertisers, and `enableOptimizedTargeting` replaces `targetingExpansionLevel`. `kpi` replaces `performanceGoal`. Deprecated services like `manualTriggers` and the `billableOutcome` field are removed. New features include proximity location list management and rule-based custom bidding algorithms.\n"],null,["# Migrate from v2 to v3\n\n| Display \\& Video 360 API is deprecated and will sunset on **October 7, 2025** . Migrate to [Display \\& Video 360 API v4](/display-video/api/reference/rest/v4) before sunset to avoid an interruption in service.\n\n*Last update: 2023-10-31*\n\nMigrate your application\n------------------------\n\nMigrating from v2 to v3 requires updating your endpoint URLs to call v3 and\nupdating your application to account for breaking changes.\n\n### Update your API calls from v2 to v3\n\nTo use v3 instead of v2, you need to update your requests to use new v3\nendpoints.\n\nFor example, to call the [`advertisers.get`](/display-video/api/reference/rest/v3/advertisers/get) method with v2, you would\nuse the following URL: \n\n GET https://displayvideo.googleapis.com/v2/advertisers/\u003cvar translate=\"no\"\u003eadvertiserId\u003c/var\u003e\n\nFor v3, update the URL to the following: \n\n GET https://displayvideo.googleapis.com/v3/advertisers/\u003cvar translate=\"no\"\u003eadvertiserId\u003c/var\u003e\n\nIf you are using a client library to make requests to the API, use the most\nrecent version of the client library and update your configuration to use v3.\n\n### Make required changes\n\nWe're introducing a number of breaking changes in v3. Review the following\ninstructions and make the required changes relevant to your existing use of the\nDisplay \\& Video 360 API.\n\n#### Update calls retrieving YouTube resources and their related targeting\n\n- `YoutubeAdGroup` and `YoutubeAdGroupAd` resources have been replaced by [`AdGroup`](/display-video/api/reference/rest/v3/advertisers.adGroups#AdGroup) and [`AdGroupAd`](/display-video/api/reference/rest/v3/advertisers.adGroupAds#AdGroupAd) resources. These new resources provide nearly identical information as the v2 resources but may use updated field names or enum types. In your integration, replace your uses of `YoutubeAdGroup` or `YoutubeAdGroupAd` resources with [`AdGroup`](/display-video/api/reference/rest/v3/advertisers.adGroups#AdGroup) and [`AdGroupAd`](/display-video/api/reference/rest/v3/advertisers.adGroupAds#AdGroupAd) resources and update calls to the following v2 services to the corresponding v3 service:\n - `advertisers.youtubeAdGroupAds` to [`advertisers.adGroupAds`](/display-video/api/reference/rest/v3/advertisers.adGroupAds#methods)\n - `advertisers.youtubeAdGroups` to [`advertisers.adGroups`](/display-video/api/reference/rest/v3/advertisers.adGroups#methods)\n - `advertisers.youtubeAdGroups.targetingTypes.assignedTargetingOptions` to [`advertisers.adGroups.targetingTypes.assignedTargetingOptions`](/display-video/api/reference/rest/v3/advertisers.adGroups.targetingTypes.assignedTargetingOptions#methods)\n- References to [`YoutubeAndPartnersBiddingStrategy`](/display-video/api/reference/rest/v3/BiddingStrategy#YoutubeAndPartnersBiddingStrategy) objects have been moved to a new [`youtubeAndPartnersBid`](/display-video/api/reference/rest/v3/BiddingStrategy#FIELDS.youtube_and_partners_bid) field within the general [`BiddingStrategy`](/display-video/api/reference/rest/v3/BiddingStrategy) object. The `biddingStrategy` field has been removed from the [`YoutubeAndPartnersSettings`](/display-video/api/reference/rest/v3/advertisers.lineItems#YoutubeAndPartnersSettings)object. Update your integration to retrieve the bidding strategy for YouTube line items or ad groups from the [`BiddingStrategy`](/display-video/api/reference/rest/v3/BiddingStrategy) object in the `bidStrategy` field in the [`LineItem`](/display-video/api/reference/rest/v3/advertisers.lineItems#LineItem.FIELDS.bid_strategy) or [`AdGroup`](/display-video/api/reference/rest/v3/advertisers.adGroups#AdGroup.FIELDS.bid_strategy) resource.\n- The `thirdPartyMeasurementSettings` field has been renamed to [`thirdPartyMeasurementConfigs`](/display-video/api/reference/rest/v3/advertisers.lineItems#YoutubeAndPartnersSettings.FIELDS.third_party_measurement_configs) in the [`YoutubeAndPartnersSettings`](/display-video/api/reference/rest/v3/advertisers.lineItems#YoutubeAndPartnersSettings) object and the `YoutubeAndPartnersThirdPartyMeasurementSettings` object has been renamed to [`ThirdPartyMeasurementConfigs`](/display-video/api/reference/rest/v3/advertisers.lineItems#ThirdPartyMeasurementConfigs). Update your integration to retrieve third-party measurement configuration information using the new field and object.\n\n#### Include required billing configurations when creating advertisers\n\n[`billingConfig`](/display-video/api/reference/rest/v3/advertisers#Advertiser.FIELDS.billing_config) is now a required field in the\n[`Advertiser`](/display-video/api/reference/rest/v3/advertisers#Advertiser) resource. Update your [`advertisers.create`](/display-video/api/reference/rest/v3/advertisers/create)\nrequests to verify that this field is set. The default billing information can\nbe retrieved for the parent partner through the new [`Partner`](/display-video/api/reference/rest/v3/partners#Partner)\nresource [`billingConfig`](/display-video/api/reference/rest/v3/partners#Partner.FIELDS.billing_config) field.\n\n#### Use new field to control optimized targeting\n\nA new boolean [`enableOptimizedTargeting`](/display-video/api/reference/rest/v3/TargetingExpansionConfig#FIELDS.enable_optimized_targeting) field has replaced the\n`targetingExpansionLevel` field in the [`TargetingExpansionConfig`](/display-video/api/reference/rest/v3/TargetingExpansionConfig)\nobject.\n\n#### Update insertion order integration to use new KPI field\n\nA new [`kpi`](/display-video/api/reference/rest/v3/advertisers.insertionOrders#InsertionOrder.FIELDS.kpi) field has replaced the `performanceGoal` field in\nthe [`InsertionOrder`](/display-video/api/reference/rest/v3/advertisers.insertionOrders#InsertionOrder) resource. This new field uses a [`Kpi`](/display-video/api/reference/rest/v3/advertisers.insertionOrders#Kpi)\nobject in place of the `PerformanceGoal` object and uses new fields and enums.\n\n#### Remove references to deprecated services and fields\n\nVarious entities have been removed in v3 to align with [past feature\ndeprecations](/display-video/api/deprecations#features):\n\n- The `advertisers.manualTriggers` service has been removed as [manual triggers\n have been deprecated](/display-video/api/deprecations#features.manual_triggers).\n- The `billableOutcome` field has been removed from the [`InsertionOrder`](/display-video/api/reference/rest/v3/advertisers.insertionOrders#InsertionOrder) resource as [outcome based buying has been\n deprecated](/display-video/api/deprecations#features.obb).\n\nAdditional changes\n------------------\n\nIn addition to the breaking changes listed above, v3 also introduces new\nfeatures.\n\n*Features added to v3 after the initial launch can be found in our [release\nnotes](/display-video/api/release-notes).*\n\n### Proximity location list management\n\nIn v3 you can fully manage [proximity location lists](//support.google.com/displayvideo/answer/2705812#lists), allowing you to\nuse the [`advertisers.locationLists.assignedLocations`](/display-video/api/reference/rest/v3/advertisers.locationLists.assignedLocations#methods) service to\ncreate and delete locations assigned to `TARGETING_LOCATION_TYPE_PROXIMITY`\n[`LocationList`](/display-video/api/reference/rest/v3/advertisers.locationLists#LocationList) resources. Locations are identified using the ID of\n`TARGETING_TYPE_POI` [`TargetingOption`](/display-video/api/reference/rest/v3/targetingTypes.targetingOptions#TargetingOption) resources. These can be\nretrieved using [`targetingTypes.targetingOptions.search`](/display-video/api/reference/rest/v3/targetingTypes.targetingOptions/search).\n\n### Ability to build rule-based custom bidding algorithms\n\nIn v3, you can build and retrieve rule-based custom bidding algorithms using the\n[`customBiddingAlgorithms`](/display-video/api/reference/rest/v3/customBiddingAlgorithms#methods), [`media`](/display-video/api/reference/rest/v3/media#methods),\n[`customBiddingAlgorithms.rules`](/display-video/api/reference/rest/v3/customBiddingAlgorithms.rules#methods) services.\n\nThis feature is in beta and only available to allowlisted partners. If your\npartner is not allowlisted, your request will return an error."]]