GET https://displayvideo.googleapis.com/v2/advertisers/advertiserId
สำหรับ v3 ให้อัปเดต URL เป็นดังนี้
GET https://displayvideo.googleapis.com/v3/advertisers/advertiserId
หากคุณใช้ไลบรารีของไคลเอ็นต์เพื่อส่งคำขอไปยัง API ให้ใช้ไลบรารีของไคลเอ็นต์เวอร์ชันล่าสุดและอัปเดตการกำหนดค่าให้ใช้ v3
ทำการเปลี่ยนแปลงที่จำเป็น
เราจะเปิดตัวการเปลี่ยนแปลงที่ส่งผลกับส่วนอื่นในระบบหลายอย่างใน v3 อ่านวิธีการต่อไปนี้
และทำการเปลี่ยนแปลงที่จำเป็นซึ่งเกี่ยวข้องกับการใช้ Display & Video 360 API ที่มีอยู่
[[["เข้าใจง่าย","easyToUnderstand","thumb-up"],["แก้ปัญหาของฉันได้","solvedMyProblem","thumb-up"],["อื่นๆ","otherUp","thumb-up"]],[["ไม่มีข้อมูลที่ฉันต้องการ","missingTheInformationINeed","thumb-down"],["ซับซ้อนเกินไป/มีหลายขั้นตอนมากเกินไป","tooComplicatedTooManySteps","thumb-down"],["ล้าสมัย","outOfDate","thumb-down"],["ปัญหาเกี่ยวกับการแปล","translationIssue","thumb-down"],["ตัวอย่าง/ปัญหาเกี่ยวกับโค้ด","samplesCodeIssue","thumb-down"],["อื่นๆ","otherDown","thumb-down"]],["อัปเดตล่าสุด 2025-09-10 UTC"],[[["\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,["| Display \\& Video 360 API v3 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\nMigrating from v2 to v3 requires updating your endpoint URLs to call v3 and\nupdating your application to account for breaking changes.\n\nUpdate 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\nMake 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\nUpdate 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\nInclude 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\nUse 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\nUpdate 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\nRemove 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\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\nProximity 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\nAbility 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."]]
