VAST tracking events / NonLinear
VAST acceptInvitation tracking event
Short answer: Fires when the user accepts a NonLinear invitation (expands or engages).
When it fires
The user opted into the overlay. Linear had a parallel name, acceptInvitationLinear, which did not survive cleanly into 4.1. Use this name on NonLinear only.
Where it is valid
| 2.0 | 3.0 | 4.0 | 4.1+ |
|---|---|---|---|
| Yes | Yes | 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="acceptInvitation">
<![CDATA[https://track.example.com/acceptInvitation]]>
</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
- acceptInvitationLinear: Linear invitation accept. Present in 3.0 and 4.0; gone as a 4.1 linear name.
- 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.