Yahoo DSP
Sync audience segments to Yahoo DSP for programmatic advertising across the Yahoo ad network.
Prerequisites
- A Yahoo DSP account with a user enabled for DSP API access
- API client credentials (Client ID and Client Secret), shown once under My Account → Activate in the DSP UI
- The numeric advertiser ID the audiences belong to
Authentication
Yahoo DSP uses an OAuth 2.0 client credentials grant in which the client proves its identity with a token signed by the Client Secret (see Yahoo’s Setup & Access Guide ).
- Obtain API client credentials from the Yahoo DSP UI
- Enter your Client ID and Client Secret in Zeotap
Zeotap signs the request, obtains the access token and renews it automatically. The Client Secret itself is never sent to Yahoo.
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
| Advertiser account ID | Text | Yes | The numeric Yahoo DSP advertiser ID. Yahoo ties every custom audience to one advertiser, and only that advertiser’s campaigns can use it. Example: 1356341 |
| Seat ID | Text | No | No longer used. Kept so older destinations still load. |
Existing destinations: a Yahoo DSP destination created before Advertiser account ID existed stops syncing with a message asking for it. Edit the destination and set Advertiser account ID.
Target Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Audience Name | Text | Yes | Name of the Yahoo DSP custom audience. If the advertiser already has an audience with exactly this name, Zeotap reuses it. Otherwise it is created with the first upload. |
| Audience ID | Text | No | Existing custom audience ID to update. Leave blank to find the audience by name, or create it. |
| Identifier | Select | No | Email (default) or Phone number. A Yahoo custom audience holds one kind of identifier, so rows without it are skipped and not counted as failed. |
How members are synced
Zeotap uses Yahoo’s Custom Audiences API. Members are added and removed in batches of up to 50,000 hashed identifiers. Remove and Mirror syncs remove members that left the audience.
Yahoo keeps a custom audience’s members for 180 days unless they are uploaded again.
With Audience Boost, the boosted users go to a separate <Audience Name>_boosted audience, found or created the same way. Because the audience holds one kind of identifier, Boost adds only identifiers of the selected Identifier: on an Email audience, boosted phone numbers are skipped.
When Yahoo throttles an upload (HTTP 429), Zeotap waits and sends it again, up to five attempts in all. It waits as long as Yahoo asks, or otherwise backs off from 2 seconds, never more than 2 minutes at a time. Server errors and dropped connections are retried the same way on requests that are safe to resend. Rows of an upload still refused after its last attempt are counted as failed.
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, and that the user they belong to has DSP API access enabled. If the secret was lost, Yahoo DSP Support can issue a new one.
”Advertiser account ID is required”
The destination was created before this field existed. Edit it and set Advertiser account ID.
”an audience named … already exists … but is a … audience”
The advertiser has another kind of audience (for example a lookalike) with the same name. Choose a different Audience Name, or set Audience ID.
Rate limits
Yahoo limits each API user to 30 member updates per minute and 100 per hour by default. Zeotap retries throttled uploads, which covers the per-minute limit; the hourly limit cannot be waited out within one upload. If you run into it, set a rate limit on the destination, or ask your Yahoo account team to raise the limit.