VAST tracking events / NonLinear
VAST otherAdInteraction tracking event
Short answer: Catch-all NonLinear interaction that is not expand, collapse, or close. Introduced in VAST 4.0.
When it fires
The user interacted in a way the named events do not cover. Use it as a last resort, not as a substitute for acceptInvitation or adExpand.
Where it is valid
| 2.0 | 3.0 | 4.0 | 4.1+ |
|---|---|---|---|
| No | No | Yes | Yes |
Legal containers: NonLinear. 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="otherAdInteraction">
<![CDATA[https://track.example.com/otherAdInteraction]]>
</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
- acceptInvitation: Fires when the user accepts a NonLinear invitation (expands or engages).
- adExpand: Fires when the creative expands. 4.0+ name replacing expand.
- close: Fires when a NonLinear creative is closed by the user.
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.