Understanding VAST feeds and ad server SDKs
Overview
This article explains the difference between VAST feeds and ad server SDK integrations for video advertising.
It also covers why VAST feeds are often the recommended starting point when testing a new ad partner or planning an ad monetization setup.
When to use VAST feeds instead of an SDK
Use VAST feeds when you want a simpler, more flexible way to serve video ads from one or more ad networks.
VAST feeds are often a good fit when you want to:
Test a new ad partner before committing to custom development
Use multiple ad networks in a Waterfall/Fallback Campaign
Keep your ad setup more vendor-independent
Reduce custom development, maintenance, and project time
Support common video ad delivery across web players, apps, and OTT platforms
Improve fill rate and revenue opportunities with minimal custom development
An SDK integration may be worth considering only when the vendor-specific features provide enough value to justify the added development, cost, testing, and long-term maintenance.
Contact Customer Support if you would like to request a VAST feed integration or discuss whether an SDK integration is possible for your setup.
How it works
VAST feeds
A VAST feed is a standard ad tag that plugs into the existing video player or playout system. VAST feeds can be used to request and serve video ads without adding a third-party software development kit to each website or app.
VAST feeds can also be used in a multi-source Waterfall/Fallback Campaign. This allows multiple ad networks or ad sources to be tried in a priority order, which can help improve fill opportunities and revenue potential.
Because VAST feeds are widely used and do not usually require the same level of custom development as an SDK, they are often the safest way to test a new ad partner first. The ad partner can demonstrate fill rates, CPMs, and payout reliability before you invest in a more complex integration.
Ad server SDKs
An SDK integration adds a third-party software development kit to your website or apps. The SDK may handle ad serving, additional tracking, banner ad placement, user interaction, stream personalization, user data collection, or other vendor-specific features.
SDK integrations usually require custom development, testing, and ongoing maintenance. They may also increase project cost and timeline.
An SDK can also tie your ad setup more closely to one ad-tech vendor. This can reduce flexibility if you later want to switch providers, add other ad networks, or use multiple ad sources in a Waterfall/Fallback Campaign.
Before considering an SDK integration, confirm that the added features justify the cost, technical complexity, testing, and ongoing maintenance.
OTT and Smart TV considerations
Many third-party SDKs may not work well on Smart TVs, Roku, Fire TV, Apple TV, and other OTT devices because each platform has its own technical requirements and restrictions.
VAST feeds are usually more flexible for OTT and multi-platform delivery because they can work with the existing video player or ad setup without requiring a separate SDK integration for each platform.
Many Lightcast customers monetize video content using multiple VAST feeds in a Waterfall/Fallback Campaign. This approach helps keep costs lower, supports a more flexible ad strategy, and reduces the risk of being locked into one ad-tech vendor.
FAQs
What is the difference between a VAST feed and an SDK integration?
A VAST feed is a standard ad tag used by the video player or ad setup to request video ads.
An SDK integration adds third-party software to a website or app and usually requires custom development, testing, and ongoing maintenance.
Why does Lightcast usually recommend VAST feeds first?
VAST feeds are widely supported, easier to test, and more flexible for using multiple ad networks.
They also allow a new ad partner to demonstrate fill rates, CPMs, and payout reliability before you invest in a more complex SDK integration.
Are SDK integrations recommended for Smart TVs and OTT devices?
Not usually. Many OTT platforms have technical requirements or restrictions that can make third-party SDK integrations difficult or unsupported.
VAST feeds are usually more flexible for Smart TVs, Roku, Fire TV, Apple TV, and other OTT devices.
How should a new ad partner be tested?
Start with the ad partner’s VAST feed first.
Review fill rates, CPMs, reporting, and payout reliability before considering a custom SDK integration.
Can VAST feeds support multiple ad networks?
Yes. VAST feeds can be used in a Waterfall/Fallback Campaign so multiple ad networks or ad sources can be tried in priority order.
When would an SDK integration make sense?
An SDK integration may make sense if the ad partner offers specific features that are not available through VAST feeds and those features justify the added development, cost, testing, and long-term maintenance.
How can a VAST feed or SDK integration be requested?
Contact Customer Support if you would like to request a VAST feed integration or discuss whether an SDK integration is possible for your setup.
