Send audiences to Yahoo DSP¶
Note
This topic contains information about configuring a destination that sends query results to Yahoo DSP using orchestrations. To configure a destination that sends audiences to Yahoo DSP using campaigns see this topic .
Yahoo DSP is a demand-side platform (DSP) to which you can send audiences, and then advertise across the Yahoo brand ecosystem, incluidng Yahoo, Yahoo Mail, TechCrunch, Yahoo Finance, Yahoo Sports, and Yahoo News.
What is DataX?
DataX is a component within the Yahoo Advertising infrastructure that allows Yahoo DSP to exchange data with external partners in a secure, automated, and scalable manner. DataX uses a partner-facing RESTful API to enable external partners (like Amperity) to send audiences to specific locations within the Yahoo DSP exchange’s taxonomy .
This destination enables your brand to manage audiences within the Yahoo DSP taxonomy from Amperity.
Amperity uses the PUT /TAXONOMY endpoint to determine the correct location within the Yahoo DSP taxonomy using your brand’s MDM ID. This ID must be validated each time an audience is sent, which can take up to 30 minutes, after which the audience is sent to Yahoo DSP.
Amperity uses the POST /AUDIENCE endpoint to manage the segment.
Note
Changes to audience lists are not immediately available in Yahoo DSP. Allow for up to 48 hours after the point at which Amperity has finished sending audience updates for them to be available.
Get details¶
Review the following details before configuring credentials for Yahoo DSP and before configuring Amperity to send audiences to Yahoo DSP.
|
Credential settings
|
|
|
Required configuration settings None. The segment name will be applied automatically if not specified. Membership duration defaults to 30 days. |
|
|
General Data Protection Regulation (GDPR) requirements To ensure that audiences are compliant with General Data Protection Regulation (GDPR) requirements for “information storage and access” and “personalization” features within the transparency consent framework you must include the following fields:
Both fields have a Boolean data type and may be set to “true” or “false”. When these fields are present in an audience, any users for whom the fields are not set or are both set to “false” will be omitted from the upload to Yahoo DSP. Only users who have both fields set and at least one field set to “true” are uploaded. Important If your brand knows your audience contains users who reside in the Europe and are protected by GDPR consent requirements you should include these fields in the audience to ensure that your brand meets GDPR consent requirements. |
Configure credentials¶
Configure credentials for Yahoo DSP before adding a destination.
An individual with access to Yahoo DSP should use SnapPass to securely share “seat MDM ID” details with the individual who will configure Amperity.
To configure credentials for Yahoo DSP
|
From the Settings page, select the Credentials tab, and then click the Add credential button. |
|
In the Credentials settings dialog box, do the following: From the Plugin dropdown, select Yahoo DSP. Assign the credential a name and description that ensures other users of Amperity can recognize when to use this destination. |
|
The settings that are available for a credential are determined by the credential type. For the “yahoo-dsp” credential type, configure settings, and then click Save.
|
Add destination¶
Use a sandbox to configure a destination for Yahoo DSP. Before promoting your changes, send a test audience, and then verify the the results in Yahoo DSP. After the end-to-end workflow has been verified, push the destination from the sandbox to production.
To add a destination for Yahoo DSP
|
|
Open the Destinations page, and then click the Add destination button. 
To configure a destination for Yahoo DSP, do one of the following:
|
|
|
Select the credential for Yahoo DSP from the Credential drop-down, and then click Continue. Tip Click the “Test connection” link on the “Configure destination” page to verify that Amperity can connect to Yahoo DSP. |
|
|
In the “Destination settings” dialog box, assign the destination a name and description that ensures other users of Amperity can recognize when to use this destination. Configure business user access By default a destination is available to all users who have permission to view personally identifiable information (PII). Enable the Admin only checkbox to restrict access to only users assigned to the Datagrid Operator and Datagrid Administrator policies. Enable the PII setting checkbox to allow users with limited access to PII access to this destination. Restricted PII access is enabled when the Restrict PII access policy option that prevents users who are assigned to that option from viewing data that is marked as PII anywhere in Amperity and from sending that data to any downstream workflow. |
|
Configure the following settings, and then click “Save”. Segment name (Required at orchestration)
Membership duration
|
|
After this destination is configured, users may configure Amperity to:
to Yahoo DSP. |