VAST feed compatibility and macros explained

Edited

Overview

This article explains how VAST feed compatibility and macros work across Lightcast-supported publishing platforms.

It also covers why simple VAST Tags with supported macros are usually recommended and when custom VAST feed requirements may need additional review or development.


How it works

VAST compatibility depends on supported platforms

Lightcast supports publishing across many App Stores, device types, players, and platforms. Because of this, multi-platform ad delivery requires compatibility across the platforms where your ads will run.

Lightcast’s ad-serving module supports compatible VAST Tags provided by demand sources, such as ad networks or ad exchanges, and can deliver the ads returned by those tags. However, Lightcast cannot guarantee that every VAST feed will be supported or accepted by every platform, device type, app, or player.

Macros and VAST formats can vary by ad provider

There are many different macros, placeholders, and VAST feed formats. Each ad network or demand partner may use its own preferred format.

A macro is a placeholder in a VAST Tag that can be replaced with information during an ad request, such as device, platform, app, content, or viewer details. Macro support can vary by platform, device, app, or player.

When you provide VAST Tags from a third-party ad platform, Lightcast may request the ad provider’s macros and parameters documentation as part of the integration review. This documentation helps confirm which placeholders are required, what each parameter passes, and whether the feed can be supported across the intended platforms.

Not all OTT devices, app platforms, or players support every macro or VAST format. A VAST Tag that works on one platform may not work the same way on another platform.

Supported and necessary macros reduce compatibility risks

VAST Tags that use only the required, widely supported macros are generally less likely to encounter compatibility issues across multiple platforms.

Using only supported and necessary macros can reduce the risk of compatibility issues, rejected ad requests, or unexpected behavior on specific devices.

For this reason, Lightcast recommends keeping VAST Tags as simple as possible and using only the supported macros required by the ad provider and the platforms where ads should run.

Some VAST feeds may behave differently across devices

Some demand sources and VAST feeds may cause issues on specific devices or platforms.

Potential issues may include:

  • Unexpected behavior when moving between videos after ad requests

  • Lower-than-expected fill rates

  • Unclear pass-backs between demand sources in a multi-source waterfall setup

  • Device-specific playback or ad request behavior

If you use a multi-source Waterfall/Fallback Campaign, make sure each VAST feed uses supported and necessary macros to help reduce compatibility risks across platforms.

Custom VAST feed requirements may require additional work

Standard compatible VAST feed integration may be included as part of the ad-server setup fee and ad-module integration fee per app.

If your ad network requires custom macros, custom feed formatting, or other special VAST feed adjustments, additional customization may be needed. Lightcast may also request macros and parameters documentation from the ad network before integration can be reviewed. Contact Customer Support to confirm the available options, technical requirements, and whether custom development fees apply.


FAQs

Are all VAST feeds supported on all platforms?

No. Lightcast supports compatible VAST Tags, but not every VAST feed is supported or accepted by every platform, device type, app, or player.

Compatibility depends on the VAST feed, the macros included, and the platforms where ads should run.


Why does Lightcast recommend keeping VAST Tags simple?

Simple VAST Tags that use only supported and necessary macros are generally less likely to encounter compatibility issues across multiple platforms.

Using supported and necessary macros can reduce the risk of rejected ad requests, unexpected playback behavior, or lower fill rates caused by compatibility issues on specific devices.


What are macros in a VAST Tag?

Macros are placeholders in a VAST Tag that are replaced with information, such as device, platform, app, content, or viewer details, when an ad request is made, where supported.

Because platform support can vary, not every macro will work across every OTT device, app, or player.


Why does Lightcast request macros and parameters documentation?

Lightcast may request macros and parameters documentation when VAST Tags come from a third-party ad platform. This documentation helps confirm which placeholders are required, what each parameter passes, and whether the VAST feed can be supported across the intended platforms.


Can custom macros be added to a VAST feed?

Custom macros may be possible, but they require review.

If your ad network requires custom macros or custom VAST feed formatting, additional customization may be needed and may involve additional fees.


Can a VAST Tag work on one platform but not another?

Yes. Different platforms, devices, apps, and players may support different VAST formats or macros.

A VAST Tag may work correctly on one platform but behave differently on another if the feed uses unsupported macros or formatting.


Can VAST feed compatibility affect fill rates?

Yes. Compatibility issues may affect whether an ad request is accepted, returned, or played successfully.

Fill rate also depends on the ad network’s available demand, targeting, request volume, and campaign setup.



Pricing

The Advertising Module is available as an add-on.

See the Add-On Rates page for more information about advertising solutions.


Additional related resources

Was this article helpful?

Sorry about that! Care to tell us more?

Thanks for the feedback!

There was an issue submitting your feedback
Please check your connection and try again.