Viant
Sync first-party audience segments to Viant DSP for programmatic advertising across display, video, mobile, and connected TV. Zeotap uploads hashed identifiers to Viant’s VDP Connect API, enabling you to activate your warehouse audiences directly in the Viant Adelphic platform.
Prerequisites
- A Viant DSP account with API access enabled
- VDP Connect API credentials (username, password, and client ID) from your Viant representative
- Your Viant Adelphic Account ID
Permissions
Your Viant account must have VDP Connect API access. Contact your Viant Programmatic Account Specialist or Account Manager to request API credentials. Credentials are separate from your Viant DSP login.
Authentication
Viant uses VDP Connect Credentials authentication.
- Contact your Viant representative to obtain API credentials (username, password, and client ID)
- Review and sign the Viant API Terms & Conditions
- In Zeotap, navigate to Destinations and click Add Destination
- Select Viant from the destination list
- Enter your Username, Password, and Client ID
- Click Test Connection to verify
Zeotap automatically obtains and manages Bearer tokens for API access.
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
| Account ID | Text | Yes | Your Viant Adelphic account ID. Example: 12345 |
| API Environment | Select | Yes | API endpoint. Default: Production |
Target Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Segment Name | Text | Yes | Name for the first-party audience segment in Viant DSP |
| Segment ID | Text | No | Existing segment ID. Leave blank to create a new segment |
| TTL (seconds) | Text | No | Time-to-live for audience members in seconds. Min: 172800 (2 days), Max: 32000000. Default: 2592000 (30 days) |
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
Required Mapping Fields
| Field | Description |
|---|---|
| Email address. Normalized and SHA256 hashed before upload |
Default Destination Fields
| Field | Type |
|---|---|
email | string |
phone | string |
ip_address | string |
mobile_id | string |
How It Works
- Authentication: Zeotap authenticates with the VDP Connect API using your credentials to obtain a Bearer access token.
- Segment creation: If no segment ID is provided, Zeotap creates a new first-party segment in your Viant account with the specified name and TTL.
- Data preparation: Identifiers are normalized and SHA256 hashed (email, phone) or sent as-is (IP, mobile ID) before upload.
- Batch upload: Records are uploaded in batches of up to 10,000 identifiers per request to the VDP Connect segments data endpoint.
- Sync modes: Add/Upsert operations add identifiers to the segment. Remove operations expire identifiers. Mirror uses diff operations to add new rows and expire removed rows.
All audiences created via the API appear under Targeting > Data > 1st Party Segments in the Viant DSP UI.
Supported Identifier Types
| Identifier | Format | Hashing |
|---|---|---|
| Standard email address | SHA256 (auto-applied) | |
| Phone | 10-digit US format | SHA256 (auto-applied) |
| IP Address | IPv4 | None (sent as-is) |
| Mobile ID | IDFA or GAID | None (sent as-is) |
Rate Limits
The Viant VDP Connect API enforces payload size limits of up to 10 MB per request and validates up to 1,000 bad records per batch. Zeotap uploads data in batches of 10,000 records and processes batches sequentially to stay within limits. Data population in the Viant platform may take up to 24 hours.
Best Practices
- Use hashed identifiers: Zeotap automatically normalizes and SHA256 hashes email and phone numbers. Ensure source data contains valid, non-empty values.
- Set appropriate TTL: Choose a TTL that matches your campaign duration. The default 30-day TTL works well for most use cases.
- Mirror mode for ongoing syncs: Use Mirror mode for recurring syncs to keep your Viant segments in sync with your warehouse audiences, automatically adding new members and removing stale ones.
- Monitor bad records: Check sync results for bad record counts, which indicate invalid identifiers that Viant rejected.
Troubleshooting
Authentication failed
Verify your username, password, and client ID are correct. VDP Connect API credentials are separate from your Viant DSP login. Contact your Viant representative if credentials have expired.
Segment not appearing in DSP
Segments created via the API appear under Targeting > Data > 1st Party Segments in the Viant DSP UI. Data population may take up to 24 hours after upload.
Bad records in sync results
Bad records indicate identifiers that failed Viant’s validation. Common causes include malformed email addresses, invalid phone number formats, or missing required fields. Check your source data quality.
TTL validation error
TTL must be between 172,800 seconds (2 days) and 32,000,000 seconds. If not specified, the default of 2,592,000 seconds (30 days) is used.
Rate limiting or timeout errors
The VDP Connect API has payload size limits. Zeotap batches uploads to 10,000 records per request. If you experience timeouts with large audiences, consider reducing sync batch sizes or increasing sync frequency.
Account ID mismatch
Ensure the Account ID matches your Viant Adelphic account. The account ID can be found in your Viant DSP interface or provided by your Viant representative.