1. Inventory and CMS discovery
The first step is to map screen types, resolutions, playback loops, connectivity, and the integration capabilities of the current CMS. This determines whether a direct connection or middleware is required.
- Screen and location inventory
- CMS API and data structure
- Creative format rules
- Current reporting capability
2. Select the integration model
If the CMS has native programmatic support, an SSP connection can be established directly. If not, Beehive designs a middleware layer that manages data and playback flows between the screen network and demand platform.
3. Pilot, launch, and operations
Before launch, screen matching, creative download, playback confirmation, and reporting are verified with a controlled pilot. Daily operations, error monitoring, and optimisation then begin.
- Pilot screen group
- Playback record validation
- Error and connection monitoring
- Regular performance reports
4. Sales house option
In addition to technical integration, the Voice Medya sales house model actively presents inventory to field and agency networks. It is designed to complement the media owner's existing direct sales structure.