VAST tracking events / Linear
exitFullscreen VAST 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.
The leave-fullscreen name lasted one version
exitFullscreen arrived in VAST 3.0 and was removed in 4.0, along with fullscreen. The replacement is playerCollapse. A 3.0 document should keep exitFullscreen. A 4.x document should use playerCollapse.
Pair it with the expand side. A tag that updates fullscreen to playerExpand and leaves exitFullscreen in place has one live URL and one dead URL on the same player. Update both.
A 3.0 player and a 4.1 document
If the document says 4.1 and a downstream player only implements 3.0, neither exitFullscreen nor playerCollapse is a safe bet. The 3.0 player calls exitFullscreen and ignores playerCollapse. The 4.1 player does the opposite. Know which player is on the placement. The version attribute is what vastlint uses. The player might implement a different set than the attribute claims, and then the event log is the authority.
The event is linear. An overlay going away is close, adCollapse, or minimize, depending on the version and the gesture. exitFullscreen never described those.
When the column stays empty
exitFullscreen was removed in VAST 4.0. A document at that version can still contain the element, and the player has no handler, so the URL is never requested. The name that replaced it is playerCollapse.
Each wrapper hop may include its own exitFullscreen URL. The player requests every one of them when the event happens, so a chain of four hops produces four calls for one playback. An http URL on an https page is dropped by the browser before the ad server sees a miss. The event name can be right and the scheme can still zero the column.
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
Put it in a Linear TrackingEvents block. It is not valid on the other creative types, and a player does not fire a tracker in the wrong container.
<Linear>
<TrackingEvents>
<Tracking event="exitFullscreen">
<![CDATA[https://track.example.com/exitFullscreen]]>
</Tracking>
</TrackingEvents>
</Linear>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.