Viant

Datafly Signal delivers conversion events to the Viant DSP (Adelphic) server-to-server using the VDP Connect Conversion API. This onboards your online and offline conversions for measurement, reporting, and campaign optimisation without a browser pixel, so delivery is unaffected by ad blockers or browser tracking prevention.

Prerequisites

Before configuring Viant in Signal you need a Viant DSP account with VDP Connect enabled and a set of API credentials.

Configuration

Configure in Signal

1. Go to Integrations > Add Integration > Viant.
2. Choose the Retail preset (page, product view, cart, checkout, payment, purchase, and lead events) or Default.
3. Enter your client_id, client_secret, account_id, and advertiser_id.
4. Select the consent categories that apply (typically advertising or marketing).
5. Click Save.

API Endpoint

PUT https://vdp-connect-api.viantinc.com/v1/conversions

Authentication is OAuth 2.0: Signal exchanges your client_id and client_secret for a short-lived Bearer access token at https://vdp-connect-api.viantinc.com/v1/oauth2/token, then sends the conversions with Authorization: Bearer <token>. The token is cached and refreshed automatically.

The request body is a JSON array of conversion records (up to 10 MB per request). Signal batches events automatically.

Identity Signals

Viant matches conversions to users using an identifiers array. Each entry has a type and a value. The more signals you provide, the higher your match rate.

How to send user data

Call datafly.identify() when a user logs in, registers, or submits a form. Signal normalises and hashes the email before sending it to Viant as email_sha256:

datafly.identify("user-123", {
  email: "jane.doe@example.com"
});

IP and anonymous_id (cookie) are attached automatically on every event — no configuration needed.

Event Mapping

Retail preset

Signal maps GA4-style event names to Viant conversionEventType values:

To customise, edit the integration’s Field Mappings in the Management UI.

Example: Purchase event

Datafly.js call:

datafly.identify("user-123", { email: "jane.doe@example.com" });
 
datafly.track("Order Completed", {
  order_id: "ORD-001",
  revenue: 129.99,
  currency: "USD",
  products: [
    { product_id: "SKU-A", product_name: "Widget", price: 49.99, quantity: 2 },
    { product_id: "SKU-B", product_name: "Gadget", price: 30.01, quantity: 1 }
  ]
});

Viant payload sent by Signal:

[
  {
    "accountId": 12345,
    "advertisers": [67890],
    "salesData": {
      "transactionId": "ORD-001",
      "conversionEventType": "Purchase",
      "conversionTimestamp": "2026-06-06T15:32:00Z",
      "amount": 129.99,
      "currency": "USD",
      "identifiers": [
        { "type": "email_sha256", "value": "5e8848...e3b0c4" },
        { "type": "ip", "value": "203.0.113.50" },
        { "type": "cookie", "value": "a1b2c3d4e5f6" }
      ],
      "purchasedItems": [
        { "itemId": "SKU-A", "productName": "Widget", "price": 49.99, "quantity": 2 },
        { "itemId": "SKU-B", "productName": "Gadget", "price": 30.01, "quantity": 1 }
      ]
    }
  }
]

Testing

1. Trigger a conversion event on your site (e.g. complete a test order).
2. In Signal’s event debugger, confirm the event resolves to the correct conversionEventType and that the identifiers array contains a hashed email, IP, and cookie.
3. In your Viant DSP account, check the conversion onboarding / measurement reports for the records to appear. Onboarded conversions are queued for processing, so allow time for them to surface in reporting.
4. A 200 response means the batch was accepted; a 400 response includes a bad_records count and per-record validation details.

Troubleshooting