Docs / Capability guide
CTV, audio, pods and SSAI
Test ad duration and media compatibility before connecting a player or stitched stream.
All capabilities · Related guide · Agent prompt for this capability
When to use this example
An ad that plays on its own may be too long for a break or incompatible with another device. Test short, full and impossible breaks before connecting CTV or audio inventory to a player or stitching service.
What the example gives you
The HTTP probe lets you send saved OpenRTB video or audio requests and inspect response summaries. Use the responses alongside pod diagnostics, then verify playback and event timing in your actual player.
Before you start
Video/audio inventory, compatible creatives and a sandbox player; SSAI also requires the deployment's stitch/transcode services and accessible media.
Run the example
Extract the archive and follow README.md for setup, commands, and expected results. Start with serving_probe.py. Local tests use sample data.
Python tools accept --help. To connect to your workspace, supply the deployment URLs, credentials and resource IDs required by the tool.
Connect it to your application
Set the placement media and use the OpenRTB guide's video/audio duration fields. For pods, set the intended total break duration and per-ad limits and check the resulting pod as a whole.
Probe a short break, a full break and an impossible duration combination. Confirm the response respects duration, advertiser exclusions and no-fill constraints before moving to the player.
Use the issued VAST/VMAP or SSAI integration URL from your deployment. Test playback and event timing in the player. The HTTP probe stops before playback and does not send beacons.
Check the result
No ad exceeds the requested duration and no pod exceeds the break. A JSON or VAST response alone does not verify transcoding, HLS playback, quartiles or settlement.