VAST tracking events / Linear
VAST exitFullscreen tracking event
Short answer: Removed in VAST 4.0. Use playerCollapse on 4.x tags. Introduced in VAST 3.0. Removed in VAST 4.0.
Replacement: use playerCollapse on VAST 4.0 and later. A 4.x player that sees exitFullscreen has no handler for it.
When it fires
Old name for leaving fullscreen. Introduced in VAST 3.0, removed in 4.0. Pair the replacement playerCollapse with playerExpand.
Where it is valid
| 2.0 | 3.0 | 4.0 | 4.1+ |
|---|---|---|---|
| No | Yes | Removed | Removed |
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="exitFullscreen">
<![CDATA[https://track.example.com/exitFullscreen]]>
</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.0-tracking-event-removed: fullscreen/exitFullscreen tracking events were removed in VAST 4.0
- VAST-4.1-tracking-event-value: Tracking event attribute not in the valid set for this VAST version
Related events
- playerCollapse: Fires when the player leaves the expanded surface (4.0+).
- fullscreen: Removed in VAST 4.0. Use playerExpand on 4.x tags.
- playerExpand: Fires when the player grows (4.0+ replacement for fullscreen).
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.