Docs / Capability guide
Auction, VAST, OpenRTB and JSON decisions
Send test requests through VAST, OpenRTB, or the JSON Decision API.
All capabilities · Related guide · Agent prompt for this capability
When to use this example
Before connecting a player, bidder or application, check that its request reaches the intended placement and produces a response it can read. The same probe helps investigate no fill without adding test impressions or clicks.
What the example gives you
You get a protocol-specific response summary, including filled or empty results. The probe does not render creatives or follow tracking URLs, so player behavior and event delivery need separate checks.
Before you start
A reachable serve endpoint and a valid sandbox placement/tag; use the matching VAST, OpenRTB or Decision API guide for request fields.
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
Choose GET /vast for tags, POST /ortb for OpenRTB 2.6, or POST /decision for JSON integration. Use a configured tag/placement and a unique request ID, and preserve required privacy signals.
Run serving_probe.py with vast, ortb or decision and the documented environment variables; use --request for your own OpenRTB/Decision JSON. The tool prints a response summary and does not follow creative URLs or fire impression/click beacons.
Compare direct, programmatic and house outcomes using explainRequest, diagnoseServing and the placement decision funnel. After an admin change, check plan health to confirm the serving nodes have the new version.
Check the result
Validate the protocol response and no-fill case. Record an impression only when the ad is shown. Use signed beacon URLs for the events that occur.