Amazon Marketing Cloud
Upload first-party audience data and conversion signals to Amazon Marketing Cloud (AMC) for measurement, analytics, and campaign optimization across Amazon’s advertising ecosystem.
Prerequisites
- An Amazon Advertising account with AMC access
- Your Amazon Advertising Profile ID
- Your AMC Instance ID (optional, e.g.
amcyzzz123456) - Access to the Amazon Advertising API
Authentication
Amazon Marketing Cloud uses OAuth 2.0 via Amazon Advertising.
- 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). Each marketplace has a separate profile. Example: 1234567890 |
| AMC Instance ID | Text | No | Your Amazon Marketing Cloud instance identifier (e.g. amcyzzz123456). Captured for reporting context; audience uploads operate at the advertiser profile level. |
| 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 in AMC |
| Audience ID | Text | No | Existing AMC audience ID to update. Leave blank to create a new audience. |
| Country Code | Text | No | ISO 3166 two-character country code for audience records. Default: US |
Supported Operations
Sync Modes
This destination is audience-only and does not support standard data sync modes.
Audience Sync Modes
| Mode | Supported |
|---|---|
| Add | Yes |
| Remove | Yes |
| Mirror | Yes |
| Upsert | Yes |
Features
- Field Mapping: No
- Schema Introspection: No
How It Works
- Authentication: Zeotap obtains an OAuth 2.0 access token from Amazon and automatically refreshes it as needed.
- Audience creation: If no Audience ID is provided, Zeotap searches for an existing audience by name to avoid duplicates. If none is found, a new audience is created.
- Batch upload: User records are normalized, hashed with SHA-256 (email addresses and phone numbers), and uploaded via asynchronous jobs.
- Job lifecycle: Each batch creates an upload job, uploads records to the job, then completes the job. AMC processes the records asynchronously.
- Mirror mode: Uses diff operations to add new or changed records and remove deleted records in a single batch.
Identifier Handling / Match Keys
Identifiers can be supplied raw (Zeotap normalizes and SHA-256 hashes them at delivery) or pre-hashed:
| 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 |
external_id | string | Sent as-is (not hashed) |
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.
Batch Limits
- Up to 100,000 identifiers per upload job
- Larger batches are automatically chunked
Rate Limits
Amazon Advertising API enforces rate limits per profile. Zeotap handles rate limiting with automatic retry. Typical limits:
- 10 requests per second per advertiser profile
- 6,000 requests per 60-minute window for batch operations
Best Practices
- Use consistent identifiers: For best match rates, always include email or phone number. Normalize email addresses before mapping.
- Set the correct region: Profile IDs are region-specific. NA, EU, and FE profiles cannot be interchanged.
- Reuse audience IDs: Provide an existing Audience ID when updating an audience to avoid creating duplicates across sync runs.
- Country code: Set the correct country code for your audience. This improves matching accuracy within AMC.
Troubleshooting
Authentication failed: invalid or expired token
Your OAuth token may have expired. Reconnect your Amazon Advertising account in Zeotap by clicking Reconnect on the destination settings page.
Profile ID not found
Verify your Profile ID in the Amazon Advertising console under Account Settings. Each marketplace (US, UK, DE, etc.) has a separate Profile ID.
AMC Instance ID invalid
Confirm your AMC Instance ID with your Amazon account team. It typically follows the format amcyzzz123456. You can find it in the AMC UI or request it from your Amazon Advertising representative.
Region mismatch
Ensure you selected the correct region. NA, EU, and FE each have separate API endpoints and profiles. A profile created in the NA region cannot be used with the EU endpoint.
Audience creation failed
Check that your Amazon Advertising account has the advertising::campaign_management scope and that your profile has permission to create audiences in AMC. Contact your Amazon account representative if issues persist.
Low match rates
Low match rates typically indicate PII quality issues. Ensure email addresses are valid and phone numbers include country codes. AMC requires SHA-256 hashed identifiers — Zeotap handles this automatically. Pre-hashed data is never double-hashed: map digest columns to hashed_email / hashed_phone, and digests arriving on the raw fields pass through unchanged. If you pre-hash yourself, follow the normalization contract in Match Keys & Identifier Hashing — a digest of a wrongly normalized value uploads cleanly but matches nothing.
Upload job stuck or timed out
AMC processes uploads asynchronously. Large uploads may take several minutes to complete. If a sync appears stuck, check the sync run details in Zeotap for error messages. Retry the sync if the issue persists.