VAST tracking events / NonLinear
VAST close tracking event
Short answer: Fires when a NonLinear creative is closed by the user.
When it fires
The overlay or companion was dismissed. This is a NonLinear event. Linear close moved to closeLinear in later versions. Putting close on a Linear creative is the wrong container.
Where it is valid
| 2.0 | 3.0 | 4.0 | 4.1+ |
|---|---|---|---|
| Yes | Yes | Yes | Yes |
Legal containers: NonLinear. 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="close">
<![CDATA[https://track.example.com/close]]>
</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
- closeLinear: Fires when a linear ad is closed. 4.1+ replacement path for linear close.
- acceptInvitation: Fires when the user accepts a NonLinear invitation (expands or engages).
- 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.