VAST tracking events / Linear
VAST mute tracking event
Short answer: Fires when the user or player mutes ad audio.
When it fires
Ad audio was muted after playback began. Pair it with unmute. Mute is a player-state event, not a quartile, and it is valid on linear creatives across VAST 2.0 through 4.1+.
Where it is valid
| 2.0 | 3.0 | 4.0 | 4.1+ |
|---|---|---|---|
| Yes | Yes | 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="mute">
<![CDATA[https://track.example.com/mute]]>
</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
- unmute: Fires when ad audio is restored after mute.
- pause: Fires when linear playback is paused.
- resume: Fires when linear playback continues after pause.
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.