One budget and pacing view
Set spend once and watch delivery across seven channels in one place.
Omni Buy plans and buys connected TV, online video, display, native, audio, digital out-of-home and in-app from a single budget, with one pacing and frequency view.
Omni Buy is the buying layer of Vectravia. You set one budget and one set of goals, and Omni Buy bids on each channel using the OpenRTB object that channel actually sends: Video for online video and CTV, Banner for display, Native, Audio, App and DOOH.
Because every channel draws from the same budget, pacing and frequency are counted across all of them. A household that has already seen your ad on a TV screen is not treated as a stranger when the same campaign reaches a phone an hour later.
Set spend once and watch delivery across seven channels in one place.
Frequency caps count exposures across channels, not inside each one.
CTV bids use OpenRTB 2.6 ad pods (structured, dynamic and hybrid) and read the ssai signal.
DOOH bids use the OpenRTB DOOH object and the Qty multiplier for audience-based screens.
Buy on the open exchange or through private marketplace deals in the same campaign.
VAST and creative specs are checked per channel before a line item goes live.
Choose a total budget, flight dates and the outcome you care about. Channels are selected, not pre-funded one by one.
Add the channels you want and any private marketplace deals. Each channel keeps its own formats and creative specs.
Each bid request is read through its OpenRTB object, so CTV pods, DOOH multipliers and native assets are priced correctly.
Spend and frequency are tracked across every channel, and pacing shifts budget to where the goal is being met.
Cross-channel buying depends on bid requests that describe each format precisely. These additions are recent.
3
types of CTV ad pod described in OpenRTB 2.6: structured, dynamic and hybrid
14.2
impressions: the spec example for how many a single DOOH screen play may count as
6
emerging CTV ad formats covered by IAB Tech Lab format signaling, from pause ads to squeezebacks
| Standard | What it does here |
|---|---|
| OpenRTB 2.6 IAB Tech Lab | Bid requests and responses for every channel, including ad pods (Video and Audio) and the DOOH and Qty objects. |
| CTV Programmatic Guide IAB Tech Lab | Reference for podded bidding, VAST delivery and app-ads.txt validation on connected TV. |
| app-ads.txt IAB Tech Lab | Seller authorization for apps on mobile and CTV app stores before a bid is placed. |
Omni Buy works on these channels today. Each channel page explains the formats and standards involved.
Ad pods and SSAI-aware bidding
In-stream and out-stream video
Streaming audio and podcasts
Screens in the real world
Mobile apps with app-ads.txt checks
Supply-path checks against ads.txt and sellers.json before every bid.
Measured and modeled numbers, labeled apart.
Self-serve console or managed desk, same reporting either way.
No. You set one budget for the campaign. Omni Buy paces it across the channels you select and shows spend per channel in the same view.
It reads the pod fields that OpenRTB 2.6 added to the Video object (such as podid, podseq and slotinpod) and the imp.ssai signal, then bids on structured, dynamic or hybrid pods as the seller describes them.
Digital out-of-home requests carry a DOOH object and a Qty multiplier that states how many impressions one play counts as. Omni Buy prices and reports against that multiplier.
Yes. Private marketplace deals and open exchange inventory can sit in one campaign, and both draw on the same budget and frequency caps.
Book a walkthrough of the console with your channels, your supply and your reporting needs.