Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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:

  1. In the list of players tags, click the circle.

  2. Edit an existing player tag and choose Generate.

2 forms of players can be generated:

  1. Short - generates 1 line of code that can modified by you remotely. This is the preferred form.

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

...

  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

...

Content

Override Functions

...