Configure destinations for Viant DSP

Viant DSP is a demand-side platform (DSP) that enables programmatic advertising campaigns across display, video, connected TV (CTV), audio, and native channels. Viant uses household-level identity that is linked to real people and real households to deliver and measure advertising that reaches specific customers across devices and channels. Audience segments built in Viant DSP can target customers using hashed emails, phone numbers, IP addresses, mobile device IDs, or cookie IDs.

Use Amperity to build audience segments and send them to Viant DSP for use in programmatic advertising campaigns. Amperity syncs hashed identifier data, such as emails, phone numbers, IP addresses, mobile device IDs, or cookie IDs, to first-party audience segments in Viant DSP, where they become targetable in DSP campaigns.

Note

This destination uses the VDP Connect API .

How this destination works

Amperity sends audience data to Viant DSP using an incremental workflow. Each run sends only new or changed records. Amperity creates the audience segment in Viant DSP automatically if it does not already exist.

A Viant DSP destination works like this:

	AUTHENTICATE Amperity authenticates to Viant DSP using an OAuth2 refresh token. Amperity exchanges the refresh token for a short-lived access token, which is used for all API requests in the workflow.
	RESOLVE AUDIENCE SEGMENT Amperity looks up the audience segment by name using the GET /v1/audiences endpoint, paginating through all results until a match is found. If the segment does not exist, Amperity creates it using the POST /v1/audiences endpoint with the configured account ID, advertiser ID, and identifier type. New segments start with INACTIVE status and activate after they accumulate at least 1,000 matched records. Important The segment data type cannot be changed after the segment is created. To use a different identifier type, configure a new segment name.
	NORMALIZE AND HASH IDENTIFIERS Important Viant DSP only accepts SHA256 hashed identifiers for email addresses, phone number and physical addresses. Amperity normalizes and hashes each value in the identifier column before sending it to Viant DSP. Identifier type Transform Email Trims whitespace, converts to lowercase, removes angle-bracket aliases, then SHA-256 hashes. Phone Number Normalizes to 10-digit US format, strips formatting characters, then SHA-256 hashes. IP, Cookie, Mobile ID Sent as-is. No hashing required.
	SEND ADDITIONS Amperity sends new audience members to Viant DSP using the POST /v1/audiences/{id}/data endpoint in batches of up to 50,000 rows. Batches run in parallel. Viant DSP processes data every 10 minutes and updates segment status after each processing cycle. Members already present in Viant DSP from a prior run are counted as cached rows and are not re-sent.
	SEND DELETIONS AND END WORKFLOW When audience members are removed from the segment in Amperity, Amperity sends a deletion request to Viant DSP using the PUT /v1/audiences/{id}/data endpoint. Note Deletions are processed asynchronously by Viant DSP and take effect within 24 hours. The workflow ends after all additions and deletions are sent.

Get details

Review the following details before configuring credentials for Viant DSP and before configuring Amperity to send audience segments to Viant DSP.

	Credential settings Refresh token Required The OAuth2 refresh token for the Viant Advertiser account. This token is issued by Viant during the OAuth2 authorization flow and should be treated as a secret. Tip Contact your Viant account representative to initiate the OAuth2 authorization flow and obtain a refresh token.
	Required destination settings Account ID Required The Viant account ID. Required when Amperity creates a new audience segment. The account ID is available from your Viant account representative. Advertiser ID Required The Viant advertiser ID. Required when Amperity creates a new audience segment. The advertiser ID is available in Viant DSP under Settings > Advertisers.
	Required orchestration settings Audience name Required The name of the audience segment in Viant DSP. If the segment does not exist, Amperity creates it automatically using the configured account ID and advertiser ID. Identifier type Required The type of identifier in the audience data. Options: Email, Phone Number, IP, Cookie, Mobile ID. This value must match the data type of the Viant audience segment. The segment data type cannot be changed after the segment is created. Audience primary key Required The primary key for the audience. Set to “identifier”.
	A query or segment that returns an identifier column containing the identifier values to send to Viant DSP. The identifier type must match the Identifier type setting. Important Viant DSP only accepts SHA256 hashed identifiers for email addresses, phone number and physical addresses.

Configure credentials

Configure credentials for Viant DSP before adding a destination.

An individual with access to Viant DSP should use SnapPass to securely share “refresh token” details with the individual who configures Amperity.

To configure credentials for Viant DSP

	From the Settings page, select the Credentials tab, and then click the Add credential button.
	In the Credentials settings dialog box, do the following: From the Plugin dropdown, select Viant DSP. Assign the credential a name and description that ensures other users of Amperity can recognize when to use this destination.
	The settings that are available for a credential vary by credential type. For the “viant-dsp” credential type, configure settings, and then click Save. Refresh token Required The OAuth2 refresh token for the Viant Advertiser account. This token is issued by Viant during the OAuth2 authorization flow and should be treated as a secret.

Add destination

Use a sandbox to configure a destination for Viant DSP. Before promoting your changes, send a sample audience, and then verify the results in Viant DSP. After verifying the end-to-end workflow, push the destination from the sandbox to production.

To add a destination for Viant DSP

	Open the Destinations page, select the New destinations button, and then select Orchestration. To configure a destination for Viant DSP, do one of the following: Click the row in which Viant DSP is located. Destinations list alphabetically and you can scroll up and down the list. Search for Viant DSP. Start typing “via”. The list filters to show only matching destinations. Select “Viant DSP”.
	Select the credential for Viant DSP from the Credential dropdown, and then click Continue. Tip Amperity validates the connection when the destination is saved. If the connection cannot be validated, an error is shown and the destination is not saved.
	In the “Destination settings” dialog box, assign the destination a name and description that ensures other users of Amperity can recognize when to use this destination. Configure business user access By default a destination is available to all users who have permission to view personally identifiable information (PII). Enable the Admin only checkbox to restrict access to only users assigned to the Datagrid Operator and Datagrid Administrator policies. Enable the PII setting checkbox to allow limited access to PII for this destination. Use the Restrict PII access policy option to prevent users from viewing data marked as PII anywhere in Amperity and from sending data to downstream workflows.
	Configure the following settings, and then click “Save”. Account ID Required The Viant account ID. Required when Amperity creates a new audience segment. The account ID is available from your Viant account representative. Advertiser ID Required The Viant advertiser ID. Required when Amperity creates a new audience segment. The advertiser ID is available in Viant DSP under Settings > Advertisers. Audience name (Required at orchestration) The name of the audience segment in Viant DSP. If the segment does not exist, Amperity creates it automatically using the configured account ID and advertiser ID. Identifier type (Required at orchestration) The type of identifier in the audience data. Options: Email, Phone Number, IP, Cookie, Mobile ID. This value must match the data type of the Viant audience segment. The segment data type cannot be changed after the segment is created. Audience primary key The primary key for the audience. Set to “identifier”.
	After configuring this destination users may use: Orchestrations to send query results Orchestrations and campaigns to send audiences Orchestrations and campaigns to send events
	Validate the audience with Viant DSP by using a sample audience with a very small membership. For example: 10 or 100 members or the minimum audience size recommended by Viant DSP. Send the sample audience to Viant DSP and verify the sample audience is correct in Viant DSP. Make adjustments if necessary. Only send full audiences after validation is complete.