- We provide a short video introducing the features of our docs. See Broadsign Documentation in MadCap Flare.
- Images are thumbnails. To embiggen, click the image.
- Search is based on keyword. Ex: "Proposals"
- Do not search with natural language. Ex: "How do I create a proposal?"
- For release notes and highlights (past and present), see Release Highlights.
- Broadsign provides docs for many of the latest versions of its products. For older documentation, see Docs Archives.
The Integrations Section
This section contains settings for products that integrate with Broadsign Control.
Note: This section is one of several under Configuration Profile Properties for players. For general information, see Configuration Profiles - Players. For edge server profiles, see Configuration Profiles - Edge Servers.
This section describes the settings for the Audience API. For a detailed tutorial, see Audience API.
- Enable Audience API: To enable Audience API, select this box.
- Path to CSV file: A mandatory path (absolute or relative) from which Broadsign will read the audience file.
Settings in this tab control how Broadsign Control Player integrates with the Intel Anonymous Video Analytics solution. This technology uses a camera to monitor and react to the audience in front of the display. There are two primary areas of functionality: Dynamic Conditions and Data Collection.
For information on how to configure Intel AIM on you player PC, see Intel AIM Setup.
This functionality, when enabled, allows Broadsign Control Player to dynamically adjust which Ad Copy is displayed depending on audience composition.
Example: Consider an advertisement for perfume. If the audience is primarily female, the player can display an ad for the female perfume line. When the audience composition changes to primarily male, the ad automatically switches to a male-oriented cologne ad.
Check the checkbox to enable this functionality, then specify the IP/Hostname and port of the AIM API server. This is typically localhost if the AIM suite is on the same machine, however, it is possible to host the AIM API on a separate machine. The AIM API server needs to be enabled in the AIM suite configuration.
The next section is for mapping the Intel AVA Conditions to your pre-defined Broadsign conditions. You will then use the Broadsign conditions to create a campaign with multiple bundles using these conditions.
Note: Only one dynamic condition of each type (Gender and Age) are active at any time. The condition that is activated depends on a simple majority rule. If there is a tie (say 3 men and 3 women), then the condition that gets activated is randomized as to ensure approximately even distribution.
This functionality, when enabled, allows Broadsign Control Player to query the AIM web service to acquire viewership data. This data is then incorporated into the standard Broadsign proof of play reports as impressions. See Real-time POP API.
Check the checkbox to enable this functionality, then specify the username and password that is required to access the AIM analytics website.
Note: For Intel AVA Data collection to work, the AIM suite must be installed on the same machine as Broadsign Control Player. This is because the Broadsign Control Player must read from AIM configuration files in order to uniquely identify the AIM device.
When AVA Data Collection is enabled, Broadsign Control Player will delay reporting of all playback statistics for a minimum of 24 hours up to a maximum of 72 hours. This is because the AIM Web Service must be queried for viewership information and this information is compiled only once per day.
Note: In order for the AIM Suite and Broadsign Control Player timestamps to match, the Broadsign Control Player MUST be synchronizing the system time.
For more detailed information, see The Core Tab.
This section allows configuration of a Broadsign integration with Quividi. For a detailed tutorial, see Quividi.
Quividi is a camera-based audience measurement system that enables the determination of the number of viewers in front of a screen, as well as the audience composition. With the native integration, it becomes possible to:
- Capture audience information, independently, on both sides of a totem display.
- Use dynamic conditions to play ads based on the audience composition.
- Include an accurate impression count as part of the proof of play of your campaigns.
Note: Broadsign does not distribute the Quividi solution.
Note: It is possible to run Quividi and the Broadsign Control Player from two different systems.
For a detailed tutorial, see Quividi.
These settings allow Broadsign Control to manage DIAPI set-ups. For a detailed tutorial, see Dispenser Independent API (DIAPI).
This section describes the configuration settings for real-time, external POP (proof-of-play). For a detailed tutorial, see Real-time POP API.
- Enable External POP reporting: Default = false. When enabled, Broadsign Control Player will attempt to submit proof of play to the external location.
- External URL: A valid HTTP/HTTPS URL to which the POP will be HTTP POSTed. Mandatory if external POP is enabled.
- API Key: Optional. If specified, Broadsign Control Player will submit this string with every HTTP POST request, adding to the security of the external POP service.
- Report POP immediately: If activated, Broadsign will submit POP immediately after each playback.
- Report POP every X seconds: If activated, Broadsign will buffer POP client-side and submit it every X seconds. Valid range: 1-65535 seconds. Broadsign applies a +/- 10% randomization client-side to avoid synchronizing the POP submission.
- Max POPs per request: Default value: 1000. Valid Range: 1-65535. This setting controls the maximum number of POPs to send in one HTTP POST.
- Verbose mode: Default=Off. When enabled, the POP JSON document will be more verbose, i.e., it will use dictionaries instead of arrays.