(1) New: Replace Audience Endpoint

Added support for completely replacing all audience IDs within an existing audience segment.

• Replaces all existing audience IDs with a new batch within 24 hours
• Intended for bulk refresh or full overwrite of an active (live) segment
• Returns a JOB ID used for asynchronous status checks
• Best practice: do not add or replace audiences again until the job is complete

Key Notes:

• The viantSegmentId in the request body must match the URL
• Audience data type must match the original segment’s data type (cannot infer from hashed values)

(2) New: Expire Specific Audiences

Introduced a new method to expire (remove) individual audience IDs from an active audience segment.

• Removes only the specified hashed values
• Action completes within 24 hours
• Returns a JOB ID to check status via Job Status Retrieval

Key Notes:

• segmentId in the body must match the endpoint
• dataType must match the original segment configuration

(3) New: Support for SHA256 Phone Number–Based Audience Creation

You can now onboard and activate phone number–based 1P audiences using SHA256-hashed phone numbers.

Preprocessing requirements (before hashing):

• Strip country code (U.S. numbers must be 10 digits)
• Remove all symbols: +, -, parentheses, spaces
• No extensions
• Hash the final 10-digit number

This enhancement adds full parity between email and phone-based identifiers for audience ingestion workflows.

Conversion API (CAPI) Support

• Seamlessly onboard conversion events alongside your audiences with VDP Connect's new /v1/conversions endpoint.

• Track any of the following out-of-the-box standard events:

  • PageView
  • LandingPage
  • ItemView
  • AddToCart
  • InitiateCheckout
  • AddPaymentInfo
  • Purchase
  • Lead
  • If you have a custom event, that cannot be mapped to above standard list of events, you can pass custom advertiser defined event name to Viant too.

• Custom Metadata Flexibility

  • Support for up to 10 advertiser-defined custom key-value pairs per account.
  • Flexible Identifier Schemes

• Hash-based or device/IP identifiers supported, including:

  • Hashed_email
  • Advertising IDs
  • IP addresses
  • Cookie IDs
  • Hashed_physical_address

• Rich Event Context

  • Timestamps in UTC (e.g. 2025-07-28T15:32:00Z)
  • Channel: Online vs. In-store
  • Geolocation: Country/State/City for precise attribution

• Batch & Async Processing

  • Send up to 10MB per payload
  • Have lot of data? Our API supports gzipped payload. Specify Content-Encoding: gzip  in the HTTP header and attach gzipped payload.

Set default expiration for "Audience Segments"

• Set default time-to-live (ttl) when creating audience segments.
  • If the ttl expires, the segment will become archived.
  • ttl is measured in seconds. For example, 345600 represents 345600 seconds.
  • The minimum ttl is 2 days (172800 seconds), and the maximum ttl is 32000000 seconds.
  • If the user does not provide a ttl, the default ttl is 32000000 seconds.

Support for onboarding & activating 1st party audiences

• Full authentication flow for CDPs, partners, advertisers, and agencies

• Support for JWT-based authorization and OAuth2 token management

• Endpoints to:

  • Create and update audience segments
  • Add audience data
  • Expire/retire segments
  • Submit user opt-out requests
  • Retrieve job status for opt-out processing