VAST tracking events / NonLinear
VAST minimize tracking event
Short answer: Fires when a NonLinear creative is minimized. VAST 4.0+. Introduced in VAST 4.0.
When it fires
The overlay was minimized rather than closed. Distinct from adCollapse and close. Pause ads and other CTV portfolio formats often need this plus creativeView.
Where it is valid
| 2.0 | 3.0 | 4.0 | 4.1+ |
|---|---|---|---|
| No | No | 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="minimize">
<![CDATA[https://track.example.com/minimize]]>
</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
- close: Fires when a NonLinear creative is closed by the user.
- adCollapse: Fires when the creative collapses after expand. 4.0+ name.
- 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.