Bot Targeting

This article describes resources that enable you to provide line-level bot fraud protection.

Overview

The Oath Ad Platforms DSP supports BOT targeting for lines serving display and video ads so that you can ensure your ads are properly represented and delivered to real people, rather than to bot traffic.

Note

Bot targeting is only available via special role.

Endpoint

Use the following endpoint to read or specify line-level bot protection settings.

/traffic/lines/{id}/targeting
  • A GET request enables you to view line-level bot protection for the specified line.
  • A POST request enables you to add line-level bot protection for the specified line.

Resources

The targeting resource is the standard Oath Ad Platforms DSP resource for targeting consumers based on their profiles, behaviors, and ad content.

This resource comprises multiple fields that enable you to specify line targeting across many types of targets including the SEGMENT, EXCHANGES, and BOT target types.

The targeting resource is defined by the following BOT targeting type-specific fields:

Field Description Data Type
id Specifies the line ID. integer
bots

Specifies an array of bot fraud prevention partners:

  • DOUBLE_VERIFY
  • IAS
array

Note

For a complete list of targeting resource fields, see Targeting Object.

Add/Update Bot Targets

Specifies line-level bot fraud protection for the specified line.

POST /traffic/lines/{id}/targeting/

Parameters

The line ID is specified in the path of the URL. All other parameters are specified in the body of the application/json payload.

Parameter Parameter Type Definition Data Type Required
id path Specifies the line lD. integer Y
bots body Specifies an array of fraud protection partners. array Y
types body

Specifies an array of targeting types to target. To target deals, BOT targeting type must be specified.

To learn more, see Targeting Types.

array Y

Example Request

The line ID is specified in the path of the resource endpoint:

POST traffic/lines/365277/targeting/

All other parameters are specified in the body of the application/json payload.

{
  "bots": [
    "IAS"
  ],
  "types": [
    {
      "name": "BOT",
      "isTargeted": true
    }
  ]
}

See also

About Targeting