> 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/tutorials/tutorials/publishers-tutorials/compatible-vast-wrapper-players.md).

# In-Stream: Compatible VAST Wrapper Players

In-Stream ad zones can serve two types of VAST elements: **Inline** and **Wrapper**. While an Inline element is your regular Video advertisement serving a standard video file, a **Wrapper** element contains a redirection to an external VAST tag, which in turn can also serve other Inline or Wrapper elements.

The most distinctive component is the `VASTAdTagURI`, which specifies the external VAST which this ad is redirecting to:

```xml
<VAST version="3.0">
	<Ad id="6294520">
		<Wrapper>
			<AdSystem>ExoClick</AdSystem>
			<VASTAdTagURI>
				<![CDATA[ https://myotheradserver.com/xml?cid=1111111 ]]>
			</VASTAdTagURI>
			<Impression id="exotr">
				<![CDATA[ https://mytrackingsolution.com/vregister.php?a=vimp&tracking_event=impression&idzone=22222&data=abcd ]]>
			</Impression>
			<Error>
				<![CDATA[ https://mytrackingsolution.com/vregister.php?a=vview&errorcode=[ERRORCODE]&idzone=22222 ]]>
			</Error>
			<Creatives>
				<Creative sequence="1" id="90160834">
					<Linear>
						<TrackingEvents>
							<Tracking id="prog_1" event="progress" offset="00:00:10.000">
								<![CDATA[ https://mytrackingsolution.com/vregister.php?a=vview&tracking_event=progress&progress=00:00:10.000&idzone=22222&data=abcd ]]>
							</Tracking>
						</TrackingEvents>
						<VideoClicks>
							<ClickTracking>
								<![CDATA[ https://mytrackingsolution.com/click.php?d=H4sIAAAAAAAAA21T227bMAz9mrwGInV_HLAV6ZItGdY6Q18KS5ayYL7Fl6Ix9PGjk3ZtgYGGeEiaRzRJK7RCIkss_R6Gtl_wTwu8oefQLLtq6g9lfVj6piJPX.Xd0DYtQVAyD7l1vih0nrvcCxk1FgyjNLFA4YwA5bzUPnopmAMnBLO5N8ilEnlc8JuxD91tseCfIWJeKG6cA8UDiwgObKG8I3ZpmHRSBacdBIoAaKdA6pBTEoAF6e0CVRUq98LWnIrs.2qXZavdbkP6Xvumvt9nU7aH7VhWXTk0bbGWcD90p4f6bqy6Yq0y1p3c5utp03W_fo4leR5Y117gtznY1hnuc32eWObA3.HzlOF52u_Z3Rmm_QQZwBbbCgfAcRBlyeqy5eNQluM4cBBDW_ecLp3qK3n2Sr5W.fk4hiN9wvN_ghmbZrhZPdbn..Ot_fE41sR3oqKbsan6CZphoKZgBRWe6mkY0K.QBqj6Zux8uHSEa.qYkeRsgUx1nfdsIpnPT8ciNP11xKrlHxLqxs8DIpQ_E5iT.j_HdhtjH4bZwWhdrodMtEGguUJurNDpHW.SsEQpl4hs1skyUMxwkV4uSpKZlAQkTKDSvIkJSJLS2gdGGxNkRLMEZRhow5EpMCiVkkloDdxakwoBhfGFNZExh0wEaxijQPDRCNSB6Fi6UJO6GG9yKVyldx7z7w0Q18yEVDIdSVKRs_3l5.4DyauAeYMvul9W.aHvni6teAKdtusEzgkfeaTfRTJlI0TrmAbDo7cOhf8Lga0kNZUDAAA-&noredirect=1 ]]>
							</ClickTracking>
						</VideoClicks>
					</Linear>
				</Creative>
			</Creatives>
			<Extensions>
				<Extension type="waterfall" fallback_index="0">
					<Extension/></Extension>
				<Extension>
					<DSA>
						<Behalf>Company Ltd</Behalf>
						<Paid>Company Ltd</Paid>
						<WhyThisAd>The time of day. Your general location (e.g. country or region). Websites or apps you may have visited.</WhyThisAd>
						<ClickThrough>
							<![CDATA[ https://a.mytrackingsolution.com/about-this-ad.html?data=eyJhZHZlcnRpc2VyX25hbWUiOiJUZWNobml1cyBMdGQifQ%3D%3D ]]>
						</ClickThrough>
					</DSA>
				</Extension>
			</Extensions>
		</Wrapper>
	</Ad>
</VAST>
```

In order to be able to monetize your traffic with these campaigns, you must ensure that the player you are using to display ads is **Wrapper compatible**, meaning that it can get and read the content within the wrapper tag.

The players listed in [In-Stream: How to implement In-Stream Part 2 - Implementation examples](/tutorials/tutorials/publishers-tutorials/how-implement-in-stream-part2.md) are 100% VAST compatible with our ads, meaning they will also work for Wrapper VAST tags:

* [**FluidPlayer**](https://www.fluidplayer.com/)
* [**JwPlayer**](https://jwplayer.com/)
* [**VideoJs**](https://videojs.com/)
* [**FlowPlayer**](https://flowplayer.com/)
* [**Kernel Video Sharing**](https://www.kernel-video-sharing.com/en/)

If you are not using any of the players listed above, please add the following **test VAST tag** to your player in order to test the player's Wrapper compatibility:

```xml
https://s.magsrv.com/v1/vast.php?idzone=3165233
```

This VAST tag is designed to always serve a Wrapper element. If your player cannot display this element, then consider updating or changing your player. If you are unable to change your player, then make sure to **disable VAST Wrapper support** of all your In-Stream ad zones.

<figure><img src="https://3569251062-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ4RqRdVZkeXomdmwHKOL%2Fuploads%2F80y4nshAYAp8yGx1tDkB%2F0EbigZDHURJDA256K8RurtRuzHgxr7fP.png?alt=media&amp;token=a87a067e-5581-431f-aec3-eeceb2757bc1" alt=""><figcaption></figcaption></figure>

By doing this, your In-Stream ad zones will not display any Wrapper elements, thus avoiding any issues on In-Stream ad serving and making sure your traffic can be monetized.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.exoclick.com/tutorials/tutorials/publishers-tutorials/compatible-vast-wrapper-players.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
