Datazoom's data collection integration can range from the very simple integrations to more complex integrations. The complexity is directly related to how a customer has chosen to implement their video player and how any of the existing data collection integrations all need to coexist.
In all cases, the Datazoom integration is setup once. All configuration of player data collection and data delivery to analytics systems is managed outside of the player. This provides maximum flexibility to use any number of analytics tools with a simple configuration change.
| Implementation | Pros | Cons |
|---|---|---|
The Datazoom HTML integration can be as easy as including <script src='https://platform.datazoom.io/beacon/v1/config?configuration_id=<CONFIG_ID>'></script> in the </video> tag, just after player load. | Simple, one line implementation via HTML; | None |
| A slightly complex implementation involves including the Datazoom plugin as the first script in a player javascript that contains additional synchronous data collection plugins. Datazoom with ensure that all data is passed through and available to the the next plugin | First line implementation in a player javascript; Data made available in a synchronous fashion. | Any changes, post Datazoom integration, will need to be verified to ensure data continues to be made available to other plugins in a synchronous fashion. |
| A more complex implementation involves including the Datazoom plugin in a player javascript that include timers to allow for asynchronous script processing. Again, the goal here is to ensure all required data is available to all plugins. | Existing plugins continue to have access to required data. | Longer initial development; Longer development as changes are made to player javascript; Changes to timers to ensure data is equally available to all plugins could add to script execution time. |
| In situations where there are multiple plugins, Datazoom offers a simple implementation that relies on core Datazoom technology to capture data and present data to multiple endpoints. This makes a plugin heavy player easy to manage as we do all of the work. | One line setup; Captured data is made available to multiple endpoints, simultaneously; Changes to data delivery is managed outside the player javascript | None |
Comments
0 comments
Article is closed for comments.