Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Commanders Act multi-player analytics issue #272

Open
3 tasks
amtins opened this issue Oct 1, 2024 · 5 comments
Open
3 tasks

Commanders Act multi-player analytics issue #272

amtins opened this issue Oct 1, 2024 · 5 comments
Assignees
Labels
enhancement New feature or request

Comments

@amtins
Copy link
Member

amtins commented Oct 1, 2024

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 amtins converted this from a draft issue Oct 1, 2024
@amtins amtins moved this from ✏️ Draft to 📋 Backlog in Pillarbox Oct 1, 2024
@amtins amtins added the enhancement New feature or request label Oct 1, 2024
@amtins amtins self-assigned this Oct 1, 2024
@amtins amtins added this to the Playback tracking v2 milestone Oct 1, 2024
@amtins amtins moved this from 📋 Backlog to 🚧 In Progress in Pillarbox Oct 1, 2024
@amtins
Copy link
Member Author

amtins commented Oct 22, 2024

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
Copy link
Member Author

amtins commented Oct 22, 2024

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
Copy link
Member Author

amtins commented Oct 25, 2024

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
Copy link
Member Author

amtins commented Oct 25, 2024

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

@amtins
Copy link
Member Author

amtins commented Nov 18, 2024

Most external variables now have their counterparts in event variables, to make it easier to handle multiple instances.

  • Comscore has been integrated
  • Webtrekk has been integrated
  • Chartbeat still needs a little work, so contact Charbeat support for more details on multi-instance

At this stage, there is no guarantee that integration will be correct.

This task has been paused to allow time for other tasks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: 🚧 In Progress
Development

No branches or pull requests

1 participant