Integrations / Advertising
Viant
Server-side conversion onboarding to the Viant DSP (Adelphic) via the VDP Connect Conversion API. Delivers an array of conversion records (accountId, advertisers, salesData) with SHA-256 hashed email, raw IP, and cookie/mobile-ID identity signals, mapped to Viant conversionEventType values (PageView, ItemView, AddToCart, InitiateCheckout, AddPaymentInfo, Purchase, Lead).
Datafly Signal delivers first-party events to Viant server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Viant expects.
Why route Viant through Datafly Signal
Conversions survive ad blockers and tracking prevention
A browser tag served from an advertising domain is blocked outright for part of your traffic, and Safari's ITP shortens the cookies it can set. Signal sends the event from your own server, so the conversions Viant optimises against are not filtered by the browser.
Email hashed before it leaves your infrastructure
Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so Viant receives match keys rather than raw personal data.
Token lifecycle is handled for you
Signal obtains and refreshes the OAuth credentials Viant requires, so nothing expires quietly in the middle of a campaign.
One consent decision governs every destination
Viant is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
What ships in the blueprint
Mapped events
add_payment_infoadd_to_cartbegin_checkoutgenerate_leadpagepurchaseview_itemVertical presets
Retail. Each preset starts from a working configuration for that vertical rather than a blank field map.
Full field mappings, configuration fields, and troubleshooting are in the Viant documentation.
Frequently asked questions
Does Datafly Signal integrate with Viant?
Yes. Datafly Signal delivers first-party events to Viant server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Viant expects. The integration is included in every deployment at no additional cost.
How is server-side Viant tracking different from the Viant tag?
The Viant tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to Viant from your server, so delivery does not depend on browser conditions.
What personal data is sent to Viant?
Email are normalised and SHA-256 hashed inside your own deployment before delivery, so Viant receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to Viant?
The blueprint ships with mappings for add_payment_info, add_to_cart, begin_checkout, generate_lead, page, purchase, view_item. Any event in your schema can be mapped to Viant through pipeline configuration without a code change.
Do I need to keep the Viant tag on my site?
No. Server-side delivery is designed to replace the tag. Most teams run both briefly during migration, using shared event IDs so Viant deduplicates, then remove the tag once server-side volume matches.
Other advertising integrations
Ready to move Viant server-side?
See how Datafly Signal delivers first-party events to Viant from infrastructure you control, with hashed identity and consent enforcement built in.