VAST tracking events / NonLinear
collapse VAST tracking event
Short answer: Removed in VAST 4.0. Use adCollapse on 4.x tags. Removed in VAST 4.0.
Replacement: use adCollapse on VAST 4.0 and later. A 4.x player that sees collapse has no handler for it.
When it fires
Old name for the creative collapsing after expand. Replaced by adCollapse in VAST 4.0.
collapse left with expand
collapse fired when the creative returned from the expanded state. VAST 4.0 replaced it with adCollapse. A 2.0 or 3.0 document keeps collapse. A 4.x document uses adCollapse.
close is dismissal of the overlay. collapse was the creative shrinking and staying available. Filing a 4.x adCollapse under the old collapse name in a downstream report is a label change you have to do yourself. The player will not emit the old name.
Which shrink you are counting
On VAST 2.0 and 3.0, collapse is the creative shrinking. There is no minimize yet, so a player may emit collapse for a gesture that a 4.x player would call minimize. The numbers will not line up across a version bump unless you map the names. The mapping is collapse to adCollapse, and some of those rows to minimize, and you cannot split them after the fact from the old URL alone.
A 4.1 tag that keeps collapse alongside adCollapse gets a call on adCollapse only. The old URL stays dark. Delete it or stop waiting on it. Leaving it in the file does not fail validation by itself if the checker is only looking at names it knows as removed. vastlint reports the removed name and points at the replacement.
When the column stays empty
collapse 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 adCollapse.
Each wrapper hop may include its own collapse 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+ |
|---|---|---|---|
| Yes | Yes | Removed | Removed |
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
Put it in a NonLinear TrackingEvents block. It is not valid on the other creative types, and a player does not fire a tracker in the wrong container.
<NonLinear>
<TrackingEvents>
<Tracking event="collapse">
<![CDATA[https://track.example.com/collapse]]>
</Tracking>
</TrackingEvents>
</NonLinear>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
- adCollapse: Fires when the creative collapses after expand. 4.0+ name.
- expand: Removed in VAST 4.0. Use adExpand on 4.x tags.
- adExpand: Fires when the creative expands. 4.0+ name replacing expand.
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.