Amazon DSP
Upload audience segments to Amazon DSP for programmatic display and video advertising across Amazon’s ad network.
Prerequisites
- An Amazon Advertising account with DSP access
- Your Amazon Advertising Profile ID
- Access to the Amazon Advertising API
Authentication
Amazon DSP uses OAuth 2.0 via Amazon.
- Click Connect with OAuth in Zeotap
- Sign in with your Amazon Advertising account
- Authorize the requested permissions
OAuth scope: advertising::campaign_management.
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
| Profile ID | Text | Yes | Your Amazon Advertising profile ID (numeric). Example: 1234567890 |
| Region | Select | Yes | Amazon Advertising region: North America (NA), Europe (EU), or Far East (FE). Default: NA |
Target Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Audience Name | Text | Yes | Name for the audience segment |
| Audience ID | Text | No | Existing audience ID to update. Leave blank to create new. |
Supported Operations
Sync Modes: Upsert, Mirror
Audience Sync Modes: Add, Remove, Mirror, Upsert
Features
- Field Mapping: No
- Schema Introspection: No
Match Keys
Amazon 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
Profile ID not found
Verify your Profile ID in the Amazon Advertising console. Each marketplace has a separate Profile ID.
Region mismatch
Ensure you selected the correct region. NA, EU, and FE each have separate API endpoints and profiles.