VAST tracking events / Linear
VAST playerCollapse tracking event
Short answer: Fires when the player leaves the expanded surface (4.0+). Introduced in VAST 4.0.
When it fires
The player left the expanded or fullscreen surface. Pair with playerExpand. This is player chrome, not the creative collapsing (adCollapse).
Where it is valid
| 2.0 | 3.0 | 4.0 | 4.1+ |
|---|---|---|---|
| No | No | Yes | 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="playerCollapse">
<![CDATA[https://track.example.com/playerCollapse]]>
</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
- playerExpand: Fires when the player grows (4.0+ replacement for fullscreen).
- exitFullscreen: Removed in VAST 4.0. Use playerCollapse on 4.x tags.
- adCollapse: Fires when the creative collapses after expand. 4.0+ name.
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.