Insufficient documentation for web analytics

Product

Analytics

Question

I’m struggling with the Bitmovin analytics. I’m using a Samsung SmartTV and can’t make it send data. I already searched the whole documentation, but nowhere I can find a simple example for using it. There’s a minimal example at How to setup Bitmovin Analytics on SmartTVs, but it doesn’t say where the config goes and when it says „The rest of the steps…“, it leads to an 404 page of on old documentation. I found this example code bitmovin-player-tizen-demo/js/main.js at main · bitmovin/bitmovin-player-tizen-demo · GitHub, but it only sets analytics data for the creation of the player (new bitmovin.player.core.Player). It doesn’t show how to change the title, videoId and custom data for player.load(source). By accident I found this Enabling Bitmovin Analytics, where an analyticsSourceMetadata object in the player.load object is shown. But in the same page there’s an analyticsConfig object shown in the player configuration that I never heard of before.
These are all little bits of sometimes contradictory information spread over multiple pages. It’s quite a mess.

Does somebody have a simple description that shows the valid parameter object hierarchy for player creation and player.load? Some real world stuff with code examples?
Even better with a real world description of parameters like how the app_id really works and what it is used for in the Bitmovin backend. Is it used to keep together all services (web/mobile/smarttv) of „myvideoservice“? Does it need to be the URL that has been requested in a LG TV? What about devices that don’t use URLs like Samsung TVs or mobile devices?
Or what about the customUserId? I can use an account id to track behavior over multiple devices, but this only works after a login and I would not see if users play trailers before they login. So I could use a device id, but then I could not evaluate the user behavior anymore. I’m missing a manual how these parameters meant to be used.

The analytics documentation raises more questions than it answers. At least for web.