The Add-ons tab group contains the settings for features that Broadsign considers to be add-ons to our core products.
For general information about configuration profiles for players, see Configuration Profiles – Players.
For edge server profiles, see Configuration Profiles – Edge Servers.
Settings in this tab control how the Broadsign 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.
- Intel AVA Dynamic Conditions: This functionality, when enabled, allows the Broadsign player to dynamically adjust which Ad Copy is displayed depending on audience composition.For example, consider an advertisement for perfume. If the audience is primarily female, the player can display a 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.Please note that 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.
- Intel AVA Data Collection: This functionality, when enabled, allows the Broadsign Player to query the AIM webservice to acquire viewership data. This data is then incorporated into the standard Broadsign proof of play reports as impressions.Check the checkbox to enable this functionality, then specify the username and password that is required to access the AIM analytics website.For Intel AVA Data collection for work, the AIM suite must be installed on the same machine as the Broadsign Player. This is because the Broadsign Player must read from AIM configuration files in order to uniquely identify the AIM device.When AVA Data Collection is enabled, Broadsign 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 webservice must be queried for viewership information and this information is compiled only once per day. In orderfor the AIM Suite and Broadsign Player time stamps to match, the Broadsign player MUST be synchronizing the system time. For more detailed information, see Configuration Profiles – Settings Section – Core.
This section explains configuration of Broadsign’s integration with Quividi’s technology.
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:
- Include an accurate impression count as part of the proof of play of your campaigns.
- Use dynamic conditions to play ads based on the audience composition.
Configuring Quividi with Broadsign
To download the software, go to VidiReports.
To download the license file, go to QuiVidi License File.
- On the system running the Quividi application, the Periodic Event mode needs to be enabled by modifying the configuration file located under:
The following needs to be added in order to allow the Broadsign Player to connect to the Vidireports’ server and receive audience dynamic measurements with a 500 milliseconds resolutions (enough accuracy for both dynamic conditions and impression metrics):
enable_socket = 1 default_event_mode = 2 event_send_period = 500
- In Broadsign’s configuration, the IP or Hostname and port of the Quividi application to connect to need to be entered.
Enabling Dynamic Conditions
When enabling dynamic conditions, Quividi will inject conditions into the Broadsign Player based on the audience details being captured. In the configuration, you will specify the Broadsign Conditions to map those being returned by Quividi. Only one condition for each type (Age or Gender) will be active at a time. The Broadsign Condition that will be activated on the Player will correspond with the one matching the majority of people.
Enabling Data Collection
When enabled, the number of viewers will be tracked using periodic audience measurements. It is important to note that any view intersecting the playback time of an Ad Copy will be recorded and counted as an impression regardless of time spent looking at the ad. This impression count will be then made available in the Campaign Performance report of the corresponding campaign.
System Time Synchronization
Perfect synchronization is key for this setup as both the Broadsign Player and Quividi need to be configured to use the same reference clock in order to remain in sync. Because the Broadsign Player is by default configured to keep track of its internal clock and correct it relatively to the Broadsign server, the Time Synchronization option needs to be changed:
- If the Quividi application is installed on the same machine as the Broadsign Player, the Time Synchronization option needs to be changed to “Let the Player set the system time” so it adjusts according to its internal clock.
- If the Quividi application is on a different machine, they both need to be set up independently using the the same Network Time Protocol (NTP). In addition, the Broadsign Player must use the system time as its internal clock. The Time Synchronization options must be set to “Do not synchronize clocks” in this case.