Skip to content

VAST Tag Types ​

Infillion uses two types of VAST tags for both TrueX and Interactive Video products. The tags differ in how the adParameters JSON payload is embedded in the VAST XML.

"Generic" Tag ​

The adParameters are embedded directly as a JSON string within the <AdParameters> node:

TrueX "Generic" Tag:

https://get.truex.com/{placement_hash}/vast/generic?{ad_request_parameters}

Interactive Video "Generic" Tag:

https://get.truex.com/{placement_hash}/vast/idvx/generic?{ad_request_parameters}

VAST Structure:

xml
<VAST version="4.0">
  <Ad id="...">
    <InLine>
      <AdSystem>trueX</AdSystem> <!-- or "IDVx" for IDVx ads -->
      <Creatives>
        <Creative>
          <Linear>
            <Duration>00:00:30</Duration>
            <AdParameters>
              <![CDATA[ { ...ad_parameters_json_string... } ]]>
            </AdParameters>
            <MediaFiles>
              <MediaFile delivery="progressive" type="video/mp4" width="1280" height="720" apiFramework="truex">
                <![CDATA[https://qa-media.truex.com/m/video/truexloadingplaceholder-30s.mp4 ]]>
              </MediaFile>
            </MediaFiles>
          </Linear>
        </Creative>
      </Creatives>
    </InLine>
  </Ad>
</VAST>

"Companion" Tag ​

The adParameters are embedded in a companion ad's <StaticResource> node as base64-encoded json string:

TrueX "Companion" Tag:

https://get.truex.com/{placement_hash}/vast/companion?{ad_request_parameters}

IDVx "Companion" Tag:

https://get.truex.com/{placement_hash}/vast/idvx/companion?{ad_request_parameters}

VAST Structure:

xml
<VAST version="4.0">
  <Ad id="...">
    <InLine>
      <AdSystem>trueX</AdSystem> <!-- or "IDVx" for IDVx ads -->
      <Creatives>
        <Creative>
          <CompanionAds>
            <Companion id="super_tag" width="960" height="540" apiFramework="truex">
              <StaticResource creativeType="application/json">
                <![CDATA[ ...base64_encoded_json_string... ]]>
              </StaticResource>
            </Companion>
          </CompanionAds>
        </Creative>
        <Creative>
          <Linear>
            <Duration>00:00:30</Duration>
            <MediaFiles>
              <MediaFile delivery="progressive" type="video/mp4" width="1280" height="720">
                <![CDATA[https://qa-media.truex.com/m/video/truexloadingplaceholder-30s.mp4 ]]>
              </MediaFile>
            </MediaFiles>
          </Linear>
        </Creative>
      </Creatives>
    </InLine>
  </Ad>
</VAST>

Differentiating TrueX and IDVx ​

The <AdSystem> node value identifies the ad type:

  • TrueX ads: <AdSystem>trueX</AdSystem>
  • IDVx ads: <AdSystem>IDVx</AdSystem>

Both tag types (Generic and Companion) work with both TrueX and IDVx products.

VPAID Tag ​

The VPAID integration uses a third tag format. The generic and companion tags carry the adParameters JSON for the TrueX Ad Renderer. The VPAID tag points your client-side ad manager at Infillion's VPAID unit instead, and the unit loads everything else on its own. It works for both TrueX and IDVx.

The tag is a VAST response with one linear creative. The <MediaFile> is a JavaScript file with apiFramework="VPAID", and the <AdParameters> node holds a small JSON payload that the unit reads:

https://get.truex.com/{placement_hash}/vast
xml
<?xml version="1.0" encoding="UTF-8"?>
<VAST version="2.0">
  <Ad id="super_tag">
    <InLine>
      <AdSystem>trueX</AdSystem> <!-- or "IDVx" for IDVx ads -->
      <AdTitle><![CDATA[VAST Super Tag]]></AdTitle>
      <Impression></Impression>
      <Creatives>
        <Creative id="super_tag">
          <Linear>
            <Duration>00:00:30</Duration>
            <AdParameters><![CDATA[{"user_id":"...","placement_hash":"..."}]]></AdParameters>
            <MediaFiles>
              <MediaFile delivery="progressive"
                         type="application/javascript"
                         width="750"
                         height="500"
                         apiFramework="VPAID">
                <![CDATA[https://media.truex.com/integration/vpaid/mobile_vpaid.js]]>
              </MediaFile>
            </MediaFiles>
          </Linear>
        </Creative>
      </Creatives>
    </InLine>
  </Ad>
</VAST>

Pass the tag to your ad manager as-is.

Flighting ​

Infillion ads are flighted in the ad pod by the tag's position. TrueX is offered in the first slot of a pod, so that a user who completes it can skip the rest of the pod. IDVx can be in any slot of the pod, and never skips ads.

GoalWhere to put the TrueX tag
Mid-roll replacementThe first slot of each mid-roll pod you want to replace. Pre-roll and the other mid-rolls are unaffected
Full-stream replacementThe first slot of the pre-roll pod, and of every mid-roll pod after it
Both on the same placementSame as full-stream replacement

In full-stream replacement, a user who opts into the pre-roll unit and completes it skips the video ads in the later pods. The TrueX tags in those pods are still played - they skip the ads, and may show a "skip card" to the user. The unit then fires AdFreePod followed by AdStopped, and the user goes back to the content.

Integration documentation for Infillion Ads