Fraud Avoidance¶
This article describes resources that enable you to provide line-level fraud protection.
Overview¶
The proprietary fraud avoidance solution for Yahoo is TalonPro. TalonPro is always enabled to protect campaigns from robotic, non-human traffic. The DSP additionally supports optional 3rd Party fraud avoidance targeting for lines serving display and video ads to ensure that ads are properly represented and delivered to real people, rather than to non-human audiences.
Endpoint¶
Use the following endpoint to read or specify line-level fraud avoidance settings.
/traffic/lines/{id}/targeting
A
GETrequest enables you to view line-level fraud avoidance for the specified line.A
POSTrequest enables you to add line-level fraud avoidance for the specified line.
Resources¶
The targeting resource is the standard Yahoo DSP resource for targeting consumers based on their profiles, behaviors, and ad content.
The targeting resource is defined by the following fraud avoidance type-specific fields:
Parameter |
Parameter Type |
Definition |
Data Type |
Required |
|---|---|---|---|---|
|
path |
Specifies the line ID. |
|
Y |
|
body |
Specifies the bot fraud prevention partner. |
|
Y |
|
body |
Specifies an array of targeting types to update, enable, or disable.
To learn more, refer to Targeting Types. |
|
Y |
Note
For a complete list of targeting resource fields, refer to Targeting Object.
Add/Update Fraud Avoidance¶
Add or update fraud avoidance 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.
Example Request URL¶
POST https://dspapi.admanagerplus.yahoo.com/traffic/lines/365277/targeting/
Example Request Body¶
{
"bots": [
"IAS"
],
"types": [
{
"name": "BOT",
"isTargeted": true
}
]
}
Example Response¶
{
"response": {
"types": [
{
"name": "BOT",
"isTargeted": true
}
],
"bots": [
"IAS"
],
"errors": null,
"timeStamp": "2018-01-12T01:57:40Z"
}
}