Page Comparison

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

Follow the instructions below instructions in order to work with the adapter.

Instructions

Setting up the channel

1. It is required to setup set up a 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 that your vast ad sources are really server-side before adding them. Server-side vast tags mean that the calls to those tags takes take place from Aniview servers.

   3. MP4 video ad sources

...

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

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

4. When sending AV_FLOOR, the value is used as the floor CPM for RTB demand

Prebid Rendering

Rendering The rendering of demand can be decided by the a 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 uses Aniview’s short tag setup:

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

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

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

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

5. Custom renderer setup:
   {
   bidder: 'aniview',
   params: {
   AV_PUBLISHERID: '55b78633181f4603178b4568',
   AV_CHANNELID: '5e9354521f78746eab47e8d8',
   AV_FLOOR: 1,
   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

...