Connect a DOOH network running Broadsign Control (CMS) to programmatic demand via Broadsign Reach's SSP APIs
domain: docs.broadsign.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Configure Broadsign Reach (Broadsign SSP) within the existing Broadsign Control (CMS) instance per the documented configuration guide
Set up the Creatives API integration so connecting DSPs can fetch creative-approval status for their campaigns
Enable the Deals API for private marketplace deal automation when working with specific DSP partners rather than only the open exchange
If audience-based buying is required, integrate the separate Broadsign Control Real-Time Audience API or the Proof-of-Play Audience Protocol depending on whether predictive or measured audience data is needed
Review Broadsign Reach release notes before upgrades, since SSP/programmatic feature behavior changes across versions
Known gotchas
Broadsign Reach requires an underlying Broadsign Control (CMS) deployment — it is not a standalone product usable without Broadsign's CMS
Real-time predictive audience bidding and proof-of-play measured audience are two distinct protocols/APIs, not one; using the wrong one produces the wrong kind of audience number for the use case
Programmatic yield features (Open Exchange, Deals API) are separately configurable modules — enabling Reach does not automatically enable every programmatic feature
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?