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

Version 1 Next »

Overview

Aniview support setting up demand using OpenRTB protocol using protocol version 2.3, 2.4 or 2.5.

This document describes the supported fields and features.

Ad Markup

The Ad Markup must be in the form of a URL-Encoded VAST XML and it must appear in the bid response for it to be considered valid. Ad markup in the win notice response is not supported, but VAST wrappers are (in case you prefer to leave the ad selection for after the bid response).

The ${AUCTION_PRICE} macro should not appear in the VASTAdTagURI node. If it does, it will not be replaced with the actual winning price.

Supported Scenarios

Web (Desktop and Mobile Browsers)

App (Desktop and Mobile Applications)

CTV

Video

Video

Video

Request

Object

Supported Fields

Bid-Request

id
tmax
test
at
cur
bcat
badv
imp(Object)
regs(Object)
device(Object)
user(Object)
ext(Object)
site(Object)
app(Object)
ifa

Imp

secure
instl
id
tagid
video(Object)
bidfloor
bidfloorcur

Video

boxingallowed
startdelay
mimes
api
placement
maxbitrate
w
h
pos
minduration
maxduration
playbackmethod
delivery
ext(Object)
linearity
protocols

site

ref
id
page
name
domain
publisher(Object)
content(Object)

app

id
name
publisher(Object)
bundle
storeurl

publisher

id
name
domain

device

js
carrier
devicetype
make
ua
os
ip
language

geo (object)
osv
dnt
model

geo

country
lat
lon
type

user

id
buyeruid

regs

coppa
ext.gdpr

pmp

private_auction
deals

deal

id
bidfloor
bidfloorcur
at
wseat

source

tid
pchain
ext.schain

Extensions

  • No labels