Viant
Send events to Viant for advertising attribution and optimization
Viant (Adelphic) is a programmatic advertising platform for buying, attribution, and measurement across channels and devices. Ours offers two ways to send conversions to Viant, and your Viant program manager will tell you which one applies — the right choice depends on the verticals you advertise in and the matching strategy Viant has set up for your account.
Which integration should I use?
- Viant — the standard integration. Use this when Viant matches conversions on hashed identifiers (email, IP). Ours delivers conversion records to a Viant-owned bucket on a routine schedule. Recommended for most non-health advertisers.
- Viant Conversion API — the HIPAA-friendly, pseudonymized integration. Use this when you advertise in healthcare or another regulated vertical, or when Viant has asked you to attribute via their click ID and impression ID. Pseudonymized IDs only — no email, no IP, no device data.
If you are not sure which one to set up, ask your Viant program manager — they will tell you whether your account is configured for identifier-based matching or postback-based attribution.
Getting Started
- Contact support@oursprivacy.com to enable the right Viant destination for your account.
- Once enabled, we'll coordinate the Viant-side setup with your program manager.
- Configure your event mappings in the Ours platform.
Setup: Viant (standard)
- Navigate to Destinations in your Ours platform.
- Search for Viant and add it to your destinations.
- Provide your Viant Advertiser ID in destination settings.
- Configure mappings — common fields include the conversion event type, transaction ID, conversion amount, and optional product details.
Setup: Viant Conversion API (postback)
The Conversion API path needs Viant's click and impression IDs captured on your landing pages, so the first step happens in your Viant campaign setup — not in the Ours dashboard.
-
In Viant, configure your landing-page URLs to append the click and impression macros, e.g.:
https://yourdomain.com/landing?viant_click_id=${ADELPHIC_CLICKID}&viant_impression_id=${ADELPHIC_IMPRESSIONID}The Ours Privacy SDK auto-captures
viant_click_idandviant_impression_idfrom the URL and persists them across sessions. -
Navigate to Destinations in your Ours platform.
-
Search for Viant Conversion API and add it to your destinations.
-
Provide your Viant Advertiser ID in destination settings.
-
Configure mappings — the click and impression IDs default to the captured values; the event name should be a masked label (e.g.
Page View,Event 1).
Mapping notes
- Event names sent through Viant Conversion API must be PHI-masked. Use generic labels like
Event 1,Page View, never names likeappointment_booked. Ours does not auto-mask — masking is your responsibility. - Each conversion is attributed by a single ID — the click ID or the impression ID, never both. When both are captured on a visitor, Ours sends the click ID and leaves the impression ID blank; it only falls back to the impression ID when there is no click ID. This happens automatically — you do not need to coordinate which one to populate. A conversion with neither ID is skipped (there is nothing for Viant to attribute).
- The standard Viant integration supports a broader range of mapping fields (transaction ID, conversion amount, product info, etc.) — see the mapping screen in the app for the full list.
- The Viant Conversion API integration intentionally accepts no PII (no email, no IP, no device ID). Only Viant's pseudonymized IDs and a masked event name.
Additional Information
For more information about Viant's advertising platform, visit their website.
Please reach out to support@oursprivacy.com to enable the integration that fits your account.
How is this guide?

