Volume navigation
VMAP tracking
ElementOn this page
Position
Break-level tracking: the breakStart / breakEnd / error events; same names as VAST tracking but a different specification, so a namespace must distinguish them.
- Spec section
- §2.3.3
- Parent
- AdBreak
- Cardinality
- 0..1（Tracking 0..n）
- Tracking events
- breakStart · breakEnd · error
Attributes and values
| Attribute | Type | Required | Values | Notes |
|---|---|---|---|---|
| Tracking/@event | NMTOKEN | Yes | breakStart | breakEnd | error | Name of the VMAP break-level event being tracked |
Children and structure
- Tracking0..nA single tracking URI, text of type anyURI, should be in CDATA
XML snippet
<TrackingEvents> <Tracking event="breakStart"><![CDATA[http://adserver.com/breakstart.gif]]></Tracking> </TrackingEvents>
Player behaviour
- 1When the event occurs the player must request the corresponding Tracking URI; with several Tracking elements for one event, all must be requested
- 2A break with tracking but no AdSource keeps valid tracking: the resources must still be requested
- 3VMAP's TrackingEvents/Tracking are intentionally named like VAST's but belong to a different specification and track different events, so a namespace must distinguish them
Invalid forms
- A Tracking without the event attribute (required)
- An event value outside the three events
- A tracking URI not wrapped in CDATA (per the spec's example and requirement)