Operators Guide
Configure destinations for Yahoo DSP¶
Yahoo DSP is a demand-side platform (DSP) to which you can send audiences. Advertise across the Yahoo brand ecosystem, including 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 Seat MDM ID
|
|
|
Required configuration settings Segment name is required. This is the name of the segment in Yahoo DSP and must be 255 characters or fewer. The segment can be an existing segment or a new segment within the Yahoo DSP taxonomy. Membership duration is configurable (“0” - “90” days) and controls how long audience members remain in the segment. The default is 30 days. Set to “0” to remove all audience members immediately. |
|
|
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” is 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 has 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 configures 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 vary by credential type. For the “yahoo-dsp” credential type, configure settings, and then click Save. Seat MDM ID
|
Add destination¶
Use a sandbox to configure a destination for Yahoo DSP. Before promoting your changes, send a sample audience, and then verify the results in Yahoo DSP. After verifying the end-to-end workflow, push the destination from the sandbox to production.
To add a destination for Yahoo DSP
|
|
Open the Destinations page, select the New destinations button, and then select Orchestration. 
To configure a destination for Yahoo DSP, do one of the following:
|
|
|
Select the credential for Yahoo DSP from the Credential dropdown, and then click Continue. Tip Amperity validates the connection when the destination is saved. If the connection cannot be validated, an error is shown and the destination is not saved. |
|
|
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 limited access to PII for this destination. Use the Restrict PII access policy option to prevent users from viewing data marked as PII anywhere in Amperity and from sending data to downstream workflows. |
|
Configure the following settings, and then click “Save”. Segment name (Required at orchestration)
Membership duration
|
|
After configuring this destination users may use:
|
|
Validate the audience with Yahoo DSP by using a sample audience with a very small membership. For example: 10 or 100 members or the minimum audience size recommended by Yahoo DSP. Send the sample audience to Yahoo DSP and verify the sample audience is correct in Yahoo DSP. Make adjustments if necessary. Only send full audiences after validation is complete. |
Workflow actions¶
A workflow will occasionally show an error that describes what prevented a workflow from completing successfully. These first appear as alerts in the notifications pane. The alert describes the error, and then links to the Workflows tab.
Open the Workflows page to review a list of workflow actions, choose an action to resolve the workflow error, and then follow the steps that are shown.
|
|
You may receive a notifications error for a configured Yahoo DSP destination. This appears as an alert in the notifications pane on the Destinations tab. 
If you receive a notification error, review the details, and then click the View Workflow link to open this notification error in the Workflows page. |
|
|
On the Workflows page, review the individual steps to determine which steps have errors that require your attention, and then click Show Resolutions to review the list of workflow actions generated for this error. 
|
|
|
A list of individual workflow actions are shown. Review the list to identify which action you should take. Some workflow actions are common across workflows and will often be available, such as retrying a specific task within a workflow or restarting a workflow. These types of actions can often resolve an error. In certain cases, actions are specific and are shown when certain conditions exist in your tenant. These types of actions typically must be resolved and may require steps that must be done upstream or downstream from your Amperity workflow. Amperity provides a series of workflow actions that can help resolve specific issues that may arise with Yahoo DSP, including: |
|
|
Select a workflow action from the list of actions, and then review the steps for resolving that error. After you have completed the steps in the workflow action, click Continue to rerun the workflow. |
Invalid MDM ID¶
The Seat MDM ID configured in the Yahoo DSP credential does not match a valid seat in the Yahoo DSP taxonomy. When an invalid MDM ID is detected, a workflow action named “Invalid MDM ID Included on Node” is generated.
The Seat MDM ID identifies your brand’s seat within the Yahoo DSP taxonomy. If the wrong value is configured, Amperity cannot place audiences in the correct location and the workflow cannot be retried until the credential is corrected.
To resolve this error, verify that the correct Seat MDM ID is configured in the Yahoo DSP credential.
Open the Amperity Credentials page in a new tab.
Verify the value for the Seat MDM ID field.
Tip
The Seat MDM ID is visible from the Advertisers page in Yahoo DSP. Log in to Yahoo DSP, open your brand’s profile, and look for the MDM ID field.
Update the Seat MDM ID value as necessary, and then save the credential.
Return to the workflow action, and then click Resolve to retry this workflow.
Invalid membership duration¶
The membership duration configured for this destination is outside the range accepted by Yahoo DSP. Membership duration must be between 0 and 90 days. When an out-of-range value is detected, a workflow action named “Invalid Expiration” is generated.
To resolve this error, update the membership duration setting for this destination.
Open the Yahoo DSP destination configuration.
Update the Membership duration setting to a value between “0” and “90”.
Save the destination configuration.
Return to the workflow action, and then click Resolve to retry this workflow.