AI-generated Key Takeaways
-
This document details how to delete an assigned targeting option from an insertion order using the Display & Video 360 API v3.
-
The Display & Video 360 API v3 has been sunset; users should use v4 instead.
-
The DELETE request requires the advertiser ID, insertion order ID, targeting type, and the assigned targeting option ID as path parameters.
-
This API call supports deleting various targeting types, including age range, browser, category, channel, and more.
-
Successful deletion results in an empty response body and requires the
https://www.googleapis.com/auth/display-video
OAuth scope.
Deletes an assigned targeting option from an insertion order.
Supported targeting types:
TARGETING_TYPE_AGE_RANGE
TARGETING_TYPE_BROWSER
TARGETING_TYPE_CATEGORY
TARGETING_TYPE_CHANNEL
TARGETING_TYPE_DEVICE_MAKE_MODEL
TARGETING_TYPE_DIGITAL_CONTENT_LABEL_EXCLUSION
TARGETING_TYPE_ENVIRONMENT
TARGETING_TYPE_GENDER
TARGETING_TYPE_KEYWORD
TARGETING_TYPE_LANGUAGE
TARGETING_TYPE_NEGATIVE_KEYWORD_LIST
TARGETING_TYPE_OPERATING_SYSTEM
TARGETING_TYPE_PARENTAL_STATUS
TARGETING_TYPE_SENSITIVE_CATEGORY_EXCLUSION
TARGETING_TYPE_VIEWABILITY
HTTP request
DELETE https://displayvideo.googleapis.com/v3/advertisers/{advertiserId}/insertionOrders/{insertionOrderId}/targetingTypes/{targetingType}/assignedTargetingOptions/{assignedTargetingOptionId}
The URL uses gRPC Transcoding syntax.
Path parameters
Parameters | |
---|---|
advertiserId |
Required. The ID of the advertiser the insertion order belongs to. |
insertionOrderId |
Required. The ID of the insertion order the assigned targeting option belongs to. |
targetingType |
Required. Identifies the type of this assigned targeting option. Supported targeting types:
|
assignedTargetingOptionId |
Required. The ID of the assigned targeting option to delete. |
Request body
The request body must be empty.
Response body
If successful, the response body is an empty JSON object.
Authorization scopes
Requires the following OAuth scope:
https://www.googleapis.com/auth/display-video
For more information, see the OAuth 2.0 Overview.