2025년 9월 8일부터 모든 새 광고 항목은 유럽연합 (EU) 정치 광고를 게재할지 여부를 선언해야 합니다. 선언을 제공하지 않는 Display & Video 360 API 및 SDF 업로드는 실패합니다. 통합을 업데이트하여 이 선언을 하는 방법에 대한 자세한 내용은
지원 중단 페이지를 참고하세요.
v2에서 v3로 이전
컬렉션을 사용해 정리하기
내 환경설정을 기준으로 콘텐츠를 저장하고 분류하세요.
최종 업데이트: 2023년 10월 31일
애플리케이션 마이그레이션
v2에서 v3으로 이전하려면 v3을 호출하도록 엔드포인트 URL을 업데이트하고 중대한 변경사항을 고려하도록 애플리케이션을 업데이트해야 합니다.
API 호출을 v2에서 v3으로 업데이트
v2 대신 v3를 사용하려면 새 v3 엔드포인트를 사용하도록 요청을 업데이트해야 합니다.
예를 들어 v2로 advertisers.get 메서드를 호출하려면 다음 URL을 사용합니다.
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 사용과 관련하여 필요한 사항을 변경하세요.
광고주를 만들 때 필수 결제 구성 포함
이제 billingConfig가 Advertiser 리소스의 필수 입력란입니다. advertisers.create 요청을 업데이트하여 이 필드가 설정되어 있는지 확인합니다. 새 Partner 리소스 billingConfig 필드를 통해 상위 파트너의 기본 결제 정보를 가져올 수 있습니다.
새 필드를 사용하여 타겟팅 최적화 제어
새로운 불리언 enableOptimizedTargeting 필드가 TargetingExpansionConfig 객체의 targetingExpansionLevel 필드를 대체했습니다.
새 KPI 필드를 사용하도록 게재 신청서 통합 업데이트
새로운 kpi 필드가 InsertionOrder 리소스의 performanceGoal 필드를 대체했습니다. 이 새 필드는 PerformanceGoal 객체 대신 Kpi 객체를 사용하고 새 필드와 enum을 사용합니다.
지원 중단된 서비스 및 필드 참조 삭제
이전 기능 지원 중단에 따라 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 서비스를 사용하여 규칙 기반 맞춤 입찰 알고리즘을 빌드하고 가져올 수 있습니다.
이 기능은 베타 버전이며 허용 목록에 있는 파트너만 사용할 수 있습니다. 파트너가 허용 목록에 추가되어 있지 않으면 요청에 오류가 반환됩니다.
달리 명시되지 않는 한 이 페이지의 콘텐츠에는 Creative Commons Attribution 4.0 라이선스에 따라 라이선스가 부여되며, 코드 샘플에는 Apache 2.0 라이선스에 따라 라이선스가 부여됩니다. 자세한 내용은 Google Developers 사이트 정책을 참조하세요. 자바는 Oracle 및/또는 Oracle 계열사의 등록 상표입니다.
최종 업데이트: 2025-07-25(UTC)
[null,null,["최종 업데이트: 2025-07-25(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,["# 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."]]
