Yahoo DSP
Sync audience segments to Yahoo DSP for programmatic advertising across the Yahoo ad network.
Prerequisites
- A Yahoo DSP account
- API client credentials (Client ID and Client Secret)
- Your Yahoo DSP Seat ID
Authentication
Yahoo DSP uses OAuth 2.0 Client Credentials grant.
- Obtain API client credentials from Yahoo
- Enter your Client ID and Client Secret in Zeotap
Zeotap automatically obtains and refreshes access tokens.
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
| Seat ID | Text | Yes | Your Yahoo DSP seat identifier. Example: 1234567 |
Target Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Audience Name | Text | Yes | Name of the Yahoo DSP audience segment |
| Audience ID | Text | No | Existing audience taxonomy ID to update. Leave blank to create new. |
Supported Operations
Sync Modes: Upsert
Audience Sync Modes: Add, Remove, Mirror, Upsert
Features
- Field Mapping: No
- Schema Introspection: No
Match Keys
Yahoo DSP matches audience members on hashed identifiers. Map raw columns and Zeotap normalizes and hashes them at delivery, or map pre-hashed SHA-256 hex digests directly:
| Field | Type | Description |
|---|---|---|
email | string | Raw email address — lowercased, trimmed, and SHA-256 hashed before upload |
hashed_email | string | Pre-hashed SHA-256 hex digest of the lowercase, trimmed email |
phone | string | Raw phone number — normalized to E.164 (digits with leading +) and SHA-256 hashed before upload |
hashed_phone | string | Pre-hashed SHA-256 hex digest of the E.164 phone number |
When both a raw field and its pre-hashed counterpart are mapped, the pre-hashed value wins. Values that are not valid 64-character hex digests are never uploaded — they are dropped (falling back to the raw column if mapped) and counted in the sync run logs. See Match Keys & Identifier Hashing for the full normalization contract, precedence, and validation rules.
Troubleshooting
Client credentials invalid
Verify your Client ID and Client Secret. Credentials can be regenerated in the Yahoo DSP platform.
Seat ID not found
Confirm your Seat ID in the Yahoo DSP interface. Each seat has a unique numeric identifier.