VAST tracking events / Linear
resume VAST tracking event
Short answer: Fires when linear playback continues after pause.
When it fires
Playback restarted after pause. A resume with no matching pause is a player bug, not a tag bug.
Resume continues a pause
resume fires when linear playback continues after pause. A resume count higher than pause means the player emitted resume without a pause, which is a player bug. A pause count higher than resume means viewers left while paused, or the resume URL is missing from the tag while pause is present.
Ship them as a pair on Linear. The names have been stable since VAST 2.0. resume is not the signal that a pause ad finished. That overlay uses creativeView and overlayViewDuration.
The beacon after a long pause
Some players treat a long pause as the end of the ad and never fire resume, even if the viewer continues. complete may then be missing too. The tag still listed resume. The player ended the session. That shows up as pause with no resume and no complete, which is the same shape as the viewer leaving. The event log's timestamps tell those apart. The XML does not.
resume on a wrapper fires in addition to resume on the InLine. Two resume calls for one continue are the chain, not two continues. Divide by the number of hops that carry the event before you compare resume to pause.
When the column stays empty
resume is in the VAST 2.0 set, and the current version still includes it. An empty column on a current player is not a version mismatch.
Each wrapper hop may include its own resume URL. The player requests every one of them when the event happens, so a chain of four hops produces four calls for one playback. An http URL on an https page is dropped by the browser before the ad server sees a miss. The event name can be right and the scheme can still zero the column.
Where it is valid
| 2.0 | 3.0 | 4.0 | 4.1+ |
|---|---|---|---|
| Yes | Yes | Yes | Yes |
Legal containers: Linear. An event in the wrong container is not a player error. It is a URL nobody calls.
Using it in a tag
Put it in a Linear TrackingEvents block. It is not valid on the other creative types, and a player does not fire a tracker in the wrong container.
<Linear>
<TrackingEvents>
<Tracking event="resume">
<![CDATA[https://track.example.com/resume]]>
</Tracking>
</TrackingEvents>
</Linear>VAST XML fragment only. This excerpt belongs inside a complete VAST document, so standalone validation will fail until it is wrapped in a full <VAST>response.
Related vastlint rules
- VAST-4.1-tracking-event-value: Tracking event attribute not in the valid set for this VAST version
Related events
- pause: Fires when linear playback is paused.
- start: Fires when linear playback actually begins, first frame rendered.
Check the XML, then confirm the beacons fire
Validate the event names and containers on the document. Test a live URL when the XML is clean and reporting is still empty.