Does AdSovereign support CTV?

Yes. CTV is supported via standard OpenRTB and VAST workflows, with SSAI-friendly bid request handling for instream and addressable TV inventory.

Is VPAID still supported?

VPAID 2.0 is supported where the partner environment allows execution. Many SSPs and publishers have deprecated VPAID, so it is best treated as conditional.

Can AdSovereign run a private exchange?

Yes. You can operate a closed marketplace with your own seat list, auction logic, deal routing, and internal-demand-first prioritization.

Is DOOH supported out of the box?

DOOH is supported as a custom deployment. Screen inventory, venue targeting, and loop-aware pacing require a custom integration layer rather than a generic connector.

Book a Pilot

Supported Formats

AdSovereign supports the ad formats enterprise programmatic actually trades — display, native, video, CTV, audio, DOOH, retail media, PMP and direct deals — across owned auction logic, rendering, identity, and measurement pipelines.

Key Facts

•Core: display, native, video (VAST), CTV, PMP / direct deals, private exchange, internal demand
•Conditional: VPAID supported only where the partner environment permits
•Modules / custom: audio (connector), DOOH (custom), retail media (add-on module)
•Each format has its own auction logic, latency budget, and identity model
•Compliance considerations vary by format, environment, and jurisdiction

In Simple Terms

Enterprise RTB is not one universal workflow. Display behaves differently from CTV, which behaves differently from DOOH. The matrix below makes the reality of what is supported — and how — explicit.

Media Format Matrix

Format	Status	Notes
Display	Supported	Standard IAB display sizes across web and in-app.
Native	Supported	OpenRTB Native 1.2 with custom asset templating.
Video / VAST	Supported	Instream and outstream VAST 4.x serving.
VPAID	Supported where environment allows	Many publishers and SSPs deprecate VPAID; serve only where the environment supports it.
CTV	Supported via OpenRTB / VAST workflows	Server-side ad insertion (SSAI) friendly via standard CTV bid request fields.
Audio	Connector-based / optional module	DAAST and audio-extended OpenRTB via dedicated connector.
DOOH	Custom deployment / connector-based	Screen inventory, venue targeting, and loop-aware pacing require a custom integration layer.
Retail Media	Add-on module	Sponsored product, on-site display, and off-site retargeting via the retail media module.
PMP / Direct Deals	Supported	Deal IDs, packaged inventory, and preferred deals.
Private Exchange	Supported	Operate a closed marketplace with your own seat list and auction logic.
Internal Demand Routing	Supported	Route impressions to internal buyers before exposing them to external demand.

Green = core supported · Yellow = conditional · Blue = optional module · Orange = custom deployment

Enterprise RTB Is Not One Universal Workflow

Each format carries operational, latency, identity, and measurement implications that shape how the stack must be configured and operated.

Auction logic

First-price, second-price, and hybrid auctions behave differently across display, video, and CTV. Floor strategy and bid landscape modeling differ accordingly.

Rendering pipelines

VAST/VPAID, native templating, and DOOH rendering each require distinct creative QA, latency budgets, and failure handling.

Latency budgets

CTV and video tolerate higher latency than display header bidding; audio and DOOH have their own envelopes tied to playback windows.

Identity & measurement

Identity coverage varies by format and environment. CTV, audio, and in-app rely on different identifiers than web display.

Compliance considerations

Children's content (COPPA), regulated verticals (HIPAA, financial), and jurisdictional rules apply differently across formats.

See the integration model behind these formats