Prisma player

The @prismamedia/player package is available for external Prisma Media sites to implement a Dailymotion video player with monetization managed by CoreAds.

The following actions are performed by the package:

• Loading the Dailymotion SDK
• Creating the player and ad call in parallel

Note

The player listens to the AD_READYTOFETCH event triggered by Dailymotion when an ad can be displayed. On each call, the monetization chain is retrieved from CoreAds and injected into the player

Prerequisites

CoreAds

The CoreAds script must be loaded and available on the page.

The line below initializes the CoreAds queue. It must be placed before the CoreAds script.

window.coreAds.queue = window.coreAds.queue || [];

Player types

Here are the available player types depending on their location on the page.

Leader

The Leader player is the main player of the page. It is generally located at the top of the page with autoplay enabled.

For monetization reasons, it must execute as early as possible. It should therefore not be lazy-loaded.

Note

This type of player has the sound set to0.01 by default.

Widget and Others

The Widget and Other players are secondary players, they can be lazy-loaded and initialized later according to your needs. Generally autoplay is disabled.

Installation

Warning

The package is delivered in TypeScript only. Adapt your configuration to import .ts files (see TypeScript with webpack).

NPM

The @prismamedia/player package is hosted on the NPM public registry. Install the package on your project with the following command:

npm install @prismamedia/player --save-dev

yarn add @prismamedia/player --dev

Warning

Minimum Node.js version 20.18.0

Setup

HTML

The video player requires an HTML <div> element with the following HTML attributes:

• id: Unique identifier
• data-ads-core: JSON configuration object for the player

<div
  id="<unique_id_1>"
  data-ads-core='{
    "playerId": "<player_id>",
    "playerPosition":  "<player_position>",
    "playerVideoTitle": "<player_video_title>",
    "playerVertical": "false"
  }'
>
  <div id="<unique_id_2>"></div>
</div>

Important

Both HTML elements must have a unique id attribute

Property	Type	Description
playerId	string	Dailymotion player identifier
playerPosition	'Leader' | 'Widget' | 'Autre'	Player position
playerVideoTitle	string	Video title
playerVertical	boolean	Whether the player should be vertical

JavaScript

import PrismaPlayer from '@prismamedia/player';

The constructor accepts the following parameters:

Arguments	Type	Default	Required	Description
playerElement	HTMLElement	null	Required	HTMLElement to target the player
config	Object	{}	Optional	Player configuration

Initialize the library with the HTML element with the <unique_id_1> and the [data-ads-core]. Next, call the init method after user consent acceptance.

const prismaPlayer = new PrismaPlayer(document.getElementById('playerWrapper-1'));
// Check consent before the next call
prismaPlayer.init();

Configuration

The second arguments of the contructor is an optional object with the following parameters:

Arguments	Type	Default	Description
playerParams	Object	{}	Player parameters for Dailymotion video player for all video players
leaderVolume	number	0.01	Volume of the leader player (between 0 and 1)

const prismaPlayer = new PrismaPlayer(document.getElementById('playerWrapper-1'), {
  playerParams: {
    mute: true
  }
});
prismaPlayer.init();

Events

The package exposes the following native events on the [data-ads-core] element. The event can expose additional data in the e.detail object.

Event type	Description
prismaPlayerReady	Triggered when the Dailymotion player is ready. The player instance is passed in the event.

Example of a listener when the player is ready.

document.querySelector('#playerWrapper-1').addEventListener('prismaPlayerReady', (e) => {
  // The player instance is accessible in the `e.detail.instance` object
  // Example to set the volume to 1
  // e.detail.instance.setVolume(1);
});

Examples

Leader Player

Initializing a Leader type player

<div
  id="playerWrapper-1"
  data-ads-core='{
    "playerId": "<player_id>",
    "playerPosition": "Leader",
    "playerVertical": "false"
  }'
>
  <div id="<player-1"></div>
</div>

const prismaPlayer = new PrismaPlayer(document.getElementById('playerWrapper-1'));
prismaPlayer.init();

Widget Player

Initializing a Widget type player

<div
  id="playerWrapper-1"
  data-ads-core='{
    "playerId": "<player_id>",
    "playerPosition":  "Widget",
    "playerVertical": "false"
  }'
>
  <div id="<player-1"></div>
</div>

const player = new PrismaPlayer(document.getElementById('playerWrapper-1'));
player.init();

Multiple players (Leader + Widget)

Initializing two players on the page, one Leader and one Widget

<div
  id="playerWrapper-1"
  data-ads-core='{
    "playerId": "<player_id>",
    "playerPosition": "Leader",
    "playerVertical": "false"
  }'
>
  <div id="<player-1"></div>
</div>
<div
  id="playerWrapper-2"
  data-ads-core='{
    "playerId": "<player_id>",
    "playerPosition": "Widget",
    "playerVertical": "false"
  }'
>
  <div id="<player-2"></div>
</div>

const playerLeader = new PrismaPlayer(document.getElementById('playerWrapper-1'));
playerLeader.init();

const playerWidget = new PrismaPlayer(document.getElementById('playerWrapper2'));
playerWidget.init();

Package testing (npm-pack workflow)

Important

The local NPM package is intended for development only, not for production. Do not use TGZ in production.

An npm-pack workflow is available to test the package before its official publication on NPM.

Follow the steps below to use the workflow:

1. Trigger the workflow from the GitHub Actions page

   • Click on Run workflow
   • Select the branch: <branch_name>
   • Click on Run workflow

2. Retrieve the artifact

   • Click on the running job
   • Wait for the workflow to complete
   • Download the artifact (prisma-player-pack.zip)

3. Install the local package

   • Extract the ZIP file
   • The content contains a TGZ file (local NPM package)
   • Install the TGZ on your project:

   npm install <path_to_tgz_file>

4. Test and validate

   • Test the package and its features
   • If everything works correctly, the MR can be merged
   • Once merged, you can install the official version from NPM

💡 More information on the npm-pack.