Yahoo demand-side platform (DSP) (formerly Verizon Media) provides a unified solution to advertisers to programmatically monitor, create, and manage advertising campaigns.

RudderStack supports Yahoo DSP as a destination where you can send your event data seamlessly.

Find the open source transformer code for this destination in the GitHub repository.

Getting started

Before configuring Yahoo DSP as a destination in RudderStack, verify if the source platform is supported by referring to the table below:

Connection ModeWebMobileServer
Device mode---
Cloud mode--Supported
To know more about the difference between cloud mode and device mode in RudderStack, refer to the RudderStack Connection Modes guide.

Once you have confirmed that the source platform supports sending events to Yahoo DSP, follow these steps:

  1. From your RudderStack dashboard, add the source. Then, from the list of destinations, select Yahoo DSP.
  2. Assign a name to your destination and click on Continue.

Connection settings

To successfully configure Yahoo DSP as a destination, you need to configure the following settings:

Yahoo DSP connection settings Yahoo DSP connection settings
  • Client ID: Enter the client ID from your Yahoo DSP account.
  • Client Secret: Enter the client secret from your Yahoo DSP account.
Refer to the Yahoo DSP documentation for more information on how to obtain the Client ID and Client Secret.
  • Account ID: Enter the Advertiser ID linked with your audience type.

  • Audience Type: Specify the type of the audience you want to update by choosing email, device ID, or IP Address from the dropdown. The default audience type is email.

    If you select the audience type as device ID, also choose the Seed List Type as shown:

    Yahoo DSP connection settings
  • Audience ID: Enter the ID of the created audience.

Refer to the FAQ section for more information on how to obtain Account ID and Audience ID.
  • Hash Required: This setting hash-encodes the user data and is enabled by default. However, you can disable it to prevent hashing.

audiencelist event structure

The following code snippet shows a sample audienceList call for email audience type:

{
"type": "audiencelist",
"properties": {
"listData": {
"add": [{
"email": 'alex@example.com'
},
{
"email": 'john@example.com'
}
]
}
}
}

The following code snippet shows a sample audienceList call for deviceId audience type:

{
"type": "audiencelist",
"properties": {
"listData": {
"add": [{
"deviceId": '34A668B2-03CF-11E5-8418-1697F925EC7B'
},
{
"deviceId": '34a66c5e-03cf-11e5-8418-1697f925ec7b'
}
]
}
}
}

The following code snippet shows a sample audienceList call for ipAddress audience type:

{
"type": "audiencelist",
"properties": {
"listData": {
"add": [{
"ipAddress": '10.1.7.237'
},
{
"ipAddress": '10.1.7.238'
}
]
}
}
}
You can send up to 50,000 email, deviceId, or ipAddress fields within one API call.
remove method is not supported in the listData.

Rate limit

The Yahoo DSP Traffic API is rate-limited and allows only a limited number of requests per user account, as shown:

TypeLimit
Requests per minute10
Requests per hour300
Requests per day5000
Refer to the Rate Limits documentation for more information.

FAQ

How do I obtain the Account ID?

The Account ID in the connection settings is the Advertiser ID associted with your Yahoo DSP account. To obtain it:

  1. Log into your Yahoo DSP account.
  2. Select Advertisers and click on the relevant advertiser to get the Advertiser ID as shown:
Yahoo DSP connection settings

How do I create an audience?

To create an audience, follow these steps:

  1. Log into your Yahoo DSP account
  2. Select Advertisers and choose the relevant advertiser.
  3. Select Targeting Library > New Custom Audience to create the required audience as shown:
Yahoo DSP connection settings

How do I obtain the Audience ID?

To obtain the Audience ID, follow these steps:

  1. Log into your Yahoo DSP account.
  2. Select Audiences and use the ID for relevant audience.
Yahoo DSP connection settings

Contact us

For more information on the topics covered on this page, email us or start a conversation in our Slack community.

Contents