VASTlint

VAST tracking events / Linear

VAST fullscreen tracking event

Short answer: Removed in VAST 4.0. Use playerExpand on 4.x tags. Removed in VAST 4.0.

Replacement: use playerExpand on VAST 4.0 and later. A 4.x player that sees fullscreen has no handler for it.

When it fires

Old name for the player entering a larger playback surface. VAST 4.0 replaced it with playerExpand because fullscreen described a browser state that does not exist on a television. Ad servers still emit fullscreen on 4.1 documents when the template was never updated.

Where it is valid

2.03.04.04.1+
YesYesRemovedRemoved

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="fullscreen">
    <![CDATA[https://track.example.com/fullscreen]]>
  </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

Related events

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.

Further reading