The generate endpoint can use active conditions to generate playlists specific for those conditions.
Note: This feature does not apply to the generate_long endpoint.
In Broadsign Control, conditions allows third-party applications to communicate with the server via the Broadsign Control Player, to activate specific pieces of content for playback. For example, conditions can be used to play a different ad copy depending on the weather. If it is sunny, ad copy X plays; if it is rainy, ad copy Y plays. For more information, see Criteria and Conditions in the Broadsign Control documentation.
Both conditions and exclusive conditions are supported.
When a regular condition is active, material associated with the condition is added to the loop. When an exclusive condition is active, only material with that condition is added to the loop. No other material is played. Conditions behave as per the remote action condition (see Condition Actions - Use Remote_Action in the Broadsign Control documentation).
The following points are of interest:
- Broadsign Air protects the first 10 minutes of the generated playlist, which are essentially “frozen”. This gives multiple physical players enough time to perfectly sync up on the same Playlist by ensuring that Broadsign Air does not touch a portion of the generated playlist before all physical players had the chance to contact it. Also, Broadsign Reach bids are only issued for Broadsign Reach slots appearing within that period, which avoids reissuing Broadsign Reach bids for multiple physical players.
- Polling with updated conditions does not impact frozen content.