AI-generated Key Takeaways
-
Edits targeting options for a single advertiser by deleting and creating assigned targeting options in batches.
-
Uses an HTTP POST request to the endpoint
https://displayvideo.googleapis.com/v3/advertisers/{advertiserId}:editAssignedTargetingOptions
. -
Requires specifying the
advertiserId
as a path parameter and providingdeleteRequests
andcreateRequests
in the request body. -
Supports various targeting types including channel, digital content label exclusion, OMIO, sensitive category exclusion, and keyword.
-
Requires authorization with the
https://www.googleapis.com/auth/display-video
scope.
Edits targeting options under a single advertiser. The operation will delete the assigned targeting options provided in BulkEditAdvertiserAssignedTargetingOptionsRequest.delete_requests
and then create the assigned targeting options provided in BulkEditAdvertiserAssignedTargetingOptionsRequest.create_requests
.
HTTP request
POST https://displayvideo.googleapis.com/v3/advertisers/{advertiserId}:editAssignedTargetingOptions
The URL uses gRPC Transcoding syntax.
Path parameters
Parameters | |
---|---|
advertiserId |
Required. The ID of the advertiser. |
Request body
The request body contains data with the following structure:
JSON representation |
---|
{ "deleteRequests": [ { object ( |
Fields | |
---|---|
deleteRequests[] |
The assigned targeting options to delete in batch, specified as a list of Supported targeting types: |
createRequests[] |
The assigned targeting options to create in batch, specified as a list of Supported targeting types: |
Response body
If successful, the response body contains data with the following structure:
JSON representation |
---|
{
"createdAssignedTargetingOptions": [
{
object ( |
Fields | |
---|---|
createdAssignedTargetingOptions[] |
The list of assigned targeting options that have been successfully created. This list will be absent if empty. |
Authorization scopes
Requires the following OAuth scope:
https://www.googleapis.com/auth/display-video
For more information, see the OAuth 2.0 Overview.