This document describes the caching manager for programmatic ad content. This feature optimizes ad delivery by requesting ads in advance and managing ad playback within your content loop.
The caching manager checks for ad slots scheduled to play in the next 5 to 20 seconds. When a new slot is identified, the player sends an ad request to the configured ad server(s).
- Ad Server Response – If the ad server returns a valid ad, the original content slot is replaced with the ad. The duration of the slot is adjusted to match the length of the received ad.
- Multiple Ad Servers – If multiple ad servers are configured, the player sends requests sequentially in the order specified in the Player Configuration Model. The ad from the first server to respond with valid content is played. If no servers return a valid ad, the scheduled content plays as planned.
- Unsold Time Management – Programmatic ads can fill unsold slots within your content loop. To ensure accurate loop timing, the duration of these ads is deducted from the total available "unsold time." This prevents the loop from running longer than its set duration due to the insertion of ads.
This mechanism also prevents consecutive ads from playing back-to-back. Without this control, ads intended as buffers between content could be skipped to maintain the loop's overall length, potentially disrupting the intended viewing experience.
Note: For players experiencing high internet latency, the caching manager settings can be adjusted in the Player Configuration Model's Expert section. Contact Broadsign Services for assistance with configuration.
To avoid excessive ad requests, a throttling mechanism is implemented. If multiple ad requests fail to receive a response, the system will temporarily delay subsequent requests. This delay increases with consecutive unsuccessful attempts, starting from 2 seconds after 2 failed attempts and reaching up to 2 minutes after 8 consecutive failed attempts. This strategy helps reduce unnecessary traffic when ad content is unavailable.