Technical Requirements for an RTB Integration

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:

  • Video SSP supports the IAB OpenRTB 2.2 API protocol (a common API specification for companies interested in an open protocol for the automated trading of digital media across platforms.)
  • To have an account configured for RTB access to marketplaces from a 3rd party system, contact your Video SSP account representative.
  • A bid response URL from your 3rd party buying system must be provided as well as instructions on user syncing and pre-targeting bid configurations that are to be applied to the RTB connection.
  • Bid URLs are configured in the Video SSP platform as RTB Ad Sources.


RTB integration guide

RTB integration guides provide technical details for developers and sales engineers, for the RTB API specifications Video SSP supports. Download the latest version OpenRTB 2.5 Protocol (version 2019-01-23).


Version Change Log
  • Upgraded the Open RTB version to 2.5. The following params are now supported:
    • “len” param in “content” Object.
    • “id” param in Site/App Object.
    • “pchain” param in Source Object(New Object added as part of 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 of “bidfloor” price and “bidfloorcur” wherever available for Open Auction in “imp” Object.
  • 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 “at” param in Bid Request Object. “at=1” is sent for first price auctions.
2018-10-25 Added support for “placement” param in Bid Request Object.
2018-09-20 Rebranding content.

GDPR Compliance

  • Added two params for GDPR compliance “regs.ext.gdpr” and “user.ext.consent”.
  • Updated the User Syncing workflow as part of GDPR compliance and UMS(Unified Mapping Service).

Programmatic Guaranteed Deals

  • Added a new param to deals object “deals.ext.guaranteed”. Value 1 signifies it’s a programmatic guaranteed deal.

Additional Device and User Parameters for Mobile Supply

For Mobile Supply, we now send additional values in the device and user objects:

  • Device object - Added new params “carrier”, “make”, “model”, “osv”, “js” and “connectiontype”.
  • User object - Added new param “yob” and “gender”.

Support for Content Category ("cat") and Language ("language"):

  • Added "Content" object under "Site" and "App" objects.

Support for IPv6 BRXD inventory only:

  • Added "ipv6" param to "Device" object.
  • Added "country" and "region" fields to "Geo" object (already present under "Device" object).

Support for Advertiser Blacklist:

  • Added support for “bcat” (blocked advertiser categories) and “badv” (blocked advertiser domains) params in Bid Request object.


Video SSP supports user syncing

Requests containing buyer’s unique identifier for a user are sent directly from user’s browser to the Video SSP server, which stores them for future use in bid requests. During initial integration choose whether to sync or not sync users from the Video SSP platform to your 3rd party buying system.

If syncing users, decide whether to use a Push or Pull syncing 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. 
Have more questions? Submit a request