Browse the help center

Video placements

Set up a video placement step by step — skip button, ad pods and competitive separation, VMAP ad breaks, the RTB video signals, the VAST tag and its version picker, VAST event tracking — with the caveats, a fix-it checklist, the field reference and a link to the server-side ad insertion (SSAI) guide.

How-to network manager publisher admin Account → Publishers → site → zone → placement (Video)

What it is and why

A video placement is the slot a video player fills: it answers one tag URL — VAST (any version from 2.0 to 4.3), VPAID or VMAP — with the creative, the skip rule, the pod and the tracking pixels the player should fire. You set the player behaviour once on the placement, and every creative that wins the slot is wrapped the same way; the player only needs the URL.

Example. A sports site’s player asks for a pre-roll before each highlight clip. The placement says skip after 5 seconds, one ad per request, VAST 4.2. The player loads the tag, gets a single 15-second creative with quartile and skip pixels, and the viewer can skip at second five. Switch Return (ads in pod) to 3 and Max. pod duration to 60 and the same URL now answers with a three-ad break of at most 60 seconds, filled one spot at a time.

Typical scenarios

You wantSetWhere
A skippable pre-roll, skip after 5 sShow skip ad button on, Show after 5Basic info → VAST configuration
A mid-roll break of up to 3 ads, at most 90 s, never two car brands back to backReturn (ads in pod) 3, Max. pod duration 90, Competitive separation = One spot per advertiser domain and advertiser categoryVAST configuration
A full ad plan for a long clip: one ad before, one at a third, one at two thirds, one afterVMAP Break sequence 1-1-1-1 with Play the last break after the content onVMAP configuration
Programmatic buyers told the player plays muted and takes 15–30 s creativesPlayback method Auto-play sound off, Min. 15 / Max. ad duration 30RTB configuration (needs Video RTB Configuration)
Viewability in reports on a third-party playerLeave the VAST version at 4.2 and wire at least one Viewability eventAd tags & API → VAST tags; VAST tracking card
A CTV channel whose stitcher calls the tag on the viewer’s behalfServer-side ad insertion (SSAI) = the stitcherVAST configuration — see Video behind server-side ad insertion

The skip, pod and VMAP settings apply to every creative the placement serves, directly linked or programmatic. The RTB block only describes the player to buyers — it never filters a creative you linked yourself (see the caveats).

Step by step

  1. Open the saved placement of the Video type (create one). The video blocks (VAST / VPAID / VMAP / RTB) sit inside the Basic info card; the tag URLs are on the Ad tags & API card further down. A video placement carries a Size — two Landscape Video Player units (1024×768 and 480×320) or Custom Video Player — but, unlike a Site Placement, it is not required: unset, the slot takes any video creative.

  2. In VAST configuration, decide on the skip button and the pod:

    VAST configuration with skip button, pod settings, competitive separation and default ad title

    • Show skip ad button and Show after (seconds) — 0–60; the seconds field unlocks only when the checkbox is on;
    • Return (ads in pod) — how many creatives one request returns (1–20);
    • Max. pod duration (sec) — total pod length (10–1800, empty = no restriction; the arrows move by 10, any whole number in range is accepted);
    • Competitive separation in a pod — keeps competing advertisers out of one break (see Keeping competitors apart in a pod);
    • Default ad title — used when a creative carries no title;
    • Server-side ad insertion (SSAI) — names the stitcher that calls the tag, if any (see Tell Epom which stitcher calls the tag);
    • Send the publisher’s price in VAST — off by default; on, the VAST answer carries the publisher’s net CPM (see Pricing in the VAST answer). Shown only to a role with Manage Pricing, and changeable only with it enabled;
    • Publisher video requirements — read-only; shown only when your role can view video creative requirements and the site’s requirements are switched on. It is the site’s video spec, which decides which uploaded videos are served here, with an Edit on the site link.
  3. VPAID configuration shows the linear-break cap (Show no more than … ads), read-only. VMAP configuration carries one Ad breaks control, answered in one of two ways:

    • Pre-rolls only — a run of pre-rolls capped by Max pre-rolls (1–10).
    • Break sequence — a real ad-break plan: one number per break, and the number is how many ads that break asks for. 1-1-1-1 is four breaks of one ad, 2-2-2 three breaks of two, and the sizes need not match (3-1-1-2). The first break plays before the content and the rest divide it between them (three breaks give start, 33% and 66%), because the response is built before anyone knows how long the content is and a percentage means the same thing for a two-minute clip and a feature film.

    Play the last break after the content makes the sequence’s last break the post-roll rather than adding one more after it — it asks for its own number of ads, and the breaks left divide the content. 1-5 with it on is one ad before the content and five after; 1-1-1 is start, 50% and the end. A single break with it on is a post-roll alone. A timeline under the control shows where the breaks land.

    Ad breaks control with a break per stepper, the post-roll toggle and a timeline of where the breaks land

  4. In RTB configuration — drawn only if your role holds Video RTB Configuration — declare what your player supports so programmatic demand bids correctly: Playback method and API framework (multi-select), Min. / Max. ad duration (sec) and Skip min (sec). The placement’s other bid-request settings — custom tag id, IAB categories, blocked categories and creative attributes — are on the separate RTB configuration card: Set a placement’s OpenRTB settings.

    RTB video configuration with playback methods, API frameworks and durations

  5. Click Save. One save writes Basic info together with every VAST / VPAID / VMAP / RTB preference — there is no separate save inside the groups.

  6. Copy the tag for your player from Ad tags & API → VAST tags (the tab sits before the Video Player demo tab):

    VAST tab with the VAST tag field, its version picker, and the VPAID and VMAP tags

    • if your network has more than one ad-serving domain, pick the Domain on the Settings tab first — the picker is there whenever at least one domain is configured, and the choice saves on the placement the moment you make it;
    • pick the spec your player asks for in the VAST version picker on the VAST tag row — 2.0, 3.0, 4.0, 4.1, 4.2 or 4.3, 4.2 by default. Only the version changes, not the key, domain or defaults. Leave it at 4.2 unless your player demands otherwise — 4.1 is the lowest version that can be viewability-measured;
    • copy the VAST tag, VPAID or VMAP URL with the copy button. All three carry the Domain, Protocol and any default parameters from Settings, and the tab refreshes them when you change a setting.
  7. Optionally switch on the events you want recorded in the VAST tracking card (below). A new placement already carries the events an admin ticked under Default VAST tracking events → New video placements (Rules, defaults and taxonomies).

    VAST tracking card with grouped playback events and progress points

VAST tracking card

Appears on saved video placements; editing it needs the Manage Placement’s VAST Events permission. Three sections:

  • Playback events — toggle which standard VAST events are recorded, grouped as Quartiles & completion (loaded, creative view, start, first quartile, midpoint, third quartile, complete), Interaction (skip, mute/unmute, pause/resume, fullscreen, expand/collapse) and Viewability & other. Select all / Deselect all / Save. Change the defaults a new placement arrived with like any hand-picked set.

    The four Viewability events — Ad viewable impression, Ad repeated viewable impression, Ad not viewable impression and Ad view undetermined impression — are what Open Measurement reports on a third-party player. Wire at least one of them to something, or the tag carries no measurement at all: Epom will not load a verification script that has nowhere to report to. A third-party pixel set to fire on a viewability event counts as wiring it, so a placement can be measured without ticking an Epom action at all.

  • Progress points — fire a conversion action at a custom playback time: pick the action, enter the time as HH:mm:ss, Add. Existing points list in a table with multi-select delete.

  • Third-party pixels — fire an external tracking URL on impression, click or a specific VAST event of your choice. Click a pixel’s URL or its Fires on value to change it in place.

The banner and the placement both have VAST tracking — which fires?

A video banner has the same kind of card, and the VAST response combines the two:

  • Third-party pixels add up. Every pixel of the banner and every pixel of the placement is written into the VAST (<Impression>, click tracking and event <Tracking> elements alike) — the banner’s first, then the placement’s. A partner’s pixel set on both is called twice.
  • Progress points add up too: each one, from either card, gets its own tracking URL.
  • Playback events do not double. Each standard event is recorded once. Switched on in both cards, the placement’s setting is the one written into the VAST, so the event is recorded under the conversion action the placement uses for it; switched on in only one card, that card’s is used.

Caveats and exceptions

Who can do this. Publishers and network managers get the same page, including the VAST tracking card and the tag tabs. The RTB configuration group needs Video RTB Configuration; the VAST tracking card needs Manage Placement’s VAST Events to edit; Send the publisher’s price in VAST needs Manage Pricing. A Can View share sees the preference fields read-only, can still copy the tag URLs, and sees only the events that are on. A demo account’s Preview opens the demo showcase page with this placement’s VAST tag in the demo player. Exact grants: User roles.

The whole video block saves with the Basic info Save button. Edit the pods and navigate away without saving Basic info and the changes are lost — the unsaved-draft banner offers to restore them on return.

RTB durations and playback methods are signals, not filters. A directly linked 60-second creative still serves even if Max. ad duration says 30; the constraint reaches programmatic demand only. To keep an uploaded file off a publisher’s inventory, use the site’s video creative requirements instead.

A break sequence answers with breaks only when the viewer could be served at all — the same checks Pre-rolls only makes before it picks a creative: consent, the placement switched on, its pretargeting, and at least one linked creative left after targeting, limits and capping. Otherwise the VMAP response is empty rather than a set of breaks whose every ad request comes back empty. Nothing is auctioned or counted for the VMAP response itself: each break asks the VAST tag for its own ads when the player reaches it.

VPAID and VMAP tags ignore the version picker. VMAP is pinned to VAST 3.0 and cannot move: the templateType attribute in the VMAP 1.0 schema has no value above vast3, so there is no legal name for a newer template. VPAID is pinned too, but the server has two answers — the endpoint that rebuilds tags against a chosen domain returns 3.0, while the fallback used when there is no domain to rebuild against returns 4.0. Both sit below the 4.1 floor, so neither can be viewability-measured.

A tag copied from the classic placement page cannot be viewability-measured. That page still shows a fixed row per tag — VAST 3.0, VAST 4.0, VPAID and VMAP — with no version picker, and every one of them is below the 4.1 floor Open Measurement needs. Take the tag from the new interface’s VAST tags tab instead. A tag already pasted into a player at 3.0 or 4.0 carries no viewability either; re-copying it at 4.2 is the fix only if that player implements Open Measurement — in one that does not, no tag version produces viewability, and while Open Measurement is enabled such a player receives no <ViewableImpression> at all.

Two different things are titled RTB configuration. The group in step 4 lives inside Basic info and describes your player. The separate RTB configuration card further down carries the custom tag id and the IAB categories sent in bid requests; it appears on every saved placement if your role has OpenRTB access, not just on video ones — Set a placement’s OpenRTB settings.

In read-only mode the VAST tracking card hides entirely when nothing is configured — no events, no progress points, no pixels. Its absence does not mean the feature is missing.

Advanced settings on a video placement offer Domain as default channel, plus Disable auto-Linking and Flexible placement size if your role allows them. Branded overlay, Refresh after (sec) and Always redirect belong to the display family and are not offered here.

Keeping competitors apart in a pod

A pod is filled one spot at a time, each the winner of the auction among what is left. Before a winner joins the pod it is compared with the spots already in it, and when it conflicts it is passed over for this break and the next winner is tried:

  • The same spot never plays twice in one break, whatever the setting — two creatives with the same ISCI / Ad-ID code, or a DSP bid whose VAST carries that code in <UniversalAdId>. Creatives without a code are only told apart by creative.
  • One spot per advertiser domain — a second spot from an advertiser with the same domain (the advertiser’s Advertiser domain; https://www.toyota.com/ and toyota.com are one) is passed over. A DSP bid is compared by the adomain in its own bid, not by the advertiser its DSP creative belongs to in Epom.
  • One spot per advertiser domain and advertiser category — also passes over an advertiser that shares an Advertiser category with one already in the break, so two car brands never sit back to back. DSP bids carry no Epom advertiser category and are compared by domain only.

When nothing that fits is left, the break is simply shorter — no slot is left empty. The check runs in memory while the pod is assembled and adds no database work to ad serving. Over the REST API the setting is podSeparation on /rest-api/placements/update/video, read back by GET /rest-api/placements/{placementId}.do, and it is copied when the placement is duplicated.

Serving behind server-side ad insertion (SSAI)

On CTV most streams stitch the ad into the video on a server: a stitcher calls the VAST tag on behalf of each viewer and fires the pixels from its own data centre. Epom then reads the viewer’s IP, user-agent, language and referer from what the stitcher forwards (clientIp / clientUa tag parameters, then X-Device-IP, X-Device-User-Agent and the other device headers), and the device user-agent replaces the stitcher’s for targeting, bot detection and bid requests. Full guide, with the header order and what the creative side of the answer carries: Video behind server-side ad insertion (SSAI).

Tell Epom which stitcher calls the tag

Server-side ad insertion (SSAI) in the VAST configuration block names the service that calls the tag. Pick it and Save; the VAST tags tab then shows the tags with that vendor’s macros for the viewer’s IP and device, the app, the show and the privacy signals, and a macros table explaining each one. The list ships with IAB standard macros, Google Ad Manager DAI, AWS Elemental MediaTailor, SpringServe (Magnite), Brightcove SSAI (VOD), FreeWheel and Publica, and admins add vendors under Upstream macro presets. What each parameter carries and the per-vendor limits: Video behind server-side ad insertion → Tell Epom which stitcher calls the tag.

Pricing in the VAST answer

A stitcher or upstream ad server that resells the slot over its own auction may want to know what the slot pays. Tick Send the publisher’s price in VAST and the answer carries a <Pricing model="cpm" currency="USD"> with the publisher’s net CPM for this placement, from VAST 3.0 (a wrapper from 4.0) — see Video banners. It is off by default because a player fetches the tag in the viewer’s browser, where anyone can read the price; turn it on only for a placement whose caller needs it. A <Pricing> the demand left in its own markup is removed either way, so what the buyer paid never travels downstream.

The box is part of pricing: a role sees it with Manage Pricing enabled or read-only, and changes it only with it enabled; a save by anyone else keeps the stored value. Over the REST API it is vastPricing on /rest-api/placements/update/video (omitted keeps the current value, and a caller without the permission gets it back in ignoredFields), and duplicating the placement copies it.

Not working?

SymptomCheckWhere
The player reports no ad, or the VMAP comes back without breaksThe placement passes the ordinary checks: switched on, consent, pretargeting, at least one linked creative left after targeting, limits and cappingThe placement’s switch, Pre-targeting, Linked banners; Why my ad is not serving
No viewability in reportsThe tag was copied at 4.1 or higher from the VAST tags tab (not the classic page, not VPAID or VMAP), the player implements Open Measurement, and at least one Viewability event is wiredVAST version picker; VAST tracking card → Viewability & other
A 60-second creative serves although Max. ad duration says 30The creative is linked directly — RTB durations limit programmatic demand onlyLinked banners; the site’s video creative requirements if the file must stay off
The break holds fewer ads than Return (ads in pod)Competitive separation or the same ISCI passed candidates over, or nothing that fits was left; the break is shorter by designCompetitive separation in a pod; the advertisers’ Advertiser domain and category
Pod or VMAP edits are goneThey were not saved — the video block saves with Basic info’s SaveBasic info → Save; the unsaved-draft banner on return
No RTB configuration group in Basic infoYour role lacks Video RTB ConfigurationAsk your network admin; User roles
No VAST tracking cardYou are read-only on a placement with nothing configured (the card hides), or your role lacks Manage Placement’s VAST EventsThe share’s level; the role
A partner pixel is called twiceIt is set on both the banner’s and the placement’s VAST tracking card — pixels add upBoth cards’ Third-party pixels
Geo, device or OS targeting is wrong on CTV, or a whole stitcher got banned for fraudThe stitcher does not forward the viewer’s IP and user-agentVideo behind server-side ad insertion
A player needs a different pod for one requestAppend maxAds / maxPodDuration to the VAST tag URL for that requestOverriding the ad pod for one VAST request

Reference

Options and fields

VAST configuration (in this order on screen):

FieldRange / valuesDefaultNotes
Show skip ad buttonon/offoffUnlocks the seconds field
Show after (seconds)0–605Only when the skip button is on
Return (ads in pod)1–201>1 turns the response into an ad pod
Max. pod duration (sec)10–1800, whole numbers (arrows move by 10)no restrictionEmpty = unrestricted
Competitive separation in a podOff, One spot per advertiser domain, One spot per advertiser domain and advertiser categoryOffApplies only when the response is a pod — see above
Default ad titletext—Fallback VAST AdTitle
Server-side ad insertion (SSAI)Off, IAB standard macros, Google Ad Manager DAI, AWS Elemental MediaTailor, SpringServe (Magnite), Brightcove SSAI (VOD), FreeWheel, Publica, plus the network’s own presetsOffAdds the vendor’s viewer macros to the VAST/VMAP tags — see Video behind SSAI
Send the publisher’s price in VASTon/offoffAdds <Pricing> with the publisher’s net CPM; needs Manage Pricing — see above
Publisher video requirementsread-only—The site’s video spec, when switched on and your role can view it

VPAID, VMAP and RTB configuration:

FieldRange / valuesDefaultNotes
Show no more than (ads) (VPAID)read-only—Reflects the stored linear-break cap
Max pre-rolls (VMAP)1–102Drawn in Pre-rolls only mode; a break sequence replaces it
Break sequence (VMAP)up to 10 breaks of up to 5 adsempty1-1-1-1, 2-2-2, 3-1-1-2. Spaces, commas and semicolons work as separators too. A sequence the server cannot read is refused on save — in the console on the field, over the REST API as errors.vmapSequence before anything is written, so a refused create makes no placement
Play the last break after the content (VMAP)on / offoffDrawn with a break sequence. The sequence’s last break becomes the post-roll and keeps its own ad count — 1-5 is one ad before the content and five after it
Playback method / API frameworkmulti-selectnoneRTB signal only; needs Video RTB Configuration
Min. ad duration / Max. ad duration / Skip min (sec)seconds—RTB signal only; needs Video RTB Configuration

Ad tags & API card:

FieldRange / valuesDefaultNotes
VAST version (VAST tags tab)2.0, 3.0, 4.0, 4.1, 4.2, 4.34.2Sets the tag URL’s version; 4.1+ is required for viewability measurement. VPAID and VMAP do not follow the picker
Domain (Settings tab)one of the network’s serving domainsfirst configuredPresent whenever the network has at least one domain, and saved on the placement as soon as you pick it

A player can override Return (ads in pod) and Max. pod duration for a single break by appending maxAds / maxPodDuration to the VAST tag URL — see Overriding the ad pod for one VAST request.

Over the API

The RTB block is videoPlaybackMethod, videoApiFramework, videoAdMinDuration, videoAdMaxDuration and videoAdSkipMin on POST /rest-api/placements/update/video.do, read back by GET /rest-api/placements/{placementId}.do. Playback methods and API frameworks are named by their OpenRTB names or ids (AUTO_PLAY_SOUND_OFF or 2, VPAID_2_0 or 2), comma-separated; an empty value clears the list and leaving the parameter out keeps it. Without the Video RTB Configuration permission the call still saves the rest of the placement and lists these fields under ignoredFields as not permitted. Pod separation is podSeparation, the stitcher ssaiStitcher (a preset’s code such as SPRINGSERVE or AWS_MEDIATAILOR; GET /rest-api/upstream-macro-presets lists them) and the price box vastPricing, all on the same call; each is copied when the placement is duplicated.

Related pages

Please disable Adblock
Are you using adblock? Disable it and reload the page to proceed to the destination page.

A registration has already been submitted from this page. Please try again in 10 minutes.