> For the complete documentation index, see [llms.txt](https://docs.exoclick.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.exoclick.com/publishers/vast/vast-tag.md).
# VAST Tag
## XML Example
```xml
Exoclick
00:00:20.54
exoclick.com
View More
View More
Exoclick SL
Exoclick SL
The time of day. Your general location (e.g. country or region). Websites or apps you may have visited.
```
## Properties
| Option | Explanation |
| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `` | XML prolog with defined version and encoding. |
| `Ad` | Ad's root element that represents a single ad. It contains all of the information necessary for the video player to display and track the Ad creative. **Exoclick currently supports one ad per VAST response since that is a common practice.** Ad "id" attribute represents the bidding campaign id. |
| `InLine` | Element that contains all the files and URIs necessary to play and track the ad. |
| `AdSystem` | Element that contains descriptive name for the system that serves the ad, which every ad serving party must provide. |
| `AdTitle` | **Not provided.** |
| `Impression` | Element that contains impression tracking URI for the ad. Impression `id` attribute represents ad server id for the impression. |
| `Error` | Element that contains a URI that the player uses to notify the ad server when errors occur with ad playback. If the URI contains an \[ERRORCODE] macro, the video player must populate the macro with an error code. |
| `Creatives` | Container element for one or more `` element used to provide creative files for the ad. For an InLine ad, the `` element nests all the files necessary for executing and tracking the ad. |
| `Creative` | Each element contains nested elements that describe the type of ad being served using nested sub-elements for `Linear` or `NonLinear` Ads. Exoclick provides only one `` element per VAST response. Creative `sequence` attribute represents sequence, so for a single creative value, the "sequence" will be 1. Exoclick Creative `id` attribute represents winning creative id. |
| `Linear` | Sets the video-formatted ads that play linearly within the streaming content, meaning before the streaming content, during a break, or after the streaming content. A Linear creative has to contain at minimum, `` element to communicate the intended runtime and a `` element used to provide the needed video files for ad execution. Exoclick also provides `TrackingEvents`, `VideoClicks` and `Icons` (optional). Linear `skipoffset` attribute identifies when skip controls are made available to the end user. |
| `Duration` | Element to denote the intended playback duration for the Linear component of the ad. Time value may is in the format `HH:MM:SS`. |
| `MediaFiles` | Container element for one or more `` elements, each of which contains a `CDATA` wrapped URI to the media file to be downloaded or streamed for the Linear creative. Linear creative are typically video files, but static images may also be used. Exoclick supports only a single `MediaFile` and no cross device or different bitrate MediaFile are supported. |
| `MediaFile` | Element contains URI to media file being served. MediaFile `delivery` attribute - either `progressive` for progressive download protocols (such as HTTP) or `streaming` for streaming protocols. MediaFile `type` attribute - MIME type for the file container, such as `video/mp4` for MP4. |
| `VideoClicks` | Element which is used to specify what the video player should do if the user clicks directly within the video player frame while the ad is being displayed. When a `` element is provided, it contains a single child `` element with URI (or `` in case of Wrapper). |
| `ClickThrough` | Is a click URI that redirects to the advertiser's site when the Ad viewer clicks the ad. The `clickthrough` is only available in the `InLine` format and is used when the linear ad unit cannot handle a clickthrough. |
| `TrackingEvents` | Element used to send tracking information back to the ad server. The `` element may contain one or more `` elements. An event attribute for the `` element enables ad server to include individual tracking URIs for events they want to track. Tracking "event" attribute - Exoclick is prepared for `impression`, `progress`, `complete`, but in most cases only `progress` is returned. Tracking `offset` attribute - when the progress of the linear creative has matched the value specified, the included URI is triggered. If the duration is not known when the offset is set to a percentage value, the progress event may be ignored. |
| `Icons` | Used for posting an icon with the linear ad. Exoclick provides only a single Icon under Icons. It can be disabled by setting `imp.ext.icons_support = 0` in the RTB request. |
| `Icon` | Element containing `` element. |
| `IconCLicks` | Element used to load an informational page in a new window as well as track when users clicks in the ad. |
| `IconClickThrough` | Element contains URI to the information page. The video player must load this page in a new window when the user clicks the icon. |
| `Extensions` | Element used for custom extensions, defined by the ad server. It must contain `` element. |
| `Extension` | Element use for each custom feature |
| `TitleCTA` | Custom element to support CTA, it has following elements: ``, ``, ``, ``. |
| `MobileText/PCText` | Elements contains CTA text such as `View More` or `Subscribe Now`. |
| `DisplayUrl` | Optional friendly domain. |
| `Tracking` | Click tracking URI. On Exoclick it can be disabled by setting sending `imp.ext.video_cta = 0` in the RTB request. |
| `DSA` | Custom element to support DSA, it has following elements: ``, ``, ``, ``. The [Digital Service Act](/exoclick-docs/dsa.md) disclaimer. |
| `Behalf` and `Paid` | The name of the advertiser who paid for this ad |
| `Why this ad` | The specific user information that was collected |
| `Clickthrough` | Additional information related to [DSA](/exoclick-docs/dsa.md) |
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.exoclick.com/publishers/vast/vast-tag.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.