VAST tracking events / Linear, NonLinear, Companion
VAST creativeView tracking event
Short answer: Fires when the creative is first displayed. Primary signal for NonLinear and companions.
When it fires
The player has rendered the creative for the first time. On linear ads this often duplicates the Impression. On NonLinear overlays and companions it is the main exposure signal, because those formats have no quartile timeline.
Where it is valid
| 2.0 | 3.0 | 4.0 | 4.1+ |
|---|---|---|---|
| Yes | Yes | Yes | Yes |
Legal containers: Linear, NonLinear, Companion. 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="creativeView">
<![CDATA[https://track.example.com/creativeView]]>
</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.
- loaded: Fires when the player has the media file and is ready. VAST 4.1+.
- overlayViewDuration: Fires with how long a NonLinear overlay was in view. VAST 4.0+.
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.