Commanders Act multi-player analytics issue

[amtins]

Description

The ticket ADI-267 describes media playback tracking issues when the web page contains multiple instances of the player. Since this use case can only be handled by our tag manager (Commanders Act), we need to create a new container.

Acceptance criteria

• Each player instance on the same page must be tracked correctly

Tasks

• POC of the new solution
• Create a new Commanders Act container that can handle multiple player instances
• Update player to adapt to new container

[amtins]

I spoke to Mario from the ADI team to find out if they minded all the media data being sent to each player event. The answer was: "As long as it keeps working, it doesn't matter".

The advantage of sending media data to each player event is that it no longer affects the number of player instances.

However, it remains to be seen whether other Commanders Act containers used data from media_* variables.

Finally, we need to adapt Comscore's instantiation so that there are as many instances as there are players.

[amtins]

In order to test the implementation of multiple instances of Comscore, the Comscore SDK script must be imported into the tag. It appears that this script is not available via a CDN and must be requested directly from Comscore.

[amtins]

After discussing with RTS, RTS UDP can't be decoupled from Play's container. The reason is snowplow creates a new session id each time the script is loaded.

[amtins]

After a careful reading of the Comscore documentation, it seems that either we have an incomplete version of the documentation or the SDK has evolved. As a result, the way Comscore is initialized on the Commanders Act side may no longer be entirely up to date.

An e-mail has been sent to Comscore to clarify the situation.

I had an outdated version of the documentaiton. La dernière version en date https://mymetrix-support.comscore.com/hc/en-us/article_attachments/20238535420443