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.
Supported supply: Video, Web, Mobile Web, App, CTV
Supported encoding: Plain text, GZIP (Recommended)
Request Object - Supported Fields
When calling demand, Aniview support the following objects and fields. If additional fields or extensions are required please contact Aniview.
Note - Some fields are located in ext in earlier versions of openRTB, Aniview automatically adjust it according to the configurable version):
Object | Supported Fields |
---|---|
request object | id |
imp | secure |
video | boxingallowed |
site | ref |
app | id |
publisher | id |
device | js geo (object) |
geo | country |
user | id |
regs | coppa |
pmp | private_auction |
deal | id |
source | tid |
Response
Aniview support the openRtb macros and will replace them in the response markup
Supported fields:
Object | Supported Fields |
---|---|
response object | id |
seatbid | bid |
bid | id |
Cookie Sync
Aniview support demand and supply initiated sync.
Aniview recommend supply initiated cookie sync. Syncing is automatically initiated by the player for relevant web traffic. It is recommended to support a dynamic redirect url so Aniview can control the redirect URL back to Aniview in realtime.
For demand initiated sync, Aniview will provide a sync URL.
For supply initiated sync, for new demand partners, provide a sync URL and Aniview will implement the integration.
Sync example:
DSP sync url: https://sync.dsp.com/partner=abc&r=https%3A%2F%2Fsync.aniview.com%2Fcookiesyncendpoint%3Fauid%3D1234%26biddername%3D9999%26key%3DBUYERUID
Dsp will redirect back to Aniview replacing BUYERUID with the actual user id
Aniview will save the user id mapping table and will use the buyeruid in future requests