Player Tags

Player Tags define which Templates should be connected to which Channels and also as a way to override specific options of central templates.

Next to each name is some basic info and the (far right side) option to edit/archive this player tag.

Generate Player Tag

There are 2 ways to generate player tags in order to send them to publishers:

In the list of players tags, click the circle.
Edit an existing player tag and choose Generate.

2 forms of players can be generated:

Short - generates 1 line of code that can modified by you remotely. This is the preferred form.
Long - generates the entire code of the player, and can’t be controlled by you remotely, so only use this if you must.

Add/Edit Player Tag

When you click to add a new player tag or click to edit an existing one, you are presented with many useful options, most of which optional!

Please remember to click Save / Deploy after you’re done.

Clicking only Save (which is possible only when editing existing templates) saves the changes as draft. The changes won’t be reflected live until you then click Deploy.

Be aware if you only click Save, a red dot will appear next to the relevant template to indicate it’s not deployed live. This will also happen if you choose Preview!

OutStream

Main

Placement Info

Left side

Name (required) - the name of the player tag.
Description - any note you like to add about this player tag.
Ref1 - add custom macros (e.g. AV_CUSTOM1=abc&AV_IDFA=1234-5678).
Publisher (required) - choose the publisher this player tag belongs to.

Right side

Global Placement ID - used for all traffic regardless of any other setting, this option tells the browser which kind of ad is used, as required by many SSPs (see examples by Index Exchange).
Position Identifier
If you don’t want the player to appear exactly where the publisher actually put the script, use this to define an alternative location.
It can be either a Tag (e.g., div in case of <div>needed location</div>) a Class (e.g. titles in case of <div class=”titles”>needed location</div>), an ID (e.g. unique in case of <div id=”unique”>needed location</div>) or a (CSS) Selector (e.g. span>div:nth-of-type(2) in case of <span><div> </div><div>needed location</div></span>).
We suggest to use Selector, as if you choose Tag/Class/ID instead it will just be converted to Selector anyway.
For Tag/Class, in case of more then one of them you can specify which one by adding # and the number of it, e.g p#3 - the third occurrence of p tag in the page (similar to document.querySelectorAll('p')[2]).
Please leave Position Identifier empty if you use DFP 1x1 instead.
DFP 1x1 - serves as a fourth option for Position Identifier. This option assumes the publisher uses GAM aka Google Ad Manager (previously known as DFP) to create an iframe and put the script in it.
In that case, this option puts the player just above the iframe.
We suggest to use this option if the publisher should control the location, and yet you prefer to bypass 1x1 size (which is GAM’s preferable dynamic mode) plus reduce the risk of your ads being considered as “heavy ads” (which are blocked by browsers like Google Chrome, especially if found inside iframes).
Please leave DFP 1x1 empty if you use Position Identifier instead.

Default Channel/Template

The channel and template of Default can be used in 3 ways: All traffic (if both A/B Testing and Mobile Settings aren’t used), Desktop (if A/B Testing is not used, but Mobile Settings is) and Ignored (if A/B Testing is used).

Publisher Channel (required) - choose which publisher channel (based on Publisher) this player tag belong to.
Template (required) - choose which of the Templates should be used to define this player tag.
Predefined Only allows choosing only system built-in templates.

A/B Testing

Optionally divide the traffic between different positions/channels/templates.

This means both Desktop and Mobile traffic while ignoring both Default Channel/Template and Mobile Settings.

Mobile Settings

Optionally turn Default Channel/Template into Desktop only traffic, while using this section for Mobile Traffic.

Note this section is ignored if A/B Testing is used.

Left side:

Position Identifier - identical to the default setting, but used only for mobile.
DFP 1x1 - identical to the default setting, but used only for mobile.

Right side:

Publisher Channel - identical to the default setting, but used only for mobile.
Template - identical to the default setting, but used only for mobile.

Override Extensions

Optionally bypass the https://aniview-test.atlassian.net/wiki/spaces/BASIC/pages/655497/Templates#Extensions for this specific tag. If you like to enable it, see the templates' extensions for instructions how to fill the settings.

Override Functions

This is one of the player tags' most powerful features, as it allows you to optionally inject your own JavaScript code into the player.

Each function is used in a different stage in the player tag’s events.

You can choose each function to override its default behavior.

Unique - controls the detection of whether this player runs more than once.
Find Win - controls if the player should run in the same document as the script of above it (e.g. parent or top).
Post Create - a usually empty placeholder that runs after the player’s main DIVs are created.
Retry - controls what happens when the player tries to re-activate itself after failures.
Create - controls the creation of the player’s main DIVs.
Position - controls where to place the player inside the page.
Load - controls the external calls to the player’s core.
Post Start - a usually empty placeholder that runs after the player has finished its initial loading.
Get Attribute - controls the pull of attributes from the script’s GET parameters.
Start - starts the player object.
Pre Run - a usually empty placeholder that runs before the player runs.
Run - controls the initially loading of the player.
Target - checks if the player runs in Desktop or Mobile.
Track - controls how the player tracks with pixels its internal flow.
Init - reserved for future usage.

InStream

Main

Placement Info

Left side

Name (required) - the name of the player tag.
Description - any note you like to add about this player tag.
Ref1 - add custom macros (e.g. AV_CUSTOM1=abc&AV_IDFA=1234-5678).
Publisher (required) - choose the publisher this player tag belongs to.

Right side

Global Placement ID - used for all traffic regardless of any other setting, this option tells the browser which kind of ad is used, as required by many SSPs (see examples by Index Exchange).
Position Identifier
If you don’t want the player to appear exactly where the publisher actually put the script, use this to define an alternative location.
It can be either a Tag (e.g., div in case of <div>needed location</div>) a Class (e.g. titles in case of <div class=”titles”>needed location</div>), an ID (e.g. unique in case of <div id=”unique”>needed location</div>) or a (CSS) Selector (e.g. span>div:nth-of-type(2) in case of <span><div> </div><div>needed location</div></span>).
We suggest to use Selector, as if you choose Tag/Class/ID instead it will just be converted to Selector anyway.
For Tag/Class, in case of more then one of them you can specify which one by adding # and the number of it, e.g p#3 - the third occurrence of p tag in the page (similar to document.querySelectorAll('p')[2]).
Please leave Position Identifier empty if you use DFP 1x1 instead.
DFP 1x1 - serves as a fourth option for Position Identifier. This option assumes the publisher uses GAM aka Google Ad Manager (previously known as DFP) to create an iframe and put the script in it.
In that case, this option puts the player just above the iframe.
We suggest to use this option if the publisher should control the location, and yet you prefer to bypass 1x1 size (which is GAM’s preferable dynamic mode) plus reduce the risk of your ads being considered as “heavy ads” (which are blocked by browsers like Google Chrome, especially if found inside iframes).
Please leave DFP 1x1 empty if you use Position Identifier instead.

Default Channel/Template

The channel and template of Default can be used in 3 ways: All traffic (if both A/B Testing and Mobile Settings aren’t used), Desktop (if A/B Testing is not used, but Mobile Settings is) and Ignored (if A/B Testing is used).

Publisher Channel (required) - choose which publisher channel (based on Publisher) this player tag belong to.
Template (required) - choose which of the Templates should be used to define this player tag.
Predefined Only allows choosing only system built-in templates.

A/B Testing

Optionally divide the traffic between different positions/channels/templates.

This means both Desktop and Mobile traffic while ignoring both Default Channel/Template and Mobile Settings.

Mobile Settings

Optionally turn Default Channel/Template into Desktop only traffic, while using this section for Mobile Traffic.

Note this section is ignored if A/B Testing is used.

Left side:

Position Identifier - identical to the default setting, but used only for mobile.
DFP 1x1 - identical to the default setting, but used only for mobile.

Right side:

Publisher Channel - identical to the default setting, but used only for mobile.
Template - identical to the default setting, but used only for mobile.

Content

Optionally add player tag level content.

Left side

Use Only Tag Content - when TRUE, the player will show only the content from the tag. Otherwise, the content playlist will be a merge of the content from the tag and template, by that order.
Ads Mode - defines when ads are being displayed with 2 modes available:
1. Slot - ads are configured to specified time slots.
2. Breaking Ads - The player will always try to play ads.
** You can define a minimum gap(time) between each ad.
Breaking Ads or Slots - based on what you chose for Ads Mode, you can either control the gap between ads or define custom slots with timeouts.

Right side

Order - choose if the content order should be sequential or randomized.
Random From - if Order is Random then choose from which content number the player will start to randomize.

Videos content

Choose if the content should be manual (possibly viaFiles) or via the CMS.

We suggest to use CMS as its 100% built in order to easily assist with serving video content.

If you choose Custom you can define external URLs or Files.

If you choose CMS you can choose with playlists or videos to use.

Override Functions

This is one of the player tags' most powerful features, as it allows you to optionally inject your own JavaScript code into the player.

Each function is used in a different stage in the player tag’s events.

You can choose each function to override its default behavior.

Unique - controls the detection of whether this player runs more than once.
Find Win - controls if the player should run in the same document as the script of above it (e.g. parent or top).
Post Create - a usually empty placeholder that runs after the player’s main DIVs are created.
Retry - controls what happens when the player tries to re-activate itself after failures.
Create - controls the creation of the player’s main DIVs.
Position - controls where to place the player inside the page.
Load - controls the external calls to the player’s core.
Post Start - a usually empty placeholder that runs after the player has finished its initial loading.
Get Attribute - controls the pull of attributes from the script’s GET parameters.
Start - starts the player object.
Pre Run - a usually empty placeholder that runs before the player runs.
Run - controls the initially loading of the player.
Target - checks if the player runs in Desktop or Mobile.
Track - controls how the player tracks with pixels its internal flow.
Fetch Content - an InStream only event that fetches from the CMS for players that use it.
Init - reserved for future usage.