VAST tracking events / Linear
VAST skip tracking event
Short answer: Fires when the user skips a linear ad. Requires skipoffset on Linear. Introduced in VAST 3.0.
When it fires
The skip control was used. Introduced in VAST 3.0. If the tag tracks skip but Linear has no skipoffset, the button never appears and the event never fires. That looks identical in reporting to a tracker that failed.
Where it is valid
| 2.0 | 3.0 | 4.0 | 4.1+ |
|---|---|---|---|
| No | 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
<TrackingEvents>
<Tracking event="skip">
<![CDATA[https://track.example.com/skip]]>
</Tracking>
</TrackingEvents>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-3.0-skip-event-no-skipoffset: skip tracking event present but Linear has no skipoffset attribute
- VAST-3.0-skipoffset-format: Linear skipoffset does not match HH:MM:SS[.mmm] or n% format
- VAST-4.1-tracking-event-value: Tracking event attribute not in the valid set for this VAST version
Related events
- complete: Fires when linear playback reaches the end of Duration.
- closeLinear: Fires when a linear ad is closed. 4.1+ replacement path for linear close.
- progress: Fires at a declared offset. The only tracking event that takes a parameter.
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.