Omni Buy
One budget across seven channels
Vectravia builds an omnichannel demand-side platform for agencies, brands and in-house teams. It plans, buys and measures seven channels from one console, and it keeps the supply path in plain sight.
One console with six products. Together they cover planning, buying, supply-path checks, audiences, context and measurement across seven channels.
One budget across seven channels
Supply-path checks before every bid
Identity and consent handled up front
Contextual targeting, no user ID needed
Measured and modeled, labeled apart
Run it yourself or hand it over
Programmatic buying already has public records that say who may sell an impression and who handled it: ads.txt, app-ads.txt, sellers.json and the SupplyChain object. A buyer can read them at the moment of the bid, but only if the platform does it for them.
That matters because supply can be wide. In the ANA's 2023 transparency study, the average campaign ran across 44,000 websites. Vectravia's answer is to read those records before a bid is placed, prefer shorter authorized paths, and show the result next to the placement.
The same idea runs through the rest of the platform. Reporting says what was measured and what was modeled. Targeting reads consent first. Controls apply before a bid is placed, not after the report arrives.
Four rules shape how Vectravia is built and how this site is written.
Vectravia describes capabilities, not results. Third-party numbers appear only with their source and date.
A reported number should say whether it was counted or estimated, so a team can decide how far to trust it.
Bids, supply-path records and privacy signals use specifications the industry already publishes and maintains.
GPP and TCF strings are read before data is used, and contextual targeting works with no user identifier at all.
Every row links to the published specification and to a plain-English guide. Building on a standard is not the same as holding a certification, and this site makes no accreditation claims.
| Standard | What it does for a buyer | Read more |
|---|---|---|
| OpenRTB 2.6 | The bid request and response format. Version 2.6 adds ad pods for connected TV and a DOOH object for digital out-of-home. | Our guide, IAB Tech Lab |
| ads.txt and app-ads.txt | Public files where a publisher or app developer lists who may sell its inventory, marked DIRECT or RESELLER. | Our guide, IAB Tech Lab |
| sellers.json and the SupplyChain object | A seller directory and the chain of sellers carried inside a bid request. Compared together, they show who handled an impression. | Our guide, sellers.json spec |
| GPP and TCF | Signals that carry privacy, consent and consumer choice across many laws and regions. | Our guide, IAB Tech Lab |
| MRC viewability guidelines | The published definition of a viewable impression: 50 percent of pixels for one second on display, two seconds on video. | Our guide, MRC summary |
| UID2 | A named third-party identity service. Vectravia handles the DSP side of the token flow where publishers pass tokens. | Our guide, UID2 overview |
Vectravia is an omnichannel demand-side platform. Agencies, brands and in-house teams use it to plan, buy and measure connected TV, online video, display, native, audio, digital out-of-home and in-app advertising from one console.
Agency trading desks, brand marketing teams and in-house programmatic specialists. Each has a page under solutions.
OpenRTB 2.6 for bids, ads.txt, app-ads.txt and sellers.json for supply-path checks, the SupplyChain object inside bid requests, and GPP and TCF for privacy signals. The table on this page links to each one.
Yes. Vectravia has a self-serve console, and a managed desk for teams that prefer to hand over the day-to-day. Reporting is the same either way. Read the comparison.
Share the channels you buy and the questions you have, and the demo will cover them.