One-time Integration Setup
In order for 3rd party buying systems to access the Video SSP marketplace and/or other marketplaces a one-time integration setup is required. To get an account configured for RTB access to marketplaces from a 3rd party system, contact your Video SSP account representative.
Bid URLs are configured as RTB Ad Sources in the Video SSP platform.
Video SSP supports the IAB OpenRTB 2.5 API protocol.
The API protocol is a common API specification used by companies interested in an open protocol for the automated trading of digital media across platforms
A bid response URL from your 3rd party buying system must be provided along with instructions on user syncing and pre-targeting bid configurations that are to be applied to the RTB connection.
Video SSP supports user syncing
Requests containing the buyer’s unique user identifier are sent directly from the user’s browser to the Video SSP server. The Video SSP server stores the request for future use in bid requests. During initial integration choose whether or not to sync users from the Video SSP platform to your 3rd party buying system.
When syncing users, decide whether to use the Push or Pull method.
- Push method - Traffic a Video SSP sync pixel alongside the campaigns in your 3rd party buying system.
- Pull method - Provide Video SSP with a sync pixel from your 3rd party buying system. Your Video SSP representative must apply it to the user sync record within the system during the initial integration.
OpenRTB 2.5 API Change Log
The RTB integration guide provides developers and sales engineers with the technical details needed for the Video SSP RTB API.
Open RTB API version 2.5 upgrade now supports the following params:
- len param in content Object
- id param in Site/App Object
- pchain param in Source Object (New Object in V 2.5)
- tagid param in imp Object
- metric new Object added. Viewability info sent in the metric object; type, value and vendor are supported.
- Added support for passing bidfloor price and bidfloorcur wherever available for Open Auction in imp Object
- Added support for at param in Bid Request Object. at=1 is sent for first price auctions.
- Added “ssai” extension to Imp Object for identifying server side requests
In case of traffic from device types 3, 6 or 7, when no valid ifa is present, we send a custom synthetic proxy ID in IFA, to be used only for frequency capping. This proxy ID is NOT to be used for audience modeling.
Added support for placement param in Bid Request Object.
Rebranded content from ONE by AOL to Oath.
- Added two params for GDPR regs.ext.gdpr and user.ext.consent.
- Updated the User Syncing workflow as part of GDPR and UMS(Unified Mapping Service).
Programmatic Guaranteed Deals
- Added a new param to deals object deals.ext.guaranteed. Value 1= programmatic guaranteed deal
- Device objects - Added new params carrier, make, model, osv, js and connectiontype.
- User Object - added yob and gender params.
- Added support for Content Category (cat) and Language (language), under Site and App objects.
- Added support for BRXD Inventory
IPv6 IP address and have started passing Country and Region fields to Geo Object in select cases.
- Added support for Advertiser Backlist.
- bcat (blocked advertiser categories) and badv (blocked advertiser domains) params in Bid Request Object.
Added support for whitelisting of buyer seats on deals.
Added support for multiple seatbids in bid response.
Currencies supported in bid responses, nurl for win notice description, SSL compliance language on page, push method for user sync to HTTPS.
Added Regs object, and devicr.lmt field. Updated Adomain in the bid response to be required, and Seat in the Seatbid as recommended
Updated definition of auction type in Deals object to reflect OpenRTB standard
Added Publisher object, updated NURL macros. Updated Creative ID to be required.
For older updates see the appendix of VSSP OpenRTB_2.5_API_version_2019-01-23