Does The Trade Desk support VPAID?

For new campaigns, treat VPAID as unsupported. The Trade Desk blocks VPAID on CTV and OTT inventory, and even on web inventory native MP4 plus OMID is the safer path. If a VAST tag includes apiFramework=VPAID, validate it before launch and remove it for CTV delivery.

Why does The Trade Desk require UniversalAdId?

UniversalAdId is the VAST 4.x identifier used for creative identity across systems. For The Trade Desk workflows it is a strong best practice because it improves cross-screen deduplication, reporting, and frequency management, especially for CTV campaigns.

What usually breaks a The Trade Desk video creative?

The most common failures are VPAID on CTV inventory, HTTP URLs, wrapper chains that are too deep for the downstream player, bad Duration values, and missing or unusable MP4 MediaFiles. These are exactly the issues to check before the creative goes live.

The Trade Desk VAST validator guide

Q: How do I validate a The Trade Desk VAST tag?

Use vastlint as a The Trade Desk VAST validator. If you already have the resolved VAST XML, paste it into the validator. If you only have a live tag URL or wrapper chain, use the tester first to fetch the response, inspect redirects, and then review the validation report.

The Trade Desk (TTD) is the largest independent demand-side platform (DSP). When you buy programmatic video through TTD, your creative still has to arrive as a player-safe VAST tag. If you need a The Trade Desk VAST validator, this page is the fast path: validate the XML, catch CTV-incompatible VPAID, keep wrapper depth under control, and confirm the media files and URLs are safe before launch.

The TTD-specific details in this guide come from public OpenTTD and UID2 material, IAB Tech Lab VAST references, and The Trade Desk partner documentation where some creative workflow details are account-gated.

Need a The Trade Desk VAST validator?

Paste resolved VAST XML into the validator for a rule-by-rule report. If you only have a live TTD tag URL or a wrapper, use the tester first to fetch the response, inspect the redirect chain, and then validate the XML.

Validate a The Trade Desk VAST tag →Test a live TTD tag URL →

Quick reference

Role	Demand-side platform (DSP)
Best-practice VAST range	2.0–4.x; prefer VAST 4.x when you need UniversalAdId and AdVerifications
VPAID	Avoid for new campaigns; blocked on CTV and OTT
Wrapper depth	Keep downstream wrappers shallow; publisher players often cap total depth at 4–5
UniversalAdId	Strong best practice for VAST 4.x, especially on CTV
Media format	MP4 H.264 baseline; provide multiple bitrates when possible
HTTPS	Required for all URLs

How to validate a The Trade Desk VAST tag

There are two common starting points. If you already have the resolved XML that will reach the player, paste it straight into the validator. If you only have a live tag URL or wrapper endpoint, use the testerfirst so you can inspect wrapper hops, tracking vendors, and the final XML before you run the full rule set.

That workflow matters for TTD because many delivery failures are not obvious from the bid or trafficking UI: extra wrappers, CTV-unsafe VPAID, HTTP tracking pixels, or MediaFiles that do not match the player environment all show up more clearly once you look at the resolved VAST response.

VPAID and CTV

For practical TTD delivery, treat VPAID as a legacy format. TTD programmatic video needs to work across publisher environments where VPAID is blocked or degraded, especially on connected TV. For new campaigns, native video plus OMID is the safer baseline.

→ vastlint rule: VAST-4.1-vpaid-in-interactive-context

UniversalAdId and VAST 4.x

If you are sending VAST 4.x markup, include a <UniversalAdId> whenever you can. It gives the creative a stable identity across systems and is particularly useful in TTD workflows where cross-screen reporting, deduplication, and frequency management all benefit from a consistent ad identifier.

<VAST version="4.0">
  <Ad id="1">
    <InLine>
      <AdSystem>My DSP Creative Server</AdSystem>
      <AdTitle>Brand Campaign 30s</AdTitle>
      <Impression><![CDATA[https://track.example.com/imp]]></Impression>
      <Creatives>
        <Creative>
          <UniversalAdId idRegistry="ad-id.org">8465903</UniversalAdId>
          <Linear>
            <Duration>00:00:30</Duration>
            <TrackingEvents>
              <Tracking event="start"><![CDATA[https://track.example.com/start]]></Tracking>
              <Tracking event="firstQuartile"><![CDATA[https://track.example.com/firstQuartile]]></Tracking>
              <Tracking event="midpoint"><![CDATA[https://track.example.com/midpoint]]></Tracking>
              <Tracking event="thirdQuartile"><![CDATA[https://track.example.com/thirdQuartile]]></Tracking>
              <Tracking event="complete"><![CDATA[https://track.example.com/complete]]></Tracking>
            </TrackingEvents>
            <MediaFiles>
              <MediaFile type="video/mp4" width="1920" height="1080"
                         bitrate="5000" delivery="progressive">
                <![CDATA[https://cdn.example.com/ad.mp4]]>
              </MediaFile>
            </MediaFiles>
          </Linear>
        </Creative>
      </Creatives>
    </InLine>
  </Ad>
</VAST>

<VAST version="4.0">
  <Ad id="1">
    <InLine>
      <AdSystem>My DSP Creative Server</AdSystem>
      <AdTitle>Brand Campaign 30s</AdTitle>
      <Impression><![CDATA[https://track.example.com/imp]]></Impression>
      <Creatives>
        <Creative>
          <UniversalAdId idRegistry="ad-id.org">8465903</UniversalAdId>
          <Linear>
            <Duration>00:00:30</Duration>
            <TrackingEvents>
              <Tracking event="start"><![CDATA[https://track.example.com/start]]></Tracking>
              <Tracking event="firstQuartile"><![CDATA[https://track.example.com/firstQuartile]]></Tracking>
              <Tracking event="midpoint"><![CDATA[https://track.example.com/midpoint]]></Tracking>
              <Tracking event="thirdQuartile"><![CDATA[https://track.example.com/thirdQuartile]]></Tracking>
              <Tracking event="complete"><![CDATA[https://track.example.com/complete]]></Tracking>
            </TrackingEvents>
            <MediaFiles>
              <MediaFile type="video/mp4" width="1920" height="1080"
                         bitrate="5000" delivery="progressive">
                <![CDATA[https://cdn.example.com/ad.mp4]]>
              </MediaFile>
            </MediaFiles>
          </Linear>
        </Creative>
      </Creatives>
    </InLine>
  </Ad>
</VAST>

HTTPS and media requirements

All URLs should be HTTPS: the VAST tag URL, media file URLs, impression pixels, click-through URLs, and tracking events. Mixed-content and insecure asset failures are still one of the easiest ways to lose delivery on premium inventory.

Provide MP4 H.264 as the baseline format. If the same creative can land across web, in-app, and CTV environments, multiple bitrates improve the chance that the downstream player can choose a compatible file without buffering or transcoding surprises.

<MediaFiles>
  <MediaFile type="video/mp4" width="1920" height="1080"
             bitrate="5000" delivery="progressive">
    <![CDATA[https://cdn.example.com/ad-1080p.mp4]]>
  </MediaFile>
  <MediaFile type="video/mp4" width="1280" height="720"
             bitrate="2000" delivery="progressive">
    <![CDATA[https://cdn.example.com/ad-720p.mp4]]>
  </MediaFile>
</MediaFiles>

<MediaFiles>
  <MediaFile type="video/mp4" width="1920" height="1080"
             bitrate="5000" delivery="progressive">
    <![CDATA[https://cdn.example.com/ad-1080p.mp4]]>
  </MediaFile>
  <MediaFile type="video/mp4" width="1280" height="720"
             bitrate="2000" delivery="progressive">
    <![CDATA[https://cdn.example.com/ad-720p.mp4]]>
  </MediaFile>
</MediaFiles>

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.

Wrapper chains

TTD creatives still have to survive the publisher player's wrapper limit. Even when TTD itself is not the only wrapper in the path, every additional redirect increases the odds of timeout or chain exhaustion. As a working rule, keep the chain shallow and inspect the live response before launch if the creative involves multiple vendors.

OMID measurement

If you need viewability or verification, prefer OMID-style <Verification>blocks over VPAID. Execution still depends on the downstream player environment, but OMID is the standards-friendly route and lines up with where the IAB ecosystem has moved.

<AdVerifications>
  <Verification vendor="moat.com-omid">
    <JavaScriptResource apiFramework="omid" browserOptional="true">
      <![CDATA[https://z.moatads.com/tradedeskintegration123/moatvideo.js]]>
    </JavaScriptResource>
  </Verification>
</AdVerifications>

<AdVerifications>
  <Verification vendor="moat.com-omid">
    <JavaScriptResource apiFramework="omid" browserOptional="true">
      <![CDATA[https://z.moatads.com/tradedeskintegration123/moatvideo.js]]>
    </JavaScriptResource>
  </Verification>
</AdVerifications>

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.

Duration and timing

<Duration> must be in HH:MM:SS format. TTD's creative review and downstream players both rely on that value being correct. Bad duration fields are easy to miss in trafficking and easy to catch in validation.

→ vastlint rule: VAST-2.0-duration-format

Pre-flight checklist for The Trade Desk

No VPAID for CTV delivery; use native MP4 and OMID where measurement is needed
All URLs use HTTPS
Wrapper chain stays shallow enough for the downstream player
MP4 H.264 media files are present and usable
<Duration> in HH:MM:SS format
<Impression> with HTTPS URL present
<UniversalAdId> included for VAST 4.x creatives when possible
<AdVerifications> with OMID script for viewability
version attribute on root <VAST> element

References

Validate your The Trade Desk VAST tag →