How to create a new player?

StreamRail’s player is also known as Blade. It serves our partners through two types of activities:

Programmatic buying – StreamRail player is implemented on DSP’s in order to buy traffic programmatically.

Direct activity– the player is implemented within the Publisher’s site itself (in case the Publisher has no player of its own).

First, make sure you have a Traffic Channel set up, as every player created is assigned to a Traffic Channel.

Then, at the platform, go to Players under Supply.
To create a new player, click on the ‘+’ button at the bottom left of the screen, and you will be directed to the player creation screen.
Give your player a suitable name (preferably one indicating the activity of the player and publisher in which the player is implemented).

Select the Traffic Channel to which the player will be assigned.
In case a Desktop or a Mobile Web Traffic Channel was selected, you will be prompted to select the type of activity for this player:
Direct Supply – selecting Direct Supply will open a new list of options designed for this type of activity. This type of activity is more suitable for direct implementation. See below for more information.
Programmatic – This option is used for programmatic buying with the player. This type of activity is more suitable for implementation in DSPs.

Please note – once the activity type has been selected and the player created, it cannot be changed in the future.

Ad Unit options – Once Direct Supply activity is select, 4 new options for the player are available for your choosing:
1. Classic – a classic static player.
2. Classic and Sticky – the player will start as a static player, with the addition of being a Sticky player once it is out of view.
3. In-Text – the player expands in between the elements of the page (according to the placement in the HTML source code).
4. In-Text and Sticky – the player will have the combined capabilities of both the Sticky and In-Text options.

Advanced Player Settings

Viewability Tolerance – all of the aforementioned options perform differently according to the Viewability Tolerance setting. The Tolerance determines the lower bar for how much of the player, in percentage, is in view before the Sticky and Viewability options occur. The default value is 50% :

Sticky Player option – selecting the Classic and Sticky option will configure the player to start as the classic player, but stick to the corner of the page once the player is out of view, like this:

An example for an available Sticky Player option:

Position – configures to which corner the player will stick.

Only After Viewable – When “on”, the player will convert to a Sticky player only after the original player was in view at least once to the user. When “off’, the player will become sticky with no regards to the user viewing the original location of the player.

Close Button – enable/disable a close button on the Sticky player.
Please note – once the user closes the Sticky player, the original player will still be active. It will not convert to a Sticky player until the page has been refreshed.

Width/Height – configures the width and height of the Sticky player. This does not affect the player’s size in its initial location.
You can configure both the width and height, or configure only one of the options, and the other will be adjusted automatically to match the ratio of the original size.

Horizontal/Vertical Offset – these options configure the distance of the player from the limits of the page according to the Position selected.

In-Text Player option
Selecting the In-Text option will configure the player to expand in between the elements of the page only once an ad has been found (depending on the placement of the player’s snippet):

Please note – due to the nature of the In-Text player, adding content to the player is not available with any In-Text ad unit.

Pause while out of view – enabling this option will pause the video whenever the user scrolls the player out of view, according to the viewability tolerance.

Close Button – enable/disable a close button on the player. Please note – once the user closes the In-Text player, it will close and will not be shown again until the page has been refreshed.

In-Text and Sticky Player option
Selecting this option will enable configuring the combined settings of the In-Text player, and the Sticky player:

Player Size Fixed/Adaptive – you can select an adaptive player size instead of a fixed size. Once Adaptive is selected, you do not need to configure the initial player size, as the player will automatically adjust its size to the placement in which the player is implemented.

You can also configure the player to be Responsive. This means the player will continuously detect and auto-adjust its size to the placement size. If set to Off, the player’s size will not change after initializing.

Watermark- in order to add a Watermark to the player, first change the Enabled state to On, and the Watermark setting will appear.

Image URL – input the watermark image file URL you wish to present as a watermark here.
Click URL – input the URL to which the user will be directed upon clicking the watermark.
Position – select the position of the watermark.
Opacity – the opacity of the Watermark as it will appear in the player.
Width/Height – configures the width and height of the watermark image.

Skip Ads – enables StreamRail’s skip button to the player, which enables skipping after 5 seconds.

Passback – replaces the code of our player with any HTML code you input here. The passback is activated according to the selected event, such as playerDone, AdError, etc.
Event Name – Select the event to trigger the passback.
HTML – Input the HTML code to be run once the passback is triggered.

Duplicating Players – Similar to the Ad Sources and Traffic Channels option, we added the option to duplicate players. Please note – The duplicated player will be of the same Activity type as the player being duplicated:

 

 

 

 

AMP

AMP is an open source HTML framework that provides a straightforward way to create web pages that are fast, smooth loading and prioritize the user experience above anything else.
StreamRail player component for AMP is now enabled, It’s free and from now you can easily use our player on AMP pages.

You can find it in amp.dev at this link as ‘blade’.

*For instructions of how to use enter  AMP Github