- 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.
This page describes the configuration of a Broadsign integration with Quividi 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.
Note: Broadsign does not distribute the Quividi solution.
Note: It is possible to run Quividi and Broadsign Control Player from two different systems.
Quividi integration is an advanced feature. We recommend that you be familiar with the following:
- Configuration Profiles - Players
- Criteria and Conditions
- Players (Resource)
- Display Units
- Content Variables
The Quividi Tab in Configuration Profiles
Configure Quividi settings in the Integrations section of your player configuration profile. See The Integrations Section.
In the Quividi Tab, you can configure the following:
- 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:
To allow Broadsign Control Player to connect to the Vidireport's server, and receive audience dynamic measurements with a 500 milliseconds resolutions (enough accuracy for both dynamic conditions and impression metrics), you must add the following:
- enable_socket = 1
- default_event_mode = 2
- event_send_period = 500
In Broadsign's player configuration profile
(see The Quividi Tab), enter the IP or Hostname and port of the Quividi application:
Perfect synchronization is key for this setup as both Broadsign Control Player and Quividi need to be configured to use the same reference clock in order to remain in sync. Because Broadsign Control Player is by default configured to keep track of its internal clock and correct it relatively to Broadsign Server, the Time Synchronization option needs to be changed:
- Open your configuration profile properties.
Go to Devices and Triggers > Core.
- Configure the following:
- If the Quividi application is installed on the same machine as Broadsign Control 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 same Network Time Protocol (NTP). In addition, Broadsign Control Player must use the system time as its internal clock. In this case, set the Time Synchronization options to "Do not synchronize clocks".
You can capture audience information, independently, on both sides of a totem display (i.e., a dual-screen with displays on opposite sides of a small tower).
Example: Imagine that you have set up two instances of VidiReports (with cameras attached). The screen on each side of the totem requires its own port, and corresponds to a separate frame with its own criterion ("F1" and "F2").
When enabling dynamic conditions, Quividi will inject conditions into Broadsign Control 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.
For more details about conditions, see Criteria and Conditions.
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.
For more details, see: