Yahoo DSP Integration for Nodus
1. Introduction to the Yahoo DSP Integration
What Is This Integration?
The Yahoo DSP integration connects your Yahoo Demand-Side Platform account with Nodus, allowing you to extract, analyze, and transform advertising data including campaign performance, creative insights, and audience metrics. This integration functions as a source connector, bringing your Yahoo DSP data into the Nodus ecosystem for advanced analytics and business intelligence.
Prerequisites:
- An active Yahoo DSP account
- Valid API credentials (Client ID and Client Secret)
- Access to the seats and advertisers you want to extract data from
- Permissions to access the Yahoo DSP API
Connection Overview:
The integration uses Yahoo's Demand-Side Platform API to extract advertising data and metrics. Authentication is handled through OAuth 2.0 using Client ID and Client Secret, and data is extracted based on predefined report templates or user-defined configurations.
2. Platform Setup Documentation (Setup Form for Yahoo DSP)
Purpose & Scope
This section covers how to set up the initial connection between Nodus and Yahoo DSP by providing the necessary authentication credentials.
Field-by-Field Breakdown:
Integration Name
- Field Name & Label: Integration Name
- Description & Purpose: A descriptive name to identify this Yahoo DSP integration within your Nodus account.
- Validation Rules & Format: Text string, required field.
- Examples: "Yahoo DSP - Main Account", "Digital Advertising Data"
- Troubleshooting Tips: Use a descriptive name that clearly identifies the specific Yahoo DSP account or purpose.
Client ID
- Field Name & Label: Client ID
- Description & Purpose: The unique identifier for your Yahoo DSP API client application.
- Validation Rules & Format: Alphanumeric string, required field.
- Examples: "abcdef123456"
- Troubleshooting Tips: You can find your Client ID in the Yahoo DSP developer portal or from your Yahoo DSP account representative.
Client Secret
- Field Name & Label: Client Secret
- Description & Purpose: The secret key associated with your Client ID, used for authentication.
- Validation Rules & Format: Alphanumeric string, required field.
- Examples: "xyz789abcdef012345"
- Troubleshooting Tips: Keep your Client Secret secure and do not share it. If your Client Secret is compromised, you should regenerate it in the Yahoo DSP developer portal.
External Link
- Link Label: "Locate your Client Information"
- URL: https://developer.yahooinc.com/dsp/api/docs/authentication/vmdn-auth-overview.html
- Purpose: Provides access to official Yahoo DSP API documentation for authentication.
Step-by-Step Guide:
- Obtain API credentials from Yahoo DSP:
- Contact your Yahoo DSP account representative to request API access
- Once approved, you will receive your Client ID and Client Secret
- Alternatively, you may need to register an application in the Yahoo Developer Portal
- Enter your integration details in the Nodus setup form:
- Provide a meaningful Integration Name
- Enter your Client ID
- Enter your Client Secret
- Save the configuration and test the connection
Reference Links:
3. Extraction/Query Configuration (Extraction Form for Yahoo DSP)
Purpose & Overview
This section explains how to configure data extraction from Yahoo DSP. The form allows you to select specific report templates and define date ranges for data extraction.
Template & Field Documentation:
Template Selection
- Field Name & Label: Select a template
- Description & Purpose: Defines which type of Yahoo DSP data to extract
- Validation Rules & Format: Dropdown selection, required field
- Available Options:
- Yahoo DSP Ad Dimensions - Campaign and creative level metrics with ad metadata
- Yahoo DSP Inventory Dimensions - Inventory source data including exchange and domain metrics
- Yahoo DSP Raw Performance - Detailed performance metrics at various levels of granularity
- Troubleshooting Tips: Select the template that best aligns with your analytics goals.
Lookback Range
- Field Name & Label: Lookback Range
- Description & Purpose: Specifies how many days back to extract data
- Validation Rules & Format: Dropdown selection, required field
- Available Options:
- 3-day Range
- 7-day Range
- 28-day Range (recommended)
- 90-day Range (Optimal if 90-day DDA is used)
- Troubleshooting Tips: Larger date ranges will result in more data being extracted but may take longer to process. The recommended range is 28 days for most use cases.
Historic Date Selection
- Field Name & Label: Historic Date
- Description & Purpose: For historical data extraction, specifies a custom date range
- Validation Rules & Format: Date picker, required field
- Troubleshooting Tips: Yahoo DSP typically maintains historical data, but there may be limitations on how far back you can extract certain metrics.
Workflow & Examples:
- Select the appropriate template (e.g., "Yahoo DSP Ad Dimensions" for campaign and creative metrics)
- Choose a lookback period or specific historic date range
- Preview the query to confirm configuration
- Execute extraction
Example Use Cases:
Ad Performance Analysis:
- Template: Yahoo DSP Ad Dimensions
- Lookback: 28-day Range
- Purpose: Analyze creative performance across campaigns
Inventory Source Analysis:
- Template: Yahoo DSP Inventory Dimensions
- Lookback: 90-day Range
- Purpose: Evaluate performance across different inventory sources and domains
Detailed Performance Metrics:
- Template: Yahoo DSP Raw Performance
- Historic Date: Custom range for specific campaign periods
- Purpose: Deep dive into comprehensive performance metrics including viewability and completion rates
4. Data Mapping & Underlying Models for Yahoo DSP
Data Model Overview
The Yahoo DSP integration extracts data using predefined query templates that map to specific dimensions and metrics available in the Yahoo DSP reporting API.
Schema & Field Mapping
Ad Dimensions Template
| Field | Description |
|---|---|
| Ad | The name or identifier of the ad |
| Ad Size | Dimensions of the ad (e.g., 300x250) |
| Advertiser | The advertiser name |
| Campaign | The campaign name |
| Campaign Current Schedule Total Budget | Current total budget for the campaign schedule |
| Campaign Schedule Name | Name of the campaign schedule |
| Campaign Daily Budget | Daily budget for the campaign |
| Campaign Total Budget | Total budget for the campaign |
| Creative Ad Description | Description text for the creative |
| Creative Ad Title | Title of the creative |
| Creative | Name or identifier of the creative |
| Creative Format | Format of the creative (Display, Video, etc.) |
| Creative Landing Page Url | Landing page URL for the creative |
| Line Channel Type | Channel type for the line |
| Channel Type | Type of channel for the campaign |
| Line Daily Budget | Daily budget at the line level |
| Line | Name or identifier of the line |
| Line Schedule Name | Name of the line schedule |
| Goal Type | Goal type for the campaign (CTR, Viewability, etc.) |
Inventory Dimensions Template
| Field | Description |
|---|---|
| Exchange | Ad exchange where impressions were served |
| Subdomain | Subdomain of the website where ads appeared |
| Inventory Type | Type of inventory (Web, Mobile App, etc.) |
| Domain | Domain of the website where ads appeared |
| App Name | Name of the mobile app where ads appeared |
| Campaign | The campaign name |
Raw Performance Template
| Field | Description |
|---|---|
| Ad | The name or identifier of the ad |
| Deal ID | Identifier for programmatic deals |
| Exchange ID | Identifier of the ad exchange |
| Campaign | The campaign name |
| Creative | Name or identifier of the creative |
| Line | Name or identifier of the line |
| Package | Name of the package |
| Domain | Domain of the website where ads appeared |
| Site Name | Name of the website |
| Supply Group | Group of supply sources |
| Site Group Name | Name of the site group |
| Subdomain | Subdomain of the website where ads appeared |
| App Name | Name of the mobile app where ads appeared |
| 25% Complete | Number of video views that reached 25% completion |
| 50% Complete | Number of video views that reached 50% completion |
| 75% Complete | Number of video views that reached 75% completion |
| 100% Complete | Number of video views that completed fully |
| Companion Clicks | Clicks on companion ads |
| Companion Impressions | Impressions on companion ads |
| Unique Households | Number of unique households reached |
| Clicks | Number of clicks received |
| Advertiser Spending | Total spending by the advertiser |
| Impressions | Number of ad impressions delivered |
| Inventory Cost | Cost of the inventory |
| Yahoo Measurable Impressions | Number of impressions measurable by Yahoo |
| Yahoo Viewable Impressions | Number of impressions viewable according to Yahoo |
| Nonviewable Impressions | Number of impressions not viewable |
| Ad Serving Cost | Cost for ad serving |
| Ad Verification Cost | Cost for ad verification services |
| Audience Measurement Cost | Cost for audience measurement |
| Brand Safety Cost | Cost for brand safety measures |
| Other Cost | Other miscellaneous costs |
| Platform Fee | Fee for using the platform |
| Total Data Fee | Total cost for data usage |
| Total Variable Cost | Total variable costs |
| Viewability Cost | Cost for viewability measurement |
| Yahoo Data Fee | Fee for Yahoo data |
| Total Vendor Fee | Total fees paid to vendors |
| Third Party Segment Fee | Fee for third-party audience segments |
| Programmatic Guaranteed Deal Fee | Fee for programmatic guaranteed deals |
| Third Party Data Fees | Fees for third-party data |
| Yahoo Demo Fee | Fee for demographic targeting |
| Yahoo Segment Fee | Fee for Yahoo audience segments |
| Yahoo Suppression Data Fee | Fee for audience suppression data |
| Filtered Clicks | Number of filtered clicks |
| Filtered Companion Clicks | Number of filtered companion clicks |
| Filtered Companion Impressions | Number of filtered companion impressions |
| Filtered Impressions | Number of filtered impressions |
| Estimated Billable Amount | Estimated amount to be billed |
| Audience Impressions | Number of impressions on target audience |
| Unique Converters | Number of unique users who converted |
5. Troubleshooting & FAQs for Yahoo DSP
Common Issues & Error Messages
Authentication Failures
- Error: "Invalid client credentials" or "Authentication failed"
- Solution: Verify your Client ID and Client Secret. Ensure they are correctly entered without any leading or trailing spaces. If issues persist, contact your Yahoo DSP representative to confirm your API credentials are active.
Missing Data
- Common Causes:
- Date range outside of data availability
- No activity for the selected template dimensions
- Permissions issues with specific advertisers or seats
- Solution: Verify that data exists for the selected date range in the Yahoo DSP UI. Ensure your API credentials have access to the seats and advertisers you're trying to extract data from.
Contact & Support Information
- Nodus Support: support@nodus.com
Best Practices for Yahoo DSP Connections
- Schedule regular extractions to maintain a current view of your advertising performance
- Consider adding custom reporting templates for specific analysis needs
- Keep your Client Secret secure and rotate it periodically according to your security policies