VAST tracking events / Linear
VAST loaded tracking event
Short answer: Fires when the player has the media file and is ready. VAST 4.1+. Introduced in VAST 4.1.
When it fires
The asset is ready; playback has not begun. This is delivery, not exposure. A gap from loaded to start is the user leaving or autoplay being blocked. Do not treat loaded as an impression.
Where it is valid
| 2.0 | 3.0 | 4.0 | 4.1+ |
|---|---|---|---|
| No | No | No | 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="loaded">
<![CDATA[https://track.example.com/loaded]]>
</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-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.
- creativeView: Fires when the creative is first displayed. Primary signal for NonLinear and companions.
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.