More about VAST

Vast ID and the Face GUID

The [unit_id] in the URL tells the player to send the Face GUID not the Face Number. This is because face numbers are not unique.

VAST and MOAT

Tracking pixels are typically sophisticated enough to know if the same user has already seen an ad on that device, and as such, they can differentiate between unique and repeat visitors. Out of home campaigns are fundamentally different. Tracking pixels are just HTML code, and the player supports the playback of HTML authored content. However, such tracking pixels are not particularly valuable in OOH digital campaigns loaded over many screens, many times per minute where visitor uniqueness cannot be guaranteed.

VAST and Playlogs

VAST activities do not produce records in Broadsign Ayuda POP reports. Broadsign Ayuda playlogs do not track programmatic data. It is the programmatic content supplier that will provide this playlog data.

Sync Groups and VAST content

Sync Groups can be used with VAST. However, not all third party ad-servers can receive the call from the leader player that includes its follower information.

This will result in the sync group leader functioning correctly but the follower players not showing VAST content. Why? Only the leader makes the call to the ad Server but it also makes a POST call that includes all of the follower players’ IDs and typically, this is what ad servers find problematic.

See Also: