What Nexus provides
Video channels, VAST tags, eligibility settings and video delivery / error reporting.
Video advertising
In-stream video advertising
A video ad before, during or after another video. Reach viewers inside a video-watching session.
IN PRACTICE
A simple example.
A short ad plays before a publisher’s news video. Player capabilities determine playback and skip behavior.
- Where it appears
- Compatible video players
- What to measure
- Starts · quartiles · completions
What you need to connect
A compatible content player and demand tag. Confirm VAST version, playback events and skip behavior with the integration.
Exact format support, enforcement and reporting depend on the connected revenue engine and agreed deployment configuration.
Plain-language definition
What is in-stream video advertising?
In-stream video advertising plays inside a video player before, during or after the requested content. The viewer experience depends on more than the media file: VAST metadata, wrapper depth, player capability, duration and tracking must work as one delivery chain.
Delivery path
From opportunity to measurable outcome.
The exact services differ by format, but every useful implementation keeps eligibility, delivery and evidence connected.
Measurement
Metrics that explain more than volume.
Use these metrics to evaluate the format. They are not a promise that every Nexus integration supplies every metric: player, publisher, analytics or conversion reporting may be needed.
Playback starts ÷ valid responses
Completed views ÷ starts
25%, 50%, 75% and complete events
VAST or player failures ÷ attempts
Operator guide
What clients should understand before launch.
What the user sees
A video creative plays inside the same player used for content. It may be skippable or non-skippable depending on the placement, creative and publisher policy.
How VAST fits
VAST describes media assets, impression tracking, click destinations, errors and playback events. A wrapper may point to another VAST response, creating additional demand hops and latency.
Why compatibility matters
Container, codec, bitrate, aspect ratio, duration and secure media delivery must be compatible with the player and environment. A valid XML response can still fail at playback.
Operator watchouts
Wrapper loops, excessive depth, slow media, unsupported codecs, duplicate tracking and unrealistic timeout budgets are common sources of lost video opportunities.
Frequently asked
Questions about in-stream video.
Pre-roll plays before requested content. Mid-roll appears during content at a defined break and therefore needs especially careful frequency and viewer-experience policy.
Build the right delivery path