Export near-live proof-of-play data from Broadsign Control to an external analytics system via the Real-Time POP API

domain: docs.broadsign.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. In Broadsign Control Administrator, create a Configuration and a Player Configuration Profile for the target players
  2. Open the profile's Integrations > POP tab, enable External POP reporting, and set the External URL that will receive HTTP POST data
  3. Configure reporting cadence — immediate per-playback submission, or buffered every X seconds (1-65535s, with ~10% jitter) — plus Max POPs per request (default 1000)
  4. Optionally set an API Key, sent as both a Broadsign-Api-Key header and the payload's api_key field on every POST
  5. Implement the external endpoint to accept a JSON body containing player_id and an array of pop records (display_unit_id, frame_id, ad_copy_id, campaign_id, schedule_id, impressions, end_time, duration), returning a 2xx status to acknowledge
  6. Optionally enable verbose mode to receive pop records as dictionaries instead of positional arrays for easier downstream parsing

Known gotchas

Related routes

schedule content to broadsign control players via the broadsign control rest api
docs.broadsign.com · 6 steps · unrated

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?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans