VAST tracking events / Linear

VAST progress tracking event

Short answer: Fires at a declared offset. The only tracking event that takes a parameter. Introduced in VAST 3.0.

When it fires

Playback reached the offset attribute. Offset must be HH:MM:SS or n%. A bare number of seconds is invalid. An offset past Duration can never fire, which looks like a dead tracker.

Where it is valid

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

<TrackingEvents>
  <Tracking event="progress" offset="00:00:15">
    <![CDATA[https://track.example.com/progress]]>
  </Tracking>
</TrackingEvents>

<TrackingEvents>
  <Tracking event="progress" offset="00:00:15">
    <![CDATA[https://track.example.com/progress]]>
  </Tracking>
</TrackingEvents>

Related vastlint rules

• VAST-3.0-progress-offset: <Tracking event="progress"> requires an offset attribute
• VAST-3.0-progress-offset-format: Tracking progress offset does not match required format
• VAST-4.1-tracking-event-value: Tracking event attribute not in the valid set for this VAST version

Related events

• start: Fires when linear playback actually begins, first frame rendered.
• firstQuartile: Fires when linear playback reaches 25 percent of Duration.
• complete: Fires when linear playback reaches the end of Duration.

Further reading

• All VAST tracking events
• VAST macros inside tracking URLs
• VAST error codes