LiveIntent
Upload custom audiences to LiveIntent for people-based advertising across email and the open web. Zeotap syncs your warehouse audiences directly to LiveIntent’s Custom Audiences platform, enabling precise targeting and suppression.
Prerequisites
- A LiveIntent account with API access enabled
- An API access token from your LiveIntent account team
- Your LiveIntent Account ID
- Your Data Provider ID (typically 84 or 101)
Authentication
LiveIntent uses Bearer Token authentication.
- Contact your LiveIntent account team to obtain an API access token
- In Zeotap, select API Access Token as the authentication method
- Enter your Access Token
The access token grants permissions to create and manage custom audiences via the LiveIntent Audiences API.
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
| Account ID | Text | Yes | Your LiveIntent account ID |
| Data Provider ID | Select | Yes | Data provider for your account. Use Standard (84) for most cases or Extended (101). Default: Standard (84) |
Target Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Audience Name | Text | Yes | Name for the custom audience |
| Audience ID | Text | No | Existing audience ID. Leave blank to create a new audience |
| Identifier Type | Select | Yes | Type of identifiers to upload: Email Hash, IDFA, or AAID. Default: Email Hash |
Supported Operations
Sync Modes
This destination is audience-only and does not support standard data sync modes.
Audience Sync Modes: Add, Remove, Mirror, Upsert
| Mode | Description |
|---|---|
| Add | Adds identifiers to the audience |
| Upsert | Adds identifiers to the audience (idempotent, same as Add) |
| Remove | Removes identifiers from the audience |
| Mirror | Adds new/changed identifiers and removes deleted ones based on diff |
Features
- Field Mapping: No
- Schema Introspection: No
Identifier Types
LiveIntent supports three types of identifiers for audience matching:
| Type | Description | Format Requirements |
|---|---|---|
| Email Hash | Hashed email addresses | MD5 (32 chars), SHA-1 (40 chars), or SHA-256 (64 chars). Lowercase, no spaces. Unhashed emails are also accepted. |
| IDFA | iOS Advertising Identifier | Apple’s identifier for advertisers |
| AAID | Android Advertising Identifier | Google’s Android advertising ID |
When using Email Hash, Zeotap automatically normalizes (lowercase, trim) and hashes email addresses before upload if they are not already hashed.
How It Works
-
Audience Setup — On the first sync, Zeotap creates a new audience in LiveIntent (or uses an existing one if you provide an Audience ID). Subsequent syncs reuse the same audience.
-
Signed URL Upload — For each batch, Zeotap requests a signed upload URL from the LiveIntent API with the appropriate action (ADD, REMOVE, or REPLACE).
-
CSV Upload — Identifiers are formatted as a single-column CSV file and uploaded to the signed URL via HTTP PUT. Each identifier occupies one line.
-
Processing — LiveIntent processes the uploaded file asynchronously. Match rates and audience counts are available in the LiveIntent platform after processing completes.
Rate Limits
The LiveIntent Audiences API does not publish explicit rate limits. Signed URLs are valid for 30 minutes and can only be used once. Zeotap processes batches sequentially to ensure reliable uploads.
Best Practices
- Pre-hash identifiers when possible to avoid unnecessary processing. LiveIntent accepts MD5, SHA-1, and SHA-256 hashes.
- Use meaningful audience names to keep your LiveIntent account organized. Zeotap checks for existing audiences by name before creating new ones.
- Monitor match rates in the LiveIntent platform after syncs complete. Low match rates may indicate identifier format issues.
- Choose the right Data Provider ID — confirm with your LiveIntent account team which ID to use for your integration.
Troubleshooting
Authentication failed: invalid access token
Verify your access token is correct and has not expired. Contact your LiveIntent account team to obtain a new token if needed.
Audience creation failed with HTTP 400
The Account ID or Data Provider ID may be incorrect. Verify both values with your LiveIntent account team.
Low match rates after sync
Ensure identifiers are properly formatted. Email hashes must be lowercase hex strings with no spaces or special characters. Salted hashes are not supported.
Signed URL expired
Signed URLs are valid for 30 minutes. If a sync takes longer than expected, Zeotap will request a new signed URL for subsequent batches.
Upload failed with HTTP 403
Your access token may have expired or lack sufficient permissions. Request a new token from your LiveIntent account team.
Duplicate audience created
If you see duplicate audiences, ensure you specify an existing Audience ID in the target settings rather than relying on name-based lookup. Name-based deduplication requires exact string matching.