VAST SSP Integration

Integrating with the RTB-Stack platform using the Video Ad Serving Template (VAST) involves a few steps to ensure that your video ad requests are correctly formatted and successfully processed. This guide provides an overview of the necessary configurations and parameters for VAST SSP integration.

The RTB-Stack platform supports VAST version 3.0 and higher.

VAST URL Configuration

The VAST URL used for sending bid requests for video ads typically looks like this:

Web:

https://your-adx-domain/vast?client=123&endpoint=123&ssp=123&isp=[ISP]&lmt=[LMT]&os=[OS]&dnt=[DNT]&connection=[CONNECTION]&page=[PAGE]&cat=[IAB_CATEGORY]&sectioncat=[SEC_IAB_CATEGORY]&pagecat=[PAGE_IAB_CATEGORY]&gdpr=[GDPR]&yob=[YOB]&gender=[GENDER]&width=[WIDTH]&height=[HEIGHT]&skipafter=[SKIP_AFTER]&skip=[SKIP]&skipmin=[SKIP_MIN]&protocols=[PROTOCOLS]&schain=[SCHAIN]&mindur=[MIN_DURATION]&maxdur=[MAX_DURATION]&pubcat=[PUB_IAB_CATEGORY]&contentcat=[CONT_IAB_CATEGORY]&lat=[LAT]&lon=[LON]&consent=[CONSENT]&coppa=[COPPA]&language=[LANG]&user_agent=[UA]&geo_type=[GEOTYPE]&ip=[IP]&rwdd=[REWARDED]&instl=[INTERSTITIAL]&pubid=[PUBLISHER_ID]&domain=[DOMAIN]

InApp:

https://your-adx-domain/vast?client=123&endpoint=123&ssp=123&isp=[ISP]&lmt=[LMT]&ifa=[IFA]&model=[MODEL]&ifa_type=[IFA_TYPE]&os=[OS]&osv=[OSV]&make=[MAKE]&dnt=[DNT]&connection=[CONNECTION]&storeurl=[STOREURL]&appname=[APP_NAME]&bundle=[BUNDLE]&cat=[IAB_CATEGORY]&gdpr=[GDPR]&yob=[YOB]&gender=[GENDER]&network_name=[NETWORK_NAME]&content_id=[CONTENT_ID]&content_rating=[CONTENT_RATING]&channel_name=[CHANNEL_NAME]&width=[WIDTH]&height=[HEIGHT]&skipafter=[SKIP_AFTER]&skip=[SKIP]&skipmin=[SKIP_MIN]&protocols=[PROTOCOLS]&schain=[SCHAIN]&mindur=[MIN_DURATION]&maxdur=[MAX_DURATION]&pubcat=[PUB_IAB_CATEGORY]&contentcat=[CONT_IAB_CATEGORY]&lat=[LAT]&lon=[LON]&consent=[CONSENT]&coppa=[COPPA]&language=[LANG]&user_agent=[UA]&geo_type=[GEOTYPE]&ip=[IP]&rwdd=[REWARDED]&instl=[INTERSTITIAL]&pubid=[PUBLISHER_ID]

Key Components of the VAST URL:

• Client, SSP, and Endpoint Identifiers: These are essential for routing the request correctly.
• Macros: These placeholders (e.g., [ISP], [MODEL], [OS]) should be replaced with real values when the bid request is made.
• Required Parameters: Certain parameters are mandatory, such as domain/bundle, IP and user agent. Ensure these are included to avoid request rejections. A complete list of supported VAST macros by the platform can be found below.

All VAST requests to the RTB-Stack platform should be made using the POST or GET method. All parameters should be included directly in the request URL. Ensuring that all required parameters are present is essential for the request to be processed correctly. Missing parameters can lead to request rejections or filtering by the platform.

Handling Invalid Requests

For any requests that are invalid or do not meet the platform's requirements, the RTB-Stack platform will return a JSON response containing a NoBidReason ("nbr") code. These NBR codes help identify the specific reason why a bid was not placed. You can find detailed descriptions and meanings of these NBR codes in the corresponding article.

VAST URL Sample:

https://your-adx-domain/vast?client=test&endpoint=test&ssp=test&isp=TestISP&lmt=1&ifa=test-ifa&model=TestModel&ifa_type=test&os=TestOS&osv=TestVersion&make=TestMake&dnt=0&connection=TestConnection&page=http%3A%2F%2Ftest.vast.com&storeurl=http%3A%2F%2Ftest.store.com&appname=TestApp&bundle=test.bundle&cat=IAB1,IAB2&gdpr=1&yob=2000&gender=M&network_name=TestNetwork&content_id=123&content_rating=PG&channel_name=TestChannel&width=640&height=360&skipafter=10&skip=1&skipmin=5&protocols=3,5,6&schain=test-schain&mindur=10&maxdur=60&pubcat=IAB22&lat=12.34&lon=56.78&consent=T&coppa=0&language=en&user_agent=TestUA&geo_type=1&ip=192.0.2.1&rwdd=1&instl=0&pubid=test-pub&domain=test.domain