CTV VAST Tag

The Ezoic CTV VAST tag monetizes video on Connected TV apps, streaming channels and TV-browser players with one HTTP request per ad opportunity. Ezoic runs a server-side auction across its demand partners and returns a standard VAST document. Your player, app or stitcher renders it like any other VAST response.

GET https://g.ezoic.net/ezoic/videoad/vast?<parameters>

No SDK is required. Every response is HTTP 200. A filled request returns a redirect or inline VAST XML, and a request with no fill returns an empty VAST document, so your player's normal no-ad path handles it.
Endpoint https://g.ezoic.net/ezoic/videoad/vast (GET; CORS enabled)
Ad format Instream video, one ad per request, VAST 2.0 to 4.2
Identity A website page URL, or an app bundle with an Ezoic-registered domain
Placement Ezoic provisions your placement. You send your normal video ad unit name in adunit.

Choose your integration

You run Use
A Roku channel using RAF Roku (RAF)
A stitcher, SSAI service or server-side fetcher Server-side (SSAI)
A Fire TV or Android TV app using IMA Fire TV and Android TV
A tvOS app using IMA Apple TV (tvOS)
A web or TV-browser player (IMA HTML5, video.js, JW Player) Web and TV-browser players
A Samsung Tizen or LG webOS app Samsung Tizen and LG webOS
An ad server that calls demand tags with macros Parameters and Server-side (SSAI)

Quickstart

  1. Pick your identity lane. Send url or d for a website. For an app or channel, send bundle with app_domain, and register the app first (see App identity).
  2. Send the core fields. devicetype=3, ifa with ifa_type, v (3 for Roku), real w and h, plcmt=1, and a cache buster cb.
  3. Add privacy and content signals you actually have. See Privacy and Content metadata.
  4. Test it. Run the curl in Testing and troubleshooting, then work through the go-live checklist in your platform guide.

For every parameter, default and allowed value, see the Parameters reference.