PV4 Documentation
Breadcrumbs

Data Integrations

A Data Integration is a connection type that lets the Orchestrator connect to a third-party service — some are generic (like UDP, which can be pointed at almost anything), others are built for one specific source (like a bespoke ODF server implementation). A Script is the separate piece that receives the data coming in on an integration and transforms it into a format templates can use — see Scripts.

This page, at the global level, is view-only — it shows which configuration fields are available for each connector type. Actual configuration happens per show, on that show's own Data Integrations page, where the same fields become editable.


Key functions

  • Multi-source connectivity
    Integrate with APIs, telemetry systems, and third-party data providers to bring live stats, scores, and other event-critical data into PV4.

  • Real-time display
    Feed integrated data directly into PLAY templates for on-screen visualization, ensuring audiences receive up-to-the-second information.

  • Contextual insights
    Combine operational data with behavioral analytics to inform workflows and audience engagement.

  • Flexible configuration
    Supports multiple providers per show, with secure authentication via client IDs and secrets.

Show-level integration settings can be overridden by the Orchestrator's local configuration — the same waterfall pattern used elsewhere in PV4. If the Orchestrator sets a value (like an address or port) locally, that local setting takes precedence over what's configured in the Portal.


Use cases

  • Sports events displaying live scores and player stats.

  • Entertainment venues showing dynamic audience engagement metrics.

  • Sponsorship activations powered by real-time performance data.