Send data to Yahoo DSP¶
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.
This topic describes the steps that are required to send email addresses to Yahoo DSP from Amperity:
Get details¶
Yahoo DSP requires the following configuration details:
|
Your brand’s MDM ID. Required. The “Site MDM ID” is the value of your brand’s Master Data Management (MDM) ID in Yahoo DSP. This is a unique advertiser ID that assigns your brand a specific location within the Yahoo DSP taxonomy. Tip You can find your brand’s Site MDM ID from the Yahoo DSP user interface. Log in to Yahoo DSP, then navigate to the Advertisers page. Open your brand’s profile. The Site MDM ID is available from the MDM ID field. 
|
|
|
The name of a segment in Yahoo DSP. This can be the name of an existing segment or be a new segment. |
|
|
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. |
Add destination¶
Configure Amperity to send email addresses directly to Yahoo DSP.
To add a destination
|
Open the Destinations tab to configure a destination for Yahoo DSP. Click the Add Destination button to open the Destination dialog box. 
Enter a name for the destination and provide a description. For example: “Yahoo DSP” and “This sends email addresses to Yahoo DSP”. From the Plugin drop-down, start typing “yah” to filter the list, and then select Yahoo DSP. |
||||||
|
Credentials allow Amperity to connect to Yahoo DSP. The credential type is set automatically. You may use an existing credential or you may add a new one. 
Select an existing credential from the Credential drop-down. – or – Select Create a new credential from the Credential drop-down. This opens the Credential dialog box. 
Enter the name for the credential, and then add a description. Yahoo DSP has the following settings:
When finished, click Save. |
||||||
|
Each destination has settings that define how Amperity will deliver data to Yahoo DSP. These settings are listed under the Settings section of the Destination dialog box. 
The following settings are specific to Yahoo DSP:
|
||||||
|
Business users are assigned to the Amp360 User and/or AmpIQ User policies. (Amp360 User allows access to queries and orchestrations and AmpIQ User allows access to segments and campaigns.) A business user cannot select a destination that is not visible to them. Business users – including users assigned to the DataGrid Operator policy – may have restricted access to PII. What is restricted access to PII? 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. You can make this destination visible to orchestrations and allow users with restricted access to PII to use this destination by enabling one (or both) of the following options: 
Note To allow business users to use this destination with campaigns, you must enable the Available to campaigns option within the data template. This allows users to send campaign results from Amperity to Yahoo DSP. The other two settings may be configured within the data template instead of the destination. |
||||||
|
Review all settings, and then click Save. 
Important You must configure a data template for this destination before you can send data to Yahoo DSP. |
Add data template¶
A data template defines how columns in Amperity data structures are sent to downstream workflows. A data template is part of the configuration for sending query and segment results from Amperity to an external location.
To add a data template
|
|
From the Destinations tab, open the menu for a destination that is configured for Yahoo DSP, and then select Add data template. This opens the Add Data Template dialog box. 
Enter the name of the data template and a description. For example: “Yahoo DSP” and “Send email addresses to Yahoo DSP.”. |
||||||
|
|
Verify business user access to queries and orchestrations and access to segments and campaigns. A business user may also have restricted access to PII, which prevents them from viewing and sending customer profile data. 
If business user access was not configured as part of the destination, you may configure access from the data template. Important To allow business users to use this destination with campaigns, you must enable the Available to campaigns option. This allows users to send campaign results from Amperity to Yahoo DSP. If you enable this option, the data extension settings require using campaign name and group name template variables to associate the name of the data extension to your campaign. |
||||||
|
|
Verify all configuration settings. The following settings are specific to Yahoo DSP:
|
||||||
|
|
Review all settings, and then click Save.
After you have saved the data template, and depending on how you configured it, business users can send query results and/or send campaigns to Yahoo DSP. |