VAST

Video Ad Serving Template

We support VAST 2.0 & VAST 3.0 for Apps & CTV.

Example tag and required macros are listed below and our account managers ([email protected]) will help you with the final ad code.

For Apps -

https://aex.ingage.tech/v1/tag/video?screensize=1920x1080&adUnitId=[AD_UNIT_ID]&publisherId=[PUB_ID]&mimes=video/mp4&mimes=video/ogg&mimes=video/webm&mimes=application/javascript&width=[WIDTH]&height=[HEIGHT]&bidFloor=0.5&bundleId=[BUNDLE_ID]&uid=[IFA_TYPE_MACRO]&plcmt=[PLCMT]&placement=[PLACEMENT]&minduration=1&maxduration=120&minbitrate=1&maxbitrate=10000

For Web -

https://ex.ingage.tech/v1/tag/video?screensize=1920x1080&adUnitId=[AD_UNIT_ID]&publisherId=[PUB_ID]&mimes=video/mp4&mimes=video/ogg&mimes=video/webm&mimes=application/javascript&width=[WIDTH]&height=[HEIGHT]&bidFloor=0.5&page=[PAGE_URL]&plcmt=[PLCMT]&uid=[UUID]&placement=[PLACEMENT]&minduration=1&maxduration=120&minbitrate=1&maxbitrate=10000

Except _adUnitId_and PublisherId all other value can be inserted dynamically. Our Publisher success team will help you with adUnitId & PublisherId

Additionally, please ensure that the &page parameter contains the full URL, including https://. The final root URL should be formatted as https://www.domain.com/. If the value sent to our server is already in this format, you may disregard this instruction.

Required & Recommended Macros

key

value

description

required

recommended

id

string

site/app id

Yes

Yes

adUnitId

string

Id of the ad unit

Yes

Yes

isApp

boolean

(OPTIONAL) Denotes whether the request is from Site / App. Use bundleId instead.

bundleId

string

App Id (If present, the tag refers to app )

Yes

Yes (For Apps Only)

page

string

Site page ( if present, the tag refers to site request )

Yes (For Sites Only)

width

integer

Width of the video player in device independent pixels (DIPS).

Yes

height

integer

Height of the video player in device independent pixels (DIPS).

Yes

bidFloor

number

"minimum": 0, only numeric values allowed

Yes

Yes

screensize

string

"pattern": "\d+x\d+"

Yes

uid

string

user id from browser traffic and ifa type for apps

Yes

placement

integer

1 (In-Stream) 2 (In-Banner) 3 (In-Article) 4 (In-Feed) 5 (Interstitial/Slider/Floating)

Yes

mimes

string[]

Yes

format

string[]

"pattern": "\d+x\d+" | Use Width and height instead

wrapperType

''iframe'' | "html"

html is used by default for banners. Videos will always be returned in xml format

plcmt

integer

1 (In-Stream) 2 (In-Banner) 3 (In-Article) 4 (In-Feed) 5 (Interstitial/Slider/Floating)

Yes

protocols

integer[]

We support [2,3,5,6,7,8]. Array of supported video protocols. Refer to List 5.8 in oRTB spec v2.5. At least one supported protocol must be specified in either the protocol or protocols attribute

Yes

minduration

integer

Minimum video ad duration in seconds.

Yes

maxduration

integer

Maximum Video ad duration in seconds.

Yes

api

integer[]

List of supported API frameworks for this impression. Refer to List 5.6 in oRTB spec v2.5.

Yes

linearity

integer

We have default of 1, as we support that only for now. It Indicates if the impression must be linear, nonlinear, etc. If none specified, assume all are allowed

skip

integer

Indicates if the player will allow the video to be skipped, where 0 = no, 1 = yes.

skipmin

integer

Videos of total duration greater than this number of seconds can be skippable; only applicable if the ad is skippable.

skipafter

integer

Number of seconds a video must play before skipping is enabled; only applicable if the ad is skippable.

sequence

integer

If multiple ad impressions are offered in the same bid request, the sequence number will allow for the coordinated delivery of multiple creatives

battr

integer[]

Blocked creative attributes. Refer to List 5.3 in oRTB spec v2.5

maxextended

integer

Maximum extended ad duration if extension is allowed. If blank or 0, extension is not allowed. If -1, extension is allowed, and there is no time limit imposed. If greater than 0, then the value represents the number of seconds of extended play supported beyond the maxduration value.

minbitrate

integer

Minimum bit rate in Kbps.

Yes

maxbitrate

integer

Maximum bit rate in Kbps.

Yes

playbackmethod

integer[]

Playback methods that may be in use. If none are specified, any method may be used. Refer to List 5.10 in oRTB spec v2.5

playbackend

integer

The event that causes playback to end. Refer to List 5.11 in oRTB spec v2.5

delivery

integer[]

Supported delivery methods (e.g., streaming, progressive). If none specified, assume all are supported. Refer to List 5.15.

pos

integer

Ad position on screen. Refer to List 5.4.

Ye


Preferences & Protection rules:

We support blocklist at advertiser domain, ad category level. We support minimum bid floor on the adUnitId level.

Please contact Account management team at [email protected] to apply the blocklist or minimum bid floor. We recommend keeping it empty by default for the maximum yield.

GDPR compliancy:

_If the users are from GDPR or any other privacy regulated area, it is required to have a CMP withTCF v2.2 in place and enable the below vendor ids (Consent & Legitimate Interest) for optimized performance. We can provide a CMP support if required, but if publisher is using own CMP we are requesting to ensure the following IAB vendors are granted Vendor Consent rights:

Vendor IDVendor Name
5833Across
617Onfocus (Adagio)
50Adform A/S
793Amazon Advertising
32Xandr, Inc.
143Connatix Native Exchange Inc.
24Epsilon
91Criteo SA
84Eskimi
755Google Advertising Products
10Index Exchange Inc.
333InMobi Pte Ltd
910Insticator
131ID5 Technology SAS
109LoopMe Limited
241OneTag Limited
69OpenX
76Pubmatic, Inc
1043TypeA Holdings Ltd
52Magnite, Inc
157Seedtag Advertising S.L
80Sharethrough, Inc
104Sonobi, Inc
13Sovrn, Inc
23Nexxen Inc.
36Nexxen Group LLC
45Equativ
1126Microsoft Advertising
128BIDSWITCH GmbH
528Kayzen
130NextRoll, Inc.
82Smaato, Inc.
512Verve Group Europe GmbH

Supported Countries (as of May 2025):

CountryAlpha-2Alpha-3
AustraliaAUAUS
AustriaATAUT
BelgiumBEBEL
CanadaCACAN
CyprusCYCYP
CzechiaCZCZE
DenmarkDKDNK
EstoniaEEEST
FinlandFIFIN
FranceFRFRA
GermanyDEDEU
Hong KongHKHKG
HungaryHUHUN
IrelandIEIRL
ItalyITITA
LiechtensteinLILIE
LuxembourgLULUX
MacaoMOMAC
MexicoMXMEX
MonacoMCMCO
MontenegroMEMNE
NetherlandsNLNLD
New ZealandNZNZL
NorwayNONOR
PolandPLPOL
PortugalPTPRT
QatarQAQAT
Saudi ArabiaSASAU
SingaporeSGSGP
SlovakiaSKSVK
South AfricaZAZAF
SpainESESP
SwedenSESWE
SwitzerlandCHCHE
United Arab EmiratesAEARE
United KingdomGBGBR
United StatesUSUSA

Quality guidance:

We recommend following the quality guidance to improve monetization outcomes.

Additional resources:

Reporting: https://documentation.insticator.com/docs/analytics-date-range How to establish the appropriate format specifications for CTV bundles. - https://iabtechlab.com/wp-content/uploads/2020/08/IAB-Tech-Lab-OTT-store-assigned-App-Identification-Guidelines-2020.pdf