...

1. 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).

2. 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>&nbsp;</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.

3. Position Text - Fill the position identifier text in this field:

   1. Tag - Single value of html tag name.

   2. Class - Single value of class attribute value.

   3. Id - Single value of id attribute value.

   4. Selector - Single or list of comma separated values of page selectors.

4. 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).

1. Publisher Channel (required) - choose which publisher channel (based on Publisher) this player tag belong to.

2. 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.

...

1. Allow Position Fallback - In the case that any of the “Position Identifier” values are not found on page, this feature attempts to position the player in any of the default position fallback selectors. The default list of selectors can be found in Account Settings / Studio / “Position Fallback Selectors”, and can be changed per account.

2. Position Text Priority - Appears only when position identifier is “Selector”, select one of two values:

   1. First in Page - From the list of comma separated selectors in the “Position text” field, position the player on the selector that appears first on the page (regardless of the order of values in comma separated list). Example: List of selectors are “p, div, h1”, if “h1” appears first in the html code of the page, the player will be positioned there.

   2. First in List - From the list of comma separated selectors in the “Position text” field, position the player on the selector that appears first in the list, considering the order of values in the comma separated selectors list. Example: List of selectors are “p, div, h1”, if “p” appears anywhere in the html code of the page, the player will be positioned there.

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).

Left side:

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

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

Right side:

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

2. 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.

1. Unique - controls the detection of whether this player runs more than once.

2. Find Win - controls if the player should run in the same document as the script of above it (e.g. parent or top).

3. Post Create - a usually empty placeholder that runs after the player’s main DIVs are created.

4. Retry - controls what happens when the player tries to re-activate itself after failures.

5. Create - controls the creation of the player’s main DIVs.

6. Position - controls where to place the player inside the page.

7. Load - controls the external calls to the player’s core.

8. Post Start - a usually empty placeholder that runs after the player has finished its initial loading.

9. Get Attribute - controls the pull of attributes from the script’s GET parameters.

10. Start - starts the player object.

11. Pre Run - a usually empty placeholder that runs before the player runs.

12. Run - controls the initially loading of the player.

13. Target - checks if the player runs in Desktop or Mobile.

14. Track - controls how the player tracks with pixels its internal flow.

15. Init - reserved for future usage.

InStream

Main

...

Placement Info

Left side

1. Name (required) - the name of the player tag.

2. Description - any note you like to add about this player tag.

3. Ref1 - add custom macros (e.g. AV_CUSTOM1=abc&AV_IDFA=1234-5678).

4. Publisher (required) - choose the publisher this player tag belongs to.

Right side

1. 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).

2. 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>&nbsp;</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.

3. 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 Publisher Channel (required) - choose which publisher channel (based on Publisher) this player tag belong to.

4. 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:

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

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

Right side:

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

2. 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.

1. Unique - controls the detection of whether this player runs more than once.

2. Find Win - controls if the player should run in the same document as the script of above it (e.g. parent or top).

3. Post Create - a usually empty placeholder that runs after the player’s main DIVs are created.

4. Retry - controls what happens when the player tries to re-activate itself after failures.

5. Create - controls the creation of the player’s main DIVs.

6. Position - controls where to place the player inside the page.

7. Load - controls the external calls to the player’s core.

8. Post Start - a usually empty placeholder that runs after the player has finished its initial loading.

9. Get Attribute - controls the pull of attributes from the script’s GET parameters.

10. Start - starts the player object.

11. Pre Run - a usually empty placeholder that runs before the player runs.

12. Run - controls the initially loading of the player.

13. Target - checks if the player runs in Desktop or Mobile.

14. Track - controls how the player tracks with pixels its internal flow.

15. Init - reserved for future usage.

InStream

Main

...

Placement Info

Left side

1. Name (required) - the name of the player tag.

2. Description - any note you like to add about this player tag.

3. Ref1 - add custom macros (e.g. AV_CUSTOM1=abc&AV_IDFA=1234-5678).

4. Publisher (required) - choose the publisher this player tag belongs to.

Right side

1. 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).

2. 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>&nbsp;</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.

3. 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.

...

1. Unique - controls the detection of whether this player runs more than once.

2. Find Win - controls if the player should run in the same document as the script of above it (e.g. parent or top).

3. Post Create - a usually empty placeholder that runs after the player’s main DIVs are created.

4. Retry - controls what happens when the player tries to re-activate itself after failures.

5. Create - controls the creation of the player’s main DIVs.

6. Position - controls where to place the player inside the page.

7. Load - controls the external calls to the player’s core.

8. Post Start - a usually empty placeholder that runs after the player has finished its initial loading.

9. Get Attribute - controls the pull of attributes from the script’s GET parameters.

10. Start - starts the player object.

11. Pre Run - a usually empty placeholder that runs before the player runs.

12. Run - controls the initially loading of the player.

13. Target - checks if the player runs in Desktop or Mobile.

14. Track - controls how the player tracks with pixels its internal flow.

15. Fetch Content - an InStream only event that fetches from the CMS for players that use it.

16. Init - reserved for future usage.

Position Function

to have more than one selector option,

1. go to ‘OVERRIDE FUNCTIONS’ - > ‘Position’ → insert the below function instead of the exist function
   

   Image Removed

2. add with comma and space after it “, ” more selectors.
   

   Image Removed

...

...