Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Aniview prebid adapter required prebid version 3.18 and above support working with RTB, video and vast server side demand tags.

Follow the below instructions in order to work with the adapter

Instructions

Setting up the channel

  1. It is required to setup server side channel. Please contact Aniview if this option is not available

  2. In a server side channel, it is possible to add

    1. RTB ad sources

    2. Server side vast ad sources. Please verify if you vast ad sources are really server side before adding them. Server side vast tags mean that the calls to those tags takes place from Aniview servers.

    3. MP4 video ad sources

Setting Up Prebid Tag

  1. Prebid tag example:
    {
    bidder: 'aniview',
    params: {
    AV_PUBLISHERID: '',
    AV_CHANNELID: '',
    }
    }

  2. The minimum configuration includes AV_PUBLISHERID and AV_CHANNELID. Additional AV macros can be added

  3. No need for AV_URL and AV_CONSENT/AV_CCPA, those should be handled automatically by prebid setup

Prebid Rendering

Rendering of demand can be decided by the publisher. It can use its own player or renderer or use the renderer defined by each adapter.
Aniview has a default renderer that renders the outstream tag as defined in the prebid ad unit code attribute.
The default renderer will render the ad and close.

It is possible to define a custom renderer that use Aniview short tag setup:

  1. Only if there is a bid from the prebid tag, the renderer is called

  2. Only if the publisher choose to use the Aniview renderer it is called

  3. The renderer always use the position id defined in prebid setup

  4. It is possible to define a channel in the custom renderer and the channel will execute after running the bid from prebid so basically it runs the prebid and than continues to work as usual as its loaded in the page.

  5. Custom renderer setup:
    {
    bidder: 'aniview',
    params: {
    AV_PUBLISHERID: '55b78633181f4603178b4568',
    AV_CHANNELID: '5e9354521f78746eab47e8d8',
    rendererConfig: {
    tagUrl: "https://play.aniview.com/…. your short tag.js",
    tagId: "must match the scriptId in the tag.js"
    }
    }
    }

    1. Both tagUrl and tagId are mandatory

    2. tagId must match the scriptId in the template used otherwise it will not work

  6. Note that you should update the publisher that your custom script is taking over the prebid defined placement in order to avoid possible conflicts with prebid

Demos

  1. Default renderer

  2. Custom renderer

  • No labels